Mostly a subtraction problem. You already know what works — the constraint is that servicing your existing customers now eats the hours growth needs.
Going from $10k to $30k MRR without hiring is mostly a subtraction problem. You already know what works — the constraint is that servicing your existing customers now consumes the hours that growth requires.
At $10k MRR your problem was finding customers. At $30k it is that you found them.
Below $10k MRR, growth comes from doing more — more outreach, more content, more conversations. Past it, doing more stops being available because your week is already full of work generated by the customers you have.
The arithmetic is straightforward. If each customer generates fifteen minutes of your attention a month, a hundred customers is twenty-five hours a quarter. Three hundred customers is seventy-five, which is most of a working month spent on maintenance.
So the growth lever at this stage is reducing per-customer attention rather than increasing acquisition. Scaling without hiring covers the mechanics; this page covers the sequence.
Two weeks of honest logging, categorised into four buckets. Most founders are surprised by the result and it is the only reliable way to find the actual constraint.
| Bucket | Healthy share | If it dominates |
|---|---|---|
| Growth work | 40%+ | — |
| Support and onboarding | Under 25% | Automate or self-serve it |
| Product and bugs | Under 25% | Quality problem, not a roadmap problem |
| Admin and billing | Under 10% | Almost entirely automatable |
The last row is the easiest win and the most commonly ignored. Billing failures, invoice queries and dunning are close to fully automatable, and they are pure overhead — see SaaS business automation.
At $10k MRR with flat pricing and one tier, every additional pound of revenue requires an additional customer — and additional customers cost hours you no longer have.
Expansion breaks that link. If existing customers can pay more as they get more value, revenue can grow without your customer count growing, which means without your support load growing.
This is usually a value metric question rather than a price question. If you charge a flat fee regardless of usage, a customer using the product ten times more than another pays the same — the value metric framework covers choosing the unit, and tier packaging covers structuring it.
Three moves, in order of return.
Answer the top five questions inside the product. You already know them. Putting the answers where the question arises removes most of your inbound without anyone noticing a change.
Fix the three bugs that generate the most tickets. Not the most severe — the most frequent. These are usually small and long-deferred because each individual report seems minor.
Make onboarding fully self-service. If you are still personally helping new customers get started at this scale, that is the single largest recoverable block of time — the onboarding framework covers closing it.
It arrives properly at this stage, and the answer is usually still not yet — but for a specific reason rather than as a principle.
Most of the work you would delegate at $10k–$30k MRR should not exist. Hiring someone to answer repetitive support questions institutionalises a problem you could remove. Automate first, then hire for what remains.
When you do, the first hire is usually part-time support or a contractor for a specific recurring task, not a generalist. And the trigger should be that a defined block of work exists which you have already failed to automate, not that you feel busy.
A test before hiring: could you write a one-page description of exactly what this person does every week? If not, you are trying to hire away a feeling rather than a task, and the hire will not fix it.
Three sources, in order of effort per pound of revenue.
Expansion from existing customers — cheapest, requires the pricing structure to support it.
Retention improvements — at this scale a point of monthly churn is real money, and the fixes are mostly one-time. Diagnose the type first.
The channel you already have, run harder — not a new one. Adding a second channel at this stage usually halves the attention on both.
If growth has stopped entirely rather than slowed, the diagnosis is separate — the MRR plateau guide covers it, and the previous stage playbook covers the four shifts that get you here.
Mostly by subtraction. At this stage servicing existing customers consumes the hours growth needs, so the lever is reducing per-customer attention rather than increasing acquisition. Start with a two-week time audit before changing anything.
The question flips from what to add to what to remove, expansion revenue starts mattering more than new customers, support becomes the binding constraint before acquisition does, and the hiring decision arrives properly for the first time.
Usually not yet, because most of the work you would delegate should not exist. Hiring someone for repetitive support institutionalises a problem you could remove. Automate first, then hire for what remains — and only when you can describe the role in one page.
The arithmetic. If each customer generates fifteen minutes of attention a month, three hundred customers is seventy-five hours a quarter — most of a working month spent on maintenance rather than growth.
Expansion from existing customers first, since it does not increase support load; then retention improvements, since a point of monthly churn is real money at this scale; then running your existing channel harder rather than adding a second one.
Bring two weeks of time logs and your customer count. Marcus names the block to remove first and what it buys you.
Try GhostCoach free →14-day free trial · cancel anytime · 30-day money-back on Lifetime