Building the platform a SaaS startup needed to own

A New Zealand SaaS startup had built something brilliant. Their product was in market, institutions were using it, and results were good. The problem wasn't what they'd built. It was the platform they were delivering it through.

They didn't own it.

Every new customer onboarding ran through a third-party system they couldn't control. Every change request, every piece of customer feedback, every growth decision — all of it bottlenecked through someone else's infrastructure. They were building a real business on top of a foundation they had no power over. Scaling internationally was harder than it needed to be. Responding to customers took longer than it should.

In order to own their own future, they needed their own platform.

The timing added pressure. Key institutional customers had a fixed deadline — a new term starting, contracts in place, expectations set. There was no room to miss it, but the timing was aggressive.

We started with discovery. Before a line of code was written, we got across the business processes, the user needs, and what the first release actually had to do. Not everything on the wishlist. The right things, in the right order, so we all had the confidence we could be ready in time.

What we built became the central integration point between the startup's core product and the external systems their institutional customers already used. Onboarding became smooth. The feedback loop between the company and their customers shortened. The company could respond to the market on their own terms.

Our engineers got quietly obsessed with making the handoffs between systems invisible to end users. That kind of problem tends to do that to good engineers.

Customers were onboarded in time. The startup now controls their own platform, owns their own roadmap, and has a foundation they can actually build on. After a period of extended support and maintenance, their internal team has taken on their platform and continued to develop and enhance it.