Solo founders almost universally underprice. They also almost universally over-fear price increases. The right answer is to raise more often, by smaller amounts, and to grandfather existing customers when you do.
Methodology. This guide draws on pricing research published by Patrick Campbell and the team at ProfitWell / Price Intelligently, plus public price-increase histories documented by Pieter Levels on Nomad List. We have raised prices on three of our own products. How we research.
The pricing literature is consistent on one point: most SaaS companies should raise prices, most don’t, and the ones that do tend to wait years longer than they should. ProfitWell’s research found that companies invest roughly 6 hours total in pricing decisions per year, despite price being one of the highest-leverage levers in the business. The asymmetry is enormous.
If two or more of these are true, your current price is leaving money on the table. If three or more are true, you should be planning the increase this quarter, not next year.
If more than 7 out of 10 inbound prospects buy, you’re not pricing optimally — you’re convenience-priced. Healthy SaaS sees 30–50% close rates. A 70%+ rate means buyers don’t need to think.
Read your cancellation reasons. If “too expensive” is bottom-three, you’re too cheap to be feared and too cheap to be valued. The customers who churn are bored, not broke.
Compare today’s product to the v1 you launched. New integrations, new automations, new tiers, new use-cases. The price was set against a smaller product; the product has grown.
Pull up your three closest competitors’ pricing pages. If your nearest peer is charging $79 for a thinner feature set while you’re at $39, the market disagrees with your self-assessment.
AI inference, hosting, third-party APIs, support time — all of it has crept up. If gross margin has slipped 10+ points since pricing was set, you’re subsidising customers with founder time.
Pieter Levels has documented Nomad List price increases publicly for nearly a decade. The pattern is the same one Patrick Campbell’s research describes: prices crept up, churn didn’t spike, MRR did. The lesson is that raising prices is rarely as scary as the founder believes it will be — especially with the right grandfathering mechanic.
Most price-increase pain comes from execution, not from the increase itself. The mechanics below take a 4–6% involuntary churn outcome and reduce it to under 1%. None of them are clever; all of them are about respecting the social contract you signed when the customer first paid you.
Existing paying customers keep their existing price. Forever or for an explicit window — the choice depends on your gross margin. The promise that “your price won’t change” is one of the most undervalued retention tools in SaaS.
Update the pricing page on a Monday. The next signup pays the new rate. The previous customer doesn’t notice. This is the simplest and least-controversial flavour of price change, and the one that most founders should be running annually.
Email existing customers two weeks ahead: “Prices are going up on [date]. If you want to upgrade your plan, do it before [date] at the old rate.” You’ll see a 5–15% upgrade rate in that window. The customers who upgrade are also your most engaged ones.
Instead of raising the existing plan’s price, launch a new tier above it with the new price. The old plan stays available but is de-emphasised on the pricing page. Over time, new signups choose the new tier; old customers stay where they are. No one is forced to move.
This is the same mechanic we walked through in our SaaS pricing experiments playbook — you can run a price test without disturbing anyone who’s already paying you.
The size of the raise determines whether it’s a price change or a re-positioning. The right answer depends on which one you’re actually doing. Most founders confuse them, which is why so many price increases land badly.
| Raise size | What it actually is | Risk |
|---|---|---|
| Under 30% | Routine price update | Low — rarely controversial |
| 30–50% | Repositioning of existing offer | Medium — requires new value framing |
| Over 50% | New product, new audience | High — should be a relaunch |
| Over 100% | Different product entirely | Risky without grandfathering |
The under-30% range is the sweet spot for solo founders. A move from $19 to $24 is a 26% increase, lands as “rounded number,” and rarely triggers cancellation. Anything beyond 50% needs to be paired with a re-launch story — new features, new positioning, new audience — or it reads as opportunistic.
Most price increases work. A few don’t. The signals that you’ve overshot and need to roll back are concrete and quick to detect. Watch for them in the four weeks after the change goes live.
A rollback isn’t a failure — it’s the experiment giving you data. Frame it as a return-to-launch-price for a limited time, not as a retraction. The customers who signed up at the higher price get the lower price too, retroactively, which converts a near-miss into a positive trust event.
The patterns below show up across nearly every solo founder we’ve watched raise prices. Skip them and you’ll skip 80% of the pain.
If your inference bill or hosting bill is out of control, the right fix is the bill, not the price. Customers can tell when a price increase is operational rather than value-based, and they react accordingly. Cut costs first, then look at pricing as a lever for growth rather than survival.
The pricing-without-product-improvement raise is the worst kind. Customers compare what they pay this month to what they paid last month for the same product. Pair the raise with a visible product improvement, even a small one, and the framing flips from “more expensive” to “here’s what’s new.”
The dollar amount of the raise matters less than the surprise. A customer who finds out about a price change from their credit card statement loses trust in a way that’s hard to recover. Always email two weeks before. Always offer a one-time annual upgrade at the old price. Always grandfather longer-term.
The opposite of the surprise mistake. Founders avoid raising prices for years, then attempt a 60% increase to catch up. The 60% increase reads as drastic; the 8% increases that should have happened over five years would have read as routine. Build a calendar reminder to revisit pricing every six months and you’ll never end up in this position.
Run the numbers before you decide. A 20% price increase that triggers 5% extra churn still leaves you with 14% more MRR. A 30% increase that triggers 10% extra churn nets +17% MRR. The break-even churn rate for a given raise is roughly the raise size minus 1%; below that, you’re winning. Above that, you’re burning trust for no gain.
This is why the “raise more often, by smaller amounts” rule beats the “wait and do a big raise” rule. Each small raise is a small experiment with a small downside; the cumulative effect is a much bigger number with much less risk. We covered the MRR side of this in our what is MRR primer, and the churn math in what is churn rate.
If you’ve been on the same price for over 12 months and at least two of the five signals are true, draft a price-update email today. The email goes to existing customers two weeks before the change. The pricing page updates the morning of. The new tier goes live for new signups. Existing customers keep their plan price.
Then watch the numbers for four weeks. If signups hold within 70% of normal and existing-customer churn doesn’t spike, you’re done. If they don’t hold, roll back to a midpoint and try again with better positioning. The full mechanic is laid out in the solo founder pricing playbook — this guide is the “when”; that one is the “how.”
The asymmetry is worth restating: the downside of a too-small raise is invisible; the downside of a too-big raise is loud but recoverable. Solo founders systematically over-fear the second and under-fear the first. The fix is to start small and stay regular.
The stack, prompts, pricing, and mistakes to avoid — for solo founders building with AI.