Go in Circles or Row Together
I built a SaaS platform. It worked. Nobody bought it. Then I built another one. It was acquired for millions. The difference wasn't the product. It was the partnership.
My business partner came to me with a clear deal. He had the idea, he would sell, I would build. Clear division.
Except he didn't stick to it.
Instead of finding clients, he got involved in the technical side. Instead of working the market, he had opinions on architecture decisions. Sales didn't happen. But it felt like we were making progress. I was building, after all.
Two and a half years later: a technically solid product. Zero clients.
The contrast
Six months later, the CEO of DirectorInsight brought me in to build his platform. He didn't have clients yet, but he knew the market. He had done the research and he had the right connections. What he needed was someone to lay the technical foundation.
We challenged each other, but responsibilities were sacred. When it was about technology, I decided. When it was about the market, he decided.
That product was acquired for millions.
The lesson
The difference wasn't the product. The difference was that everyone did what they were good at. And didn't do what they weren't.
This pattern shows up everywhere. In startups, in consulting engagements, in internal projects. The moment roles blur, progress stalls. Not because people are incompetent, but because effort gets scattered.
A technical co-founder who spends half their time on sales strategy is only half a technical co-founder. A business person who spends their afternoons reviewing architecture is only half a business person. You end up with two halves instead of two wholes.
The test
If you're building a product with a partner, ask yourself this: is everyone actually doing what was agreed? Not on paper. In practice. Every week.
Look at last week. Where did each person spend their time? Does that match the original division of responsibilities? If your technical co-founder spent three days in sales meetings, that's not "being involved." That's a role boundary violation that costs you engineering velocity.
If your business partner is reviewing pull requests instead of talking to prospects, you don't have a partnership problem. You have a sales problem that nobody is solving.
What to do about it
The fix isn't a difficult conversation. It's a simple one.
Sit down. Look at what each person actually did last week. Compare it to what was agreed. If there's a gap, close it. Not with vague commitments, but with specific deliverables for next week.
And if the gap keeps reopening? Then you have a different problem. Either the roles were wrong from the start, or one partner doesn't trust the other to do their part. Both are fixable, but only if you name them.
The most expensive partnerships aren't the ones that fail loudly. They're the ones that drift quietly for years, producing good work that nobody buys.
Kort samengevat: ik bouwde twee producten met twee partners. Bij de eerste bemoeide mijn compagnon zich met de techniek in plaats van te verkopen. Resultaat: solide product, nul klanten. Bij DirectorInsight waren de rollen heilig. Resultaat: overname voor miljoenen. Het verschil was niet het product, maar dat iedereen deed waar hij goed in was.
Jan Keijzer builds software for founders and has been on both sides of this equation. jan-keijzer.nl