Two divisions that changed how I price: the customer count, and the support hours next to it

How many customers do I need is target divided by price. That takes one line and it is not the answer. Here are the two numbers that actually decide it.

At 5000 a month you need 173 customers at 29, or 51 at 99. The first feels achievable, which is exactly the problem.

Put support next to the count. At 15 minutes per customer per month, 29 means 173 customers and 10 hours a week of support before you have built or sold anything. At 49 it is 103 customers and 5.9 hours. The two numbers move in opposite directions and somewhere between them is a floor.

Past about eight hours a week, support is not a cost of the business. It is the job.

So the honest answer at that target is: at or above 49, about 103 customers. Below that the count stops being the binding constraint and your calendar becomes it.

The bit I run for people who ask me about pricing: you do not need 103 customers in total, you need 103 at the SAME TIME. It is a level to hold, not a finish line to cross.

At 5 percent monthly churn, holding 103 means signing about 6 new customers a month before you have grown by a single seat. At 29 it is about 9 a month, on top of the 10 hours of support you already owe. That is why the cheap rows are worse than they look on the way in.

Three levers, unequal. Cutting support minutes is linear and helps at every price at once — that is what onboarding, docs and a product that explains itself actually buy. Raising the price is the fastest single move and the one most people refuse. Lowering the target is allowed; the number is a choice.

What the arithmetic does not know: every customer costs the same in it, billing and refunds are ignored, and it assumes the customers exist and can be reached — which is the question that actually kills most ideas.

Both calculators are free and take no signup: https://whittleos.com/guides/how-many-customers-do-i-need