People ask me, fairly often, when I'm going to start hiring. The question is always framed the same way: as if hiring is the obvious next step, the proof that the business is real, the metric I should be optimizing for. I keep saying "not yet." The honest version of that answer is that I'm not sure I ever will, at least not in the way the question is asking.
This used to be a confession. In 2026, it's increasingly a defensible structural choice.
What hiring used to be for
For thirty years, the case for hiring was unambiguous: there's work you can't do yourself, and you need leverage. If you wanted to ship a product, you needed engineers. If you wanted to sell it, you needed salespeople. If you wanted to scale operations, you needed operators. Each of these required full-time humans, because the work required full-time humans.
The cost was substantial — every hire is a person, a salary, a management overhead, a cultural risk — but the alternative was leaving compounding revenue on the table. A founder who refused to hire was capping the business at their own bandwidth. The math wasn't subtle.
The math has changed. Quietly, asymmetrically, and faster than most founders have absorbed.
What changed in the last 24 months
Three things, layered on top of each other.
First, specialist software became absurdly competent. The set of things one person can do with modern tools — design, code, copywriting, video, accounting, ops — would have required a 12-person team in 2018. Not 80% of the way there. Actually equivalent output for most use cases. Not in everything; the gaps are real and I'll come back to them. But the gap closed for the median task.
Second, contract markets matured. The senior freelancer or specialist contractor in 2026 is a different category of person from the one in 2015. They have track records, references, defensible rates, and tooling. You can hire them for two weeks, get production-quality work, and never see them again. The "I need a permanent employee for this" reflex is mostly a 1990s assumption.
Third, AI assistance turned medium-skill tasks into supervision tasks. The work that used to consume a junior engineer's week is now me reviewing output and steering it. The bottleneck shifted from execution to judgment. Hiring junior people to execute makes less sense when execution is the cheap part.
The hidden cost of hiring
Founders who hire usually focus on the cash cost — salary, benefits, tools, office. That's the visible expense. The hidden expense is bigger and almost never makes it into the calculation.
You spend time hiring. You spend time onboarding. You spend time clarifying what you actually want, because what was implicit in your head now has to be explicit on a Notion page. You spend time reviewing. You spend time managing morale, conflict, priorities, vacation requests, calibration. You spend time un-stuck-ing people. None of this is the work. All of it is necessary if you have the team.
For most founders, the first hires reduce their throughput for 9–12 months before adding to it. The business doesn't actually grow until much later. Many businesses never recover the productivity they had at one person.
What I do instead
I structure my work in three layers, deliberately.
Layer one: things only I can do. Brand decisions. Direction. Final review on anything that ships. Client relationships at the senior level. These are the founder-bound activities and I do not delegate them. Ever.
Layer two: things I do with AI assistance. Most engineering. Most writing. Most analysis. The tooling does the mechanical part. I do the judgment part. This used to be most of the day. Now it's most of the value, in less than half the time.
Layer three: things I send out. Specialist work that has a clean spec and a clean output. Custom photography. Translation. Specialized legal. Specific audit work. I have a roster of contractors. None of them are employees. None of them require management.
The setup runs on me, plus tools, plus a network of independents. It scales the part of my output that needs to scale (execution) without scaling the part that doesn't (overhead).
Where this breaks
Honest caveats. This works for me, and I think it works for a specific kind of business — one that sells expertise or premium product, doesn't need huge transactional volume, and where the founder's judgment is the differentiator. It does not work for:
Businesses that need 24-hour operational coverage. Businesses that need on-site presence in multiple cities. Businesses where the bottleneck is genuinely physical labor at scale. Businesses where the work product is so domain-specific that no contractor exists. In any of those, hire — that's what hiring is for.
It also doesn't work if you actually want a team. Some founders do. They like the company, the collaboration, the leadership challenge. Those are real reasons. They are not the reasons people usually state, but they're real, and if they're yours, hire. The mistake is hiring because you think you should, when the underlying math no longer supports it.
The day I will hire
The day I hire is the day I find something I cannot do well alone, and where the contractor model fails to fill the gap, and where the new person's leverage clearly exceeds my management overhead. That day may come. It hasn't yet. If you don't have a clear answer to all three of those, neither do you.
The strangest thing about the 2026 economy is that "one person" is no longer the entry-level business size. It's a viable end state. The founders who realize this early get to keep the margin that used to flow to coordinating people. The ones who don't keep paying for an org chart that hasn't been necessary since 2023. There's no shame in either choice. There's only honesty about what your business actually needs versus what your peers expect.