The Co-Founder Problem Nobody Warns You About

Business Development Series – How to Avoid Unsuitable Co Founders

There’s a particular kind of exhaustion that doesn’t show up on any balance sheet.

It’s not burnout from overwork. It’s not the slow grind of a bad month. It’s the specific, hollow feeling of watching something you built — really built, over years, with your own hands and mind — sit frozen in time because you’re waiting on someone else to show up.

I know that feeling well. I’ve been living inside it.

Context first: Why this “Founders Guide” series exist

This might read like naming and shaming. It’s not.

Every detail here is factual, verifiable, and entirely the co-founder’s own actions drawn from personal experience, emails, and timelines. No spin.

Even seasoned founders get burned. This series shows what can happen and how to protect yourself next time.

Since 2000, I’ve run GAUK Media. One of our flagship projects — Government Auctions UK — grew into a million-dollar-a-year business, driven largely by marketing. My marketing. The kind that compounds quietly over time: content, search, community, reach. If you want to understand the scale, the project’s history speaks for itself at gaukonline.co.uk/gauk-it.

It worked. For a long time, it really worked.

But there’s always been a gap — the one that sits between what I can vision and what I can build technically. I’m not a programmer. Never have been. And for years, that gap was managed. Our server tech Dave stepped in around 2018 when manual catalogue uploads hit their ceiling. We worked together to build automation. It was going well.

Then Dave died of cancer.

That loss — the personal loss, and yes, the professional one left a hole that took time to fully understand. Because what Dave represented wasn’t just a skill set. He was someone I trusted. Someone with skin in the game. Someone who gave a damn.

What followed was a hard education in what it means to be a non-technical founder trying to hire technical people.

I want to say something plainly here, not as a complaint but as a pattern I’ve observed repeatedly: no other profession expects to be paid by the hour regardless of outcome. I’ve had multiple developers promise a working product, take payment, and walk away leaving half-finished code and zero accountability. Not one. Multiple. The work sits unfinished. The money’s gone. And there’s no mechanism to reclaim either.

I did my due diligence each time. I asked questions. I checked references. I was careful. It didn’t matter.

By the time I reached the most recent chapter of this story, we had a new build at 90% completion. Ninety percent. We had a working MVP. The end was genuinely in sight. My plan was to bring in investment, hire a reliable CTO, and finally cross the finish line properly.

I joined the Ministry of Awesome cohort — a startup programme here in New Zealand — specifically to sharpen the investor pitch and refine the approach. It was during one of those sessions, in a meeting room, that I met Josh Trebilco.

He was personable, technically sharp, and genuinely enthusiastic about what GAUK was doing. He was also the founder of CodingNZ, which gave me some assurance around credibility. My concern upfront, and I raised it directly, was whether he could sustain the commitment. He assured me he had residual revenue from CodingNZ and the time to see this through.

We agreed to partner. And here’s where I made a decision I’ve since had a lot of time to think about.

Trebilco wanted to scrap the existing build and write his own version from scratch. I pushed back. We had a working MVP. We were at 90%. Starting over is never a neutral decision it resets everything. But he was confident, and his reasoning had logic to it. So I agreed.

He projected six months to a working product.

Six months passed. Then seven. Promises were made and remade. I even ran a countdown-to-launch email sequence based on his timeline — something that, in retrospect, I should never have done without the product in hand.

Then, without warning, Trebilco announced he’d taken a full-time position with a logistics company called Road Ninja. Just like that. He suggested he could still contribute one day a week but that didn’t materialise in any meaningful way. A few months later, he messaged to say he was stepping away from GAUK entirely.

He also mentioned, somewhere in those conversations, that his vision had been to spend six months building, then hand the marketing over to me while he stepped back and collected the reward.

Anyone who’s built a startup knows that’s not how this works. Startups don’t have a “sit back” phase. Not at our stage. Not for a long time.

I’ll be honest: this made me furious. Still does, if I let myself think about it too long.

Because I had delivered. Millions of views across social media. A real audience. Real momentum. Everything I promised, I did. But with no functioning platform to direct that audience to, it was like filling a bathtub with the drain open.

And here’s the part that doesn’t get talked about enough in the co-founder conversation — the asymmetry of accountability. As the non-technical founder, I was entirely dependent on the technical side being done. There was no workaround. No “I’ll just build it myself over the weekend.” The leverage was always in his corner, and when he left, he left cleanly, with no real consequence.

That asymmetry is the thing non-technical founders need to understand before they ever shake hands with a developer.

So. What do you do with all of this?

That’s what this series is going to explore — not theoretically, but from lived experience and hard-won clarity. How do you structure a co-founder relationship when you can’t evaluate the work yourself? How do you build in accountability without breaking trust? What are the legal, contractual, and human signals you need to watch for before you go all in?

The lessons aren’t pretty, but they’re real.

And if even one person reads this and avoids the kind of year I’ve just had — that’s worth something.

Next in the series: What a co-founder agreement actually needs to say — and what most people leave out.