Most “solo vs. agency” posts are thinly-disguised sales pitches for one side. This one isn’t. I’m a solo operator, but I’ve also run multi-engineer engagements under my consultancy, so I’ve seen both shapes from the inside.
Here’s what actually matters.
The real question isn’t “which is cheaper”
The question is: who is accountable when something breaks?
Everything else — cost, speed, scope — falls out of that one answer.
When a solo operator wins
You want one name on every decision. Agencies diffuse accountability across PMs, devs, and ops. When a bug shows up in production, “who owns this” is a meeting. With a solo operator, there is no meeting. One name on the commit, one name on the deploy, one name on the pager.
Your scope fits one person. Most scopes do — people just overestimate. A multi-tenant SaaS, a RAG system, a payment SDK, an AWS-from-scratch e-commerce backend: I’ve shipped all of these solo. If the scope needs six engineers, it probably also needs a product manager, a designer, and a QA lead — and you shouldn’t be comparing solo to agency, you should be comparing agency to hiring.
You want to ship in weeks, not months. No recruiting cycle. No onboarding. No “let me introduce you to the team” Zoom. Day one is working code, not a project charter.
You care about code ownership. Solo operators usually work in your repo, on your cloud, with your deploy keys. Agencies sometimes gate this behind retainer renewals. Ask upfront.
You want senior work on every hour. Agencies have to staff juniors to be profitable. A solo senior is, by definition, not staffing juniors on your project.
When an agency wins
Scope legitimately exceeds one person’s bandwidth. Some projects — complex enterprise integrations, regulated industries with parallel workstreams, 10+ simultaneous screens — genuinely need 4+ people working in parallel. A solo operator becomes the bottleneck. Don’t pretend otherwise.
You need domain expertise the operator doesn’t have. If your project is 40% a specialty the solo operator doesn’t live in (say, FedRAMP compliance, or embedded firmware, or payment-card-industry audits), an agency with that specific practice is worth it.
You need 24/7 incident response from day one. Most solo operators can offer on-call coverage, but not a multi-timezone follow-the-sun rotation. If you run a system where every minute of downtime is measurable revenue loss, you want an agency with a real ops team.
You want one contract for everything. Some enterprise procurement departments simply cannot sign a contract with a single person. That’s a political problem, not a technical one — but it’s real.
What people get wrong about the comparison
“Solo is riskier because of the bus factor.” True in theory. In practice, agencies staff high turnover too — the senior who sold you the engagement is rarely the senior who delivers it. And a good solo operator writes runbooks and decision docs precisely because they know you need to survive their absence.
“Agencies are more expensive.” Often, but not always. Solo senior rates can match or exceed agency blended rates. The cost story depends on what hours you’re actually getting — 160 agency hours at $150/hr with 40 of those spent on internal coordination isn’t cheaper than 100 senior hours at $200/hr with 0 coordination tax.
“Solo can’t scale.” Separate question. Solo can handle a launch. Whether it can handle 10× user growth depends on the architecture they leave you with — which is usually better than what agencies deliver, because solo operators live with their own infrastructure decisions.
How I’d frame it
Here’s my honest decision tree:
- Is the scope more than 12 weeks of one senior engineer’s time? No → solo. Yes → keep reading.
- Does it need real parallel workstreams? No → solo, extended timeline. Yes → keep reading.
- Does it need a specialty outside your operator’s stack? No → solo + specialist subcontractor. Yes → agency or keep reading.
- Do you need 24/7 coverage from hour one? No → solo + retainer for ongoing. Yes → agency.
If you ended up at “agency” from that tree, hire one — but vet the senior who will actually do the work, not just the AM who sold it.
The honest close
If you’re reading this and your scope does fit one person — and most do — let’s talk. I’m available for scoped builds, retainers, and rescue work.
If your scope really needs a team, I still run multi-engineer engagements through my consultancy. Same “one accountable operator” promise, just with engineers I hire and lead under me. Same contact page.
The shape of the engagement should match the shape of the problem. Everything else is sales theatre.