Pricing advice for small software is either enterprise value-pricing theory or charge more as a slogan. The solo founder's question is a different one: not what this is worth, but whether there is any price at which ONE PERSON can carry the customers that price requires.
The verdict that does not exist
The analysis returns 3 verdicts, and the first thing to notice is what is missing. There is no verdict for too high. That is not an oversight — it is not the failure mode a one-person product has.
The middle verdict is the one to sit with. Acceptable means you can charge enough and have NOTHING SPARE — no room for a bad month, a refund run, or the customer who turns out to cost four times the average. Most first prices land there and get read as a pass.
The contract also defines a low-ticket trap: an idea structurally stuck below roughly 19 a month, or 100 once. When that is true the analysis says so and names the reason rather than proposing a price it does not believe in.
Where most pricing writing cheats
Be clear about what that threshold is, because this is where most pricing writing cheats. It is a JUDGEMENT WRITTEN INTO A PROMPT, not a measurement — a line drawn by a person who had seen enough one-person products to have an opinion. On its own it is worth very little, and you should treat any pricing floor you read anywhere the same way.
What makes it interesting is what happens next to arithmetic that knows nothing about it. Sweep the price ladder at a 3000 target and 15 support minutes per customer per month: 9 a month is 334 customers and 19.2 hours a week; 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 eight hours a week support is not a cost of the business, it is the job — and that is where the pricing line falls, without either half having been told about the other.
The limit, stated before anyone else states it
Now the honest limit, because it is the kind of coincidence people quote badly: BOTH HALVES ARE OURS. A prompt rule agreeing with a calculator we also wrote is internal consistency, not external validation. What makes it worth publishing is only that the two were authored separately for different purposes, and neither was tuned to the other. If you take the number and drop the sentence, you have taken the wrong half.
Two rules that keep the output honest
Two implementation rules that keep the output honest. Comparators cite a source or say UNKNOWN — a competitor's price is a fact about the world, and inventing one is the single most common lie in pricing research, convincing precisely because plausible prices are easy to generate.
And the model is NOT ALLOWED to do the arithmetic. The customers-needed calculation is explicitly forbidden to it and done in code instead. That is not a performance decision. A division is the one part of this with a right answer, and handing a right answer to something that samples is how you get a page of confident numbers that do not add up.
One more closed set worth copying: what a price may be anchored to. 5 options, and the first three — revenue, hours saved, a bill cut — are the ones you can defend in a sentence to a stranger. If the honest answer is status, you are selling a feeling, which sometimes works and never works predictably for one person with no brand. If the answer is other, the price is a guess wearing a rationale.
The ladder and both rules: https://whittleos.com/guides/how-to-price-a-micro-saas
Top comments (0)