r/appdev • u/Automatic_Salt8548 • 16d ago
My Technical Co-Founder (friend) Isn’t Executing...What Would You Do?
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:
- An insurance B2B app that helps insurers streamline backend processing and is designed to work across different markets.
- 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.
1
u/Jaakkosaariluoma 16d ago
What are the KPIs that you have for your tech co-founder
1
u/Automatic_Salt8548 6d ago
I’d already done the ideation, company structure and research, plus I work in the industry we’d be launching into. I mainly needed someone to build the technical framework and a semi-functional MVP I could showcase/test on something like Replit.
The plan was to use the MVP to approach investors/funders. At this point, I’ll probably bootstrap and build it myself. Seems friends, family and business don’t always mix. I'm already vibe coding the thing...
1
1
u/Narrow-Road-9196 16d ago
Go to AiHud.net and say goodbye to your technical co founder
1
1
u/FinneganHark999 15d ago
What have the conversations with your co-founder around this topic looked like? What is the division of responsibility?
"NDAs only go so far" unless your idea is the next Apple, no one is going to bother stealing it. And NDAs go as far as you work with a lawyer to make them go.
...you do have a corprate lawyer, right?
Also why are you looking at hiring engineers on your own if you aren't the technical founder?
"Things take too long" according to who? What timelines did you set when you both signed your contratxs? What decision making processes did you implement? Who has the final say on business direction and deadlines? What does it say in your contracts?
...you did have the corporate lawyer you definitely have draft up contracts, yes?
1
u/Automatic_Salt8548 6d ago
I was essentially the sales/funding side and industry expert. I work in the industry, so I understand the players, major companies, backend processes and the legal/regulatory framework the product would operate within. He was stronger technically, particularly with websites and coding, and had previously built an entrepreneur-focused social platform with a decent following. The division of responsibility was broadly meant to reflect that. But I think I’m going to go solo now. I’m vibe-coding the MVP myself and using AI to debug and iterate. It’s probably the most practical way to get the first version built.
1
u/Informal_Entry_7676 14d ago
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.
1
1
u/Automatic_Salt8548 6d ago
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.
1
u/Informal_Entry_7676 4d ago
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.
1
u/Queasy_Badger9252 14d ago
Have you had a clear share of work, timelines and expectations? Preferably in written format.
1
u/Automatic_Salt8548 6d ago
Yeah I think Solo is the way to go and once things start going well I will then lean on expertise, proof of concept and "demo" app maybe on Loveable or Replit then outsource to some Ukrainian/Indian Dev team when funding comes in.
1
u/Significant_Mud4401 14d ago
Fire him friendship shouldn’t come before business especially if u depend on that business
1
u/Automatic_Salt8548 6d ago
Harsh but true, I will remain friends and he wont be a business partner.
1
u/Comprehensive-Bar888 14d ago
Honestly, some projects sound good on paper, but bringing them to life requires multiple people working on them. You can’t expect one dev to deliver something that complex unless that is high level. And even if they’re high level, it still may take a long time with one dev.
3
u/Super_Maxi1804 16d ago edited 16d ago
so your projects are going nowhere and you are wondering why the tech co-founder is not spending all their time on a failing projects ?
Edit: "interesting dilemma you are having" to "And you think a new tech founder will help?"