You are still answering tickets at midnight. The product makes money. The roadmap is a list you never finish. In 2026 you can ship alone longer. That does not tell you when to hire. Someone on the internet says “hire at $10k MRR.” Someone else says never hire at all. Both can be wrong for your week.
The useful rule is simpler. Hire after the work no longer fits one person. Not after a vanity milestone. Not because you are lonely. When a real, repeatable job is too big for you, and the business can pay another person without panic, you hire. Indiecity is for one person or a team under twenty. You do not need a department. You need the next seat only when your hours are full.
Stay small on purpose if that is the business
Hiring is not a moral upgrade. Some of the best bootstrapped products stay tiny forever. Pieter Levels wrote in 2019 why he still codes, designs, and markets his own products even when he can afford a team. He wants to keep building with his hands. He automates the boring loops with scripts so he does not need to manage people for work a robot can finish.
People have repeatedly asked me for years why now that I can afford it, I don't hire people, build a team and stop coding myself. Instead every day I still work on all my products by myself.
If that is your goal, stop reading for permission to stay solo. You already have it. This guide is for the other case: the work is real, the money is real, and your hours are the constraint.
What “the work no longer fits” actually means
It is not a feeling. It is a pattern you can write down.
- The same job eats a fixed block of your week (support, demos, onboarding, content ops, bug triage).
- That job is teachable. You can write steps. Someone else could follow them.
- Leaving it undone hurts revenue or retention, not just your mood.
- Doing it yourself blocks the work only you can do (closing, product judgment, hard sales, architecture).
- Profit (or stable surplus) can cover pay for long enough to ramp, not just one good month.
Arvid Kahl put the trap clearly: he thought hiring only made sense when there was “enough” for a full-time job, so he never hired while he already worked twelve-hour days. The load was real. The job title was the fiction. He also delayed because onboarding looked heavy. Waiting only stacked more undelegated work on top of the handoff he still had to do.
His fix is blunt. Hire for the work that annoys you most. In most SaaS companies, that is customer service first. Software scales. You do not. Once the base grows, someone has to triage the surprises so you can fix the real issues.
Do the unscalable work yourself first
Before you hire, you still need to know what good looks like. Paul Graham’s 2013 essay still holds: early on you recruit users by hand and do work that does not scale. That is how you get the first customers. It is also how you learn the job you might later pay someone to run.
If you have never done support, a support hire copies whatever you already do, including silence. If you have never sold, a salesperson invents a pitch you cannot coach. If you have never shipped a weekly post that brought signups, a content hire has no channel to grow.
Canny learned that the hard way. In early 2018 they were two founders, profitable, around $9k MRR, and stretched across product, demos, support, and marketing. They almost hired outbound sales. Seasoned founders asked which acquisition channels already worked. Sales was not one of them. Content was. So they hired a content marketer.
A month in they had one weak post, more founder time on marketing than before, and no trust. Around week five they ended it. Sarah Hum wrote that they hired for the role too early. They had no real content strategy. They expected a new person to save the day. Later they hired an engineer, a craft they already understood, and that hire worked.
Hire someone to do the things you have found success doing yourself. That way, they have a great starting point and can go up from there. Spinning up a completely new area of work is a risk.
Money first, then a seat
Bootstrapped means the hire eats revenue, not a raise. Canny’s later team guide is simple: grow the team as revenue grows, keep profitability in view, and only open a role that is essential for the next phase. They did not start hiring until after ramen profitability. Contractors and freelancers still fill gaps when a full-time seat is not ready.
Tyler Tringas told Indie Hackers that after Storemapper paid him what was, for him, a full-time salary (over $80,000 a year), he added support and a Rails developer so he could work on the business and travel without the product dying offline. The hire followed surplus and a clear need, not a blog milestone.
Stripe’s guide for first hires starts the same place: map what you already cover, pick roles by impact, and respect the budget. Part-time help and contractors are normal until you can fund a specialist. Count salary, tools, taxes, and the weeks before they are useful. If one bad month makes payroll impossible, you are early.
Pick the role that unblocks you
Write one week of your hours. Circle the blocks that are (1) necessary, (2) repeatable, and (3) not the unique judgment only you own. That circle is the job description.
- Support and success when tickets and onboarding eat founder time (Arvid’s default for SaaS).
- Engineering when the product is on fire and you are past your depth. Josh Pigford’s first Baremetrics hire was an engineer after large data sets outgrew what he could hold alone.
- Content or marketing only when a channel already works and you can coach quality.
- Sales only when you have a pitch, a price, and proof that humans close, not slides.
Ask Canny’s question out loud: what is the one role that would make the biggest impact right now? If you cannot answer in one sentence, you are hiring a feeling. Wait.
A practical sequence for the first seat
- Track two weeks of time. Name the top three recurring jobs by hours.
- Write a one-page SOP for the heaviest job. If you cannot write the steps, you cannot hire them yet.
- Price the seat: pay + tools + taxes + three months of ramp. Confirm profit still covers it.
- Try a contractor or a paid trial project before full employment when the work allows it.
- Hire into a channel or craft you already run. Do not invent a department on day one.
- Give clear outcomes for the first 30 days (tickets closed, deploys shipped, posts live). Review weekly. End it early if feedback does not stick.
In the next 30 days you own [job]. Success looks like [measurable outcomes]. I will be available for [hours] of questions each week. We review every Friday. If this is not working by day 30, we will say so plainly and decide whether to adjust or stop.
That note saves both of you weeks. Canny’s hard lesson was that staying polite and quiet wastes time. Honest weekly feedback makes a bad fit obvious for both sides.
What to stop doing
- Hiring because a podcast said a number.
- Hiring a salesperson for a product you have never sold yourself.
- Hiring a content lead before you have one channel that already works.
- Waiting for a “full-time” pile of work while you already work every night.
- Hiring so you feel less lonely when you need peers, not payroll.
- Skipping the SOP and hoping the new person will invent the process.
- Keeping a bad fit for months because firing feels worse than slow death.
How you know it is time
The work no longer fits one person. Profit can pay. You can teach the job because you already did it. Those three together beat any MRR chart. If any one is missing, wait, automate, or hire a few contractor hours. If all three are true, open the seat.
When you make the hire (or when you choose to stay solo on purpose) and the story is real, write it down. When the product has a name and a page, put it on the map. You can join while you decide. Peers help you think. They do not clear your ticket queue. After the first seat, the next question is how to keep the team under twenty as revenue grows.
Until the work no longer fits, keep doing it yourself. That is still the job.
FAQ
Questions people get stuck on
Is there a magic MRR where I should hire?
No. Revenue is not the signal. The signal is a repeatable job that eats the hours you need for product, sales, or survival, and profit that can pay someone without panic. Canny was profitable around $9k MRR and still got the first hire wrong because they hired into a role without a real process. Tyler Tringas hired after Storemapper paid him a full-time salary. The dollar number is personal. The hours problem is not.
Should my first hire be a developer?
Only if shipping is the bottleneck and you already know what to build. Josh Pigford’s first Baremetrics hire was an engineer because large data sets were on fire and he was over his head. If support or demos eat your week while the product is good enough, hire for that instead. Hire into the work you already run, not into a fantasy org chart.
What about hiring a salesperson first?
Risky if you have never sold yourself. When Canny thought about outbound sales as a first hire, other founders asked which acquisition channels already worked. Sales was not one of them. Their advice was to double down on what already brought customers, not to invent a new channel with a stranger. If you have no sales process, a rep cannot invent one for you.
Can I stay solo forever?
Yes, if that is the business you want. Pieter Levels has said for years that he still builds, designs, and markets his products himself, and that he automates the boring parts with scripts instead of hiring a team. [Indiecity is for one person or a team under twenty](/about). [Staying under twenty](/stories/keep-saas-under-20-people) is a choice, not a delay. Solo is not failure. Hiring is optional.
Contractor or employee?
Start with a contractor or a paid trial when you can. You want proof that the work is real, documented, and transferable before payroll, benefits, and tax IDs. Stripe’s founder hiring guidance treats freelancers and part-time help as a normal bridge until the company can afford a full-time specialist. Promote to employee when the hours and the trust are steady.
How do I know I waited too long?
You work twelve-hour days, still ship late, and the same queue (support, onboarding, bugs, demos) never clears. Arvid Kahl wrote that he delayed hiring because he thought the work was not “full time,” while he was already stuffing it into endless days. Waiting past that point does not make you lean. It makes you the bottleneck.
What if the first hire fails?
End it cleanly and write down what you learned. Canny’s first content hire ended around week five. They later said they hired for the role too early, without a real strategy, and expected someone to save the day. Their next hire was an engineer, a craft they already understood. A failed first hire is expensive. It is not a reason to never hire again.
How much cash should I have before I hire?
Enough that a bad quarter or a three-month ramp does not force you to fire someone next month. Grow the team with revenue, the way Canny describes: hire when you can afford it, keep profitability in view, and count onboarding cost, tools, and taxes, not only salary. If one paycheck would put you back to ramen risk, wait or use a contractor for fewer hours.
Should I hire so I feel less lonely?
No. Loneliness is real. A payroll is not therapy. Find peers in a community, a mastermind, or [join Indiecity](/join). [A cofounder is also the wrong fix for loneliness](/stories/cofounder-or-stay-solo). Hire when a job needs a second pair of hands, not when your calendar needs company.
