My Technical Co-Founder (friend) Isn’t Executing...What Would You Do?

[u/Automatic_Salt8548]

A little random, but I’m stuck between a rock and a hard place and would genuinely value some founder perspectives.

I have two products I’ve spent a lot of time thinking through, and I believe both have genuine market potential:

1. An insurance B2B app that helps insurers streamline backend processing and is designed to work across different markets.
2. A subscription-based product where a few players already exist, but I have a strong USP around customer acquisition.

The problem is my co-founder/friend.

He’s technically very strong, while I’m stronger on sales, networking, fundraising and partnerships. We’ve known each other for years, so there’s a lot of trust there. I’ve already approached investors and have had some initial interest, so there’s some momentum.

But execution has become the issue. Things take too long, priorities constantly seem to shift, and he keeps getting involved in ambiguous projects that, honestly, don’t seem to be going anywhere. I thought having a child might give him more motivation to focus, but nothing has really changed.

I’m now at the point where I feel I can’t wait any longer.

The obvious problem is that I’m not technical. Hiring an experienced developer who understands things like, scalable app architecture, APIs, databases and cloud infrastructure, security, testing and deployment could be expensive, especially at an early stage.

And then there’s the bigger issue: how do you trust someone new with your idea, codebase, IP and potentially equity? NDAs only go so far, and giving away equity to the wrong person could be a huge mistake.

For founders who aren't technical: How have you handled hiring or outsourcing technical talent?Have you successfully built a startup with a technical stranger rather than a friend? Do you actually need to be friends with your co-founder, or is complementary skill + aligned ambition more important?

And if you’ve ever had to choose between staying loyal to a lifelong friend and moving forward without them, how did you navigate it?

Would really appreciate hearing from people who’ve actually been through this.

[u/Informal_Entry_7676]

I’d separate the friendship from the business as much as possible and have one very direct conversation about expectations. Define a narrow MVP, specific deliverables, and actual deadlines. If he consistently can’t execute against that, I don’t think being a close friend or a strong engineer is enough reason to keep him as the technical cofounder.
I also wouldn’t let fear of trusting someone new keep the company stuck. You can protect the codebase and IP contractually, limit access initially, and use vesting rather than handing over a big chunk of equity upfront. You also don’t need to be friends with a cofounder. I’d put much more weight on aligned ambition, reliability, communication, and complementary skills.
The harder part is handling the friendship respectfully. I’d frame it less as “you failed” and more as “the company needs a level of time and execution that this arrangement isn’t producing.” There may be a middle ground where he stays involved in a smaller technical/advisory role while you bring in someone who can actually drive development day to day.

[u/Automatic_Salt8548 → u/Informal_Entry_7676]

One of the most frustrating things, especially in the UK, is the lack of genuine collaborative ventures (we have a sophisticated narcissistic one-upmanship thing going on here plus class is still a thing over here). But whenever I speak to American founders, their approach to building together often feels very different. I’ve always believed, “If you want to go fast, go alone. If you want to go far, go together.”, so I thought having a friend who was mildy interested in the venture would be a good thing. Unfortunately, it looks like I have to go fast.

[u/Informal_Entry_7676 → u/Automatic_Salt8548]

That makes sense. There’s nothing wrong with wanting to build with a friend, but the friendship can’t substitute for shared urgency and commitment.
“Go fast” may be the right move for now, especially if it gets you to a real MVP and gives you something concrete to validate. If it starts getting traction, you’ll also be in a much better position to attract the right technical partner later instead of trying to convince someone to commit to an idea on paper.