Why I Chose to Stay Solo Instead of Building a Startup

A year ago, someone at a networking event asked me, a solo founder with six figures in recurring revenue, when I was going to "build a real company." I had 200-plus customers and zero employees. To them, that meant I was holding myself back.

I told them I was thinking about it. That was a lie. I'd already decided.

The Question Solo Founders Get Asked

Once revenue starts climbing, the question comes in a few different forms.

"When are you hiring?" Or: "Have you thought about raising?" Or, the subtler version: "How do you plan to scale this?"

The assumption underneath all three is the same. Growth means headcount. Building something serious requires a team. Going it alone is fine for early days, but at some point you have to grow up and become a startup.

I believed that for a long time. Then I added an Engineering department and a Marketing department in the same week, and 32 agents came online across two teams. Within four days, those agents were doing work I'd have needed to hire four full-time people to cover.

That was the moment I stopped planning a startup. Not because I gave up on scale. Because I stopped confusing headcount with capability.

What the Agents Actually Did

Here's what the first month looked like in concrete terms.

The Content Creator was writing two long-form blog posts per week and drafting a monthly email newsletter. In a hiring context, that's a £40K/year role in most markets. The SEO Specialist ran keyword gap analysis every two weeks and mapped results to a publishing roadmap. The Social Media Strategist handled post scheduling, caption drafts, and flagged engagement spikes so I could respond to what was working.

On the engineering side, the Backend Architect reviewed every API change before it hit production. The Security Auditor went through the codebase once a month and returned a structured findings report. The Code Reviewer caught a timing issue in my payment flow that I'd have shipped confidently and lived with for months.

None of that ran me £80K a year in combined salaries, NI contributions, and recruiting fees. The Marketing department is $25.45/month. Engineering is $29.82/month.

The question "when are you going to build a startup?" started to feel like the wrong question. I was already running one.

What Stayed With Me

What I haven't handed to an agent, and don't plan to:

The call with a customer who's three days from churning and needs someone who understands the context behind their frustration. The decision about which new market to move into and when. The pricing call when a competitor undercuts us by 20%. The read on whether a feature request from five customers is real signal or noise from a vocal minority.

Those don't require execution capacity. They require judgment, and judgment comes from being close to the business for long enough to develop a feel for it. What AI agents give me is the time to stay close. When I'm not buried in content drafts or code reviews, I can actually think. That's the trade.

Who Should Start Where

If you're at the point where you feel like you need to hire, stop and ask which single bottleneck is causing the most pain right now.

Is it content and SEO? Start with Marketing. Is it code quality, test coverage, or keeping your infrastructure from breaking? Start with Engineering. Is it customer support eating your mornings? Start with Support.

Subscribe to that one department. Run it for 30 days with real tasks. In most cases the pressure to hire disappears because the specific bottleneck that was driving that pressure disappears with it.

If you're pre-revenue and still figuring out what to build, this doesn't apply yet. Sort the product first. Once you have customers paying, the bottleneck usually shifts to operations and delivery, and that's where AI departments have the most immediate impact.

The Honest Version

AI agents are not a reason to avoid every hire forever. If your business model depends on in-person relationships, physical presence, or judgment calls that require real-time human reading of a room, you'll find limits.

Agents also get things wrong. If you're shipping their output directly to customers without reviewing it first, that's a problem. The quality of what comes out is proportional to the quality of the brief going in, and there's a learning curve on writing good briefs.

The deeper point isn't that you should never hire. It's that most solo founders hire out of exhaustion rather than strategy. When you're overwhelmed, hiring feels like the only solution. Agents fix the overwhelm problem. Then you can make the hiring decision with clear eyes, from a stable position, not a desperate one.

For me, the answer was to stay solo. I have 110-plus agents across all 11 departments, and the business runs the way I always imagined a startup would, without the investors to report to, without the management overhead, without the hiring rounds that take months and go wrong half the time.

That doesn't mean it's the right answer for everyone. But it was the right answer for me.

---

You're still the decision-maker. You're just no longer the only worker. Start here.