The Case Against Hiring
The default startup story has a moment everyone treats as graduation. You hire. Headcount, an office, an org chart. The press calls it scaling. I want to make the unfashionable case that for a certain kind of builder, hiring is where the thing you loved quietly dies.
Start with the accounting nobody does. The instant you hire someone, your job flips from building to managing, and those aren’t adjacent skills. They’re different jobs sharing a title. Paul Graham nailed the schedules. A maker needs long unbroken blocks. A manager’s day is chopped into meeting-sized confetti. The moment you have reports, you’re on the manager’s schedule whether you asked for it or not. The exact thing that made you good, those deep hours with your hands on the work, is the first casualty of the hire that was supposed to give you leverage.
For most of history this trade was forced. You couldn’t build anything serious alone, so growth meant people, and people meant managing them, and that was the cost of scale. No other door. But the constraint is dissolving live. One capable builder with modern tools and a swarm of agents now produces what took a team of ten. The leverage that used to require headcount is starting to come from software. Which means the central reason to hire, I physically can’t do enough alone, is going false across more and more of the work.
So the question flips from “when do I hire” to “do I need to at all.” And the answer, more often than people admit, is no. Not because you can’t find good people, but because every hire imports a tax you only stop noticing because everyone pays it. Coordination overhead. Communication that used to happen instantly inside one head now crawling across many. Meetings that exist purely to undo the confusion that having multiple people created. Politics, eventually, always. The team is a cost center cosplaying as a growth engine, and most founders never run the comparison because “scaling” sounds like winning.
I’m not romantic about it. Some things genuinely need many hands. Building a rocket? Build a team, lead it well. But most things are not rockets. Most things are a good product that needs to reach the right people, and one person with taste, leverage, and distribution can do that, kept small on purpose. Staying small isn’t a phase you tolerate until you can afford people. It can be the design.
The part that took me longest to admit about myself: I don’t want to manage. For years I read that as a flaw, a ceiling on my ambition, something to outgrow. Now I read it as a spec. I want my hands on the work. I want the maker’s schedule. I want to build excellent things and ship them, not run a forty-person org I’d spend my days refereeing.
The agents are about to make the solo path stronger than the team path across a huge range of work. The most ambitious move of the next decade might not be building a big company. It might be refusing to.
One of a series of essays. I’m Prajjwal Chittori. prajjwalchittori.com.