A prompt rule and a calculator, written separately, landed on the same pricing floor

Charge more is not pricing advice, it is a slogan with a good hit rate. Here is the version I can actually defend, and the part of it I think people will quote wrongly.

The solo founder's pricing question is not what is this worth. It is whether there is any price at which one person can CARRY the customers that price requires.

Our contract names a low-ticket trap at roughly 19 a month, or 100 once. I want to be blunt about what that number is: a judgement written into a prompt by someone who had seen enough one-person products to have an opinion. Not a measurement. Treat every pricing floor you read anywhere the same way, including this one.

What makes it worth publishing is what happened when I put it next to arithmetic that knows nothing about it. At a 3000 target and 15 support minutes per customer per month: 9 a month is 334 customers and 19.2 hours a week of support. 19 is 9.1 hours. 29 is 104 customers and 6 hours.

The 2 rows at or below the pricing threshold are exactly the 2 rows in the heavy support band. Past about eight hours a week support is the job rather than a cost of the business, and the pricing line lands there without either half having been told about the other.

And now the limit, because this is the sentence I expect to get dropped: both halves are mine. A prompt rule agreeing with a calculator I also wrote is internal consistency, not validation. The only thing that makes it interesting is that they were written separately, for different purposes, and neither was tuned to the other.

The verdict vocabulary has 3 options and none of them is too high. That is not an oversight — it is not the failure mode a one-person product has. And the middle verdict, acceptable, means you can charge enough with nothing spare: no room for a bad month, a refund run, or the customer who costs four times the average. Most first prices land there and get read as a pass.

Two rules I would put in any pricing tool. Comparators cite a source or are marked unverified, because inventing a competitor's price is the most common lie in this genre and plausible prices are trivially easy to generate. And the model is not allowed to do the division — that is the one part of this with a right answer, and handing a right answer to something that samples is how you get confident numbers that do not add up.

Practical: start ABOVE the floor rather than at it. Dropping a price later is easy; raising it on existing customers is the conversation nobody enjoys.

The ladder: https://whittleos.com/guides/how-to-price-a-micro-saas