01The setup
Amilia runs recreation and membership software; their customers wanted that data flowing into HubSpot, and Amilia invested in SyncSmart to build the bridge — a SmartRec-to-HubSpot integration. That framing matters: a partner was putting real money behind us to extend their platform, which meant the bar was theirs, not just ours. Miss it, and it's not an internal roadmap slip — it's a partner's bet that didn't pay off.
02The build — scope grew, timeline held
We built the SmartRec → HubSpot integration to spec over a five-month window, November through March. Then the scope grew: a second integration — to a third-party registry — was added mid-stream. The easy path is to let new scope move the date, and nobody would have blinked. Instead we absorbed it and still delivered on schedule — two integrations where one was scoped, without asking the partner to wait for the thing they'd paid for.
03The launch — proven, then scaled
We didn't ship into a vacuum and hope. We launched in partnership with a flagship YMCA and validated the build against their real-world use cases — so day one was proven against a marquee customer's actual workflows, not a sandbox. Getting a recognizable, high-expectation reference customer live is what turns "it works" into "it's ready to sell."
It's since grown into a production workhorse. The integration now runs across about five customers — including multi-location YMCA groups — syncing thousands of members and their activities every day. Not a demo that shipped once: live infrastructure moving real data at volume.
04Enablement — so both sides could sell it
A launched integration nobody can sell or support is shelfware. I built the go-to-market layer myself: internal sales enablement plus a customer knowledge base of 17 support articles for the SmartRec integration — authored using Claude to read the connector code folders and project docs directly, so the documentation matched what the software actually did instead of what a spec once said it would.
Enablement ran both directions. When Amilia's own prospect-facing Security & Compliance brief — for a nonprofit's legal review — came back with the SyncSmart leg blank, I filled it: our security attestation, hosting and data-residency posture, data-persistence behavior, and a customer-facing DPA. The partner could keep selling because our half of the due-diligence answer was ready when they needed it.
05Making it sustainable
Once it was live and selling, the relationship drifted the way successful partnerships often do: the weekly cadence quietly became a pipeline of free work — unpaid features, consulting, and support, with Amilia's engineers booking straight onto our calendars for more. So I reset it, treating the partnership as an ecosystem to design rather than a contract to re-sign:
- Rewrote the commercial terms. A revised reseller / hosting agreement with a real definitions section — iterated to its eighth version — so the relationship rested on defined terms, not habit.
- Defined the operating model. Amilia owns first-line support and demos; SyncSmart takes escalations only; no more free development; new features are paid expansions. A clear line, drawn on purpose.
- Reset the cadence, up-level. Moved from weekly to a monthly partner review and sent the reset to the Amilia principals with a one-page operating model attached — so it landed as a decision, not a complaint.
06Result & what I'd take forward
One partner integration, owned end to end: built with expanding scope on a held timeline, launched and validated on a flagship customer, enabled for sale and support on both sides, and finally structured into a bounded, paid model that compounds margin instead of draining it.
The lesson I carry: the signature and the integration are the easy part. The durable value comes from delivering under pressure, proving it on a real customer, arming the people who sell it, and designing the incentives so the relationship stays profitable instead of quietly turning into unpaid roadmap. That's the lens I bring to any partner or vendor relationship now.