From four failed co-founder splits to a $66M solo startup

Executive overview

Most founders treat co-founders as a default rather than a deliberate choice — and pay for it when the relationship breaks down. David Phillips cycled through four co-founder splits before refounding his company alone with $40K left in the bank.

The core insight: solo founding forces a level of resourcefulness that co-founding rarely demands, and AI tools have now removed the main reasons founders avoided going solo.

Four co-founder splits and what they taught

• First split: geographic drift post-college; ended amicably, both sides built competing versions of the same company
• Second: raised a seed round with a hackathon partner, then got fired six months in — key lesson: move on fast, don't litigate it
• Third and fourth: iterated through co-founders while building a coding bootcamp; eventual acquisition provided a clean exit
• Each breakup reinforced the same pattern: misaligned commitment, not misaligned vision, is what ends most co-founder relationships

How to handle a co-founder departure

• Make the separation logical, not emotional — find common ground on what's best for the cap table
• Encourage the departing founder to get experienced startup legal counsel; a startup attorney will tell them the same thing: move on and preserve the equity upside
• If the company can continue, continuing is often better than shutting down — existing investors and cap table relationships have value
• Find one close ally in your investor pool before sending the hard update; their support before the email goes out matters more than the words in the email
• Send the update, state the plan, offer a six-month checkpoint — don't over-explain

Choosing the right idea as a solo founder

• With $40K left and no co-founders, Phillips ran every idea through a strict filter: can I do this solo, do I have deep domain expertise, can I reach profitability without raising?
• Fondo surfaced because he had been an accountant at Deloitte, had done startup accounting every possible way, and had personally lost track of his own runway — he was the customer
• The prior idea (Bloomjoy) was opportunistic: a Facebook meme page that sparked a listicle distribution play, killed when Facebook changed its terms of service
• The durability test: accounting for startups is not going away; the format changes, the need does not
• Domain expertise is the shortcut to trust — and trust is the only path to early customers

Getting the first customers

• First big client (The Hustle / Sam Parr) came through a Twitter DM and a warm intro from a shared investor; it felt like the model, but then no one else signed up for three months
• Pivot insight: early-stage startups, not mid-market, were the real customer — lower ACV, far more of them
• Delaware franchise tax wedge: posted on Bookface offering to file it for free; 100 companies signed up; filed all 100 returns; pitched bookkeeping to all 100; got the first 10 paying customers
• Same pattern at Hackbright (the coding bootcamp): launched on Hacker News, got one applicant; switched to teaching code for free at local meetups; that built the trust that filled the school
• The repeating principle: do the core thing for free first, build trust through demonstrated expertise, then offer the paid product

Building trust beyond the core product

• Fondo targets early-stage founders, whose biggest problem is distribution and visibility — not accounting
• Solution: build an audience, then use it to promote customers and prospects (podcast appearances, livestream show, blog features)
• Outcome: founders have landed investor meetings and acquisitions after appearing on Fondo's media; the brand benefit to Fondo is secondary but real
• Helping people with problems unrelated to your product creates an opening for them to consider your product — an opening that would not exist otherwise

Working with family

• Family brings built-in trust, loyalty, and genuine investment in the company's outcome — the same things founders seek in co-founders, without the cold-start risk
• The risk of a complete falling out is lower with family than with a professional co-founder
• Requires clear role definition and explicit expectation-setting; professionalism has to be maintained deliberately

The bear and bull case for solo founding

Bear case

• It is simply harder — harder than co-founding, and harder than most people expect
• When launches fail, there is no one to commiserate with; when you are stuck, there is no one to think out loud with
• The lows are lower and you absorb them alone

Bull case

• Hardship builds resiliency that co-founding rarely forces
• No co-founder friction means ideas go from concept to market faster
• Solo founders build real teams earlier because they have to
• More equity to give to early hires
• Default co-founders — chosen to avoid going solo, not because of genuine fit — produce most of the bad co-founder relationships; removing the default removes the bad outcomes

Why AI changes the calculus

• AI coding tools (Claude Code, Cursor) mean a solo founder can build and ship an MVP without a technical co-founder
• The most common reason founders sought co-founders — needing someone who could build — no longer applies
• "There's no excuse" to wait for a co-founder; anyone can build and get to customers now
• The argument: solo founding should eventually become the default; truly great co-founders remain valuable, but co-founders of convenience produce most of the horror stories