Your target divided by your price, rounded up. That is the whole first answer, and every result for this question spends a page defining MRR instead of giving it. The second answer is the one that decides things: at that customer count, how many hours a week is support, and does what is left still fit one person's week?
The count, and why it is the easy half
At $5,000 a month you need 173 customers at $29, or 26 at $199. No model, no estimate — a division, and you can run it yourself on the customers-needed calculator without signing up for anything.
One honest edge in that arithmetic: a one-time price has no answer here at all. There is no recurring revenue to divide, so the function returns nothing rather than a confident zero. If your plan is a single payment, this question is the wrong one and the number you actually need is how many sales per month, forever, to replace the ones that do not repeat.
What makes the count feel useful is that it is achievable-sounding. Six hundred people is not many people. That feeling is where the mistake lives.
The second number, which is the constraint
Support is not free and it does not scale down. Take fifteen minutes per customer per month — one short email, or a fraction of a call you are not taking — and put it next to each price:
| Price | Customers needed | Support / week | What that is |
|---|---|---|---|
| $9 | 556 | 32 h | support is the job |
| $19 | 264 | 15.2 h | support is the job |
| $29 | 173 | 10 h | support is the job |
| $49 | 103 | 5.9 h | a real share of the week |
| $99 | 51 | 2.9 h | a real share of the week |
| $199 | 26 | 1.5 h | background noise |
| $499 | 11 | 0.6 h | background noise |
Both columns are computed by the functions behind the two free tools, at $5,000 a month and 15 support-minutes per customer per month. The target and the minutes are your dials; the arithmetic is not.
Read it from the bottom and the shape is obvious. The two numbers move in opposite directions: every step down in price multiplies the customers, and every extra customer adds support you personally owe. Somewhere between them is a floor.
Last price that does not work
173 customers, 10 hours a week of support before you have built or sold anything.
First price that does
103 customers and 5.9 hours — a real share of the week, and survivable.
The bands are calibrated to a solo founder's week rather than a company's: past eight hours a week, support is not a cost of the business, it is the job.
So the answer to "how many customers do I need" at this target is not a number. It is: at or above $49, 103 of them. Below that the count stops being the binding constraint and your calendar becomes it.
Three ways the floor moves
Cut the minutes. Support load is linear in them, so halving fifteen minutes halves every hour column and moves the floor down a price step. This is what onboarding, docs and a product that explains itself actually buy you, and it is the only lever that helps at every price at once.
Raise the price. The fastest single move, and the one most solo founders refuse. Look at what $199 does to the customer count — 26 people is a number you could learn the names of.
Lower the target. $5,000 is a choice, not a law. Run the tools at yours.
The number is a level, not a total
One thing the division quietly hides: you do not need 103 customers in total. You need 103 customers at the same time. They are a level to be held rather than a finish line to be crossed, and every month some of them leave.
The arithmetic for that is unforgiving and easy. At five per cent monthly churn you lose one in twenty every month, so holding 103 means signing roughly 6 new customers a month before you have grown by a single seat. That is the treadmill, and it is why the cheaper rows in the table are worse than they look: at $29 the same churn rate means replacing about 9 people a month, on top of the 10 hours of support you already owe.
Which is the honest version of "how many customers do I need": enough to reach the level, plus enough every month to stay there, at a price where serving them is not your whole week.
What this arithmetic does not know
It assumes every customer costs the same, and real customer loads vary. It assumes support is your only per-customer work, ignoring billing, refunds and the occasional bug that eats a Saturday. And it assumes the customers exist and can be reached, which is the question that actually kills most ideas and that no calculator can answer.
Treat the floor as a lower bound on the price, not an upper bound on the difficulty.
The short version
- The count is target ÷ price, rounded up. It is one line, and it is not the answer.
- Put the support-hours calculator next to it: at 15 minutes per customer per month, $29 means 10 hours a week before you have built anything.
- At $5,000/month the floor lands around $49 — 103 customers.
- Three levers: fewer support minutes, a higher price, a smaller target. The first helps at every price at once.
- A one-time price has no answer here, and the calculator says so instead of returning a zero.