Raise prices

Break one: fear holds the price down for years. The founder prices from their own wallet, from the customer they had two years ago, or from the dread of three angry emails. The number that replaces that dread comes from Jason Hale's testing discipline: price at roughly a tenth of delivered value, then raise about 5% at a time until you lose about 20% of prospects. Complaints are the market's honest number. If nobody complains, you're not being kind, you're subsidizing everyone, and the subsidy comes out of your margin, your marketing budget, and your sleep. Rob Walling's most repeated advice compresses the same finding to three words: double your prices. Directionally, for most B2B software, he's right.

Break two: the correct raise, executed abruptly on the installed base. The documented case is Gumroad in 2025: a jump to a flat 10% fee, hitting existing creators all at once, no grandfathering, no story ahead of the invoice. The math may well have been right; the trust burned anyway, publicly, in threads the company didn't control. An installed base doesn't experience your new price as strategy. It experiences a changed deal. The variables you actually control are sequence and narrative, and they matter more than the number does.

1. Pull the evidence. Three instruments: close rate, discount frequency, and the reaction at quote time. An 85% close rate with zero pushback is a pricing problem, not a sales achievement. So is the customer who says "that's it?" on the call. You're looking for the sound of money left on tables.

2. Audit the value, in dollars. The value equation: dream outcome, times perceived likelihood of achieving it, divided by time and effort to get there. Put an annual dollar figure on what you actually deliver: hours saved times loaded cost, revenue influenced, risk retired. If you're charging under a tenth of that figure, the gap is real, and it's yours to take to exactly the degree the value actually lands for the customer.

3. Raise on new customers first. No trust to spend there. Move in 5% steps, or test a doubled tier on the next cohort if the gap from step two is embarrassing. Hold each step two to four weeks. Watch close rate and complaint rate, nothing else.

4. Read the pushback like an instrument. Under 20% of prospects flinching: raise again, you haven't found the ceiling. Around 20%: that's the market's number, park there. Well past 20%: step back once, then check whether the objection is actually price or a value gap upstream (onboarding, activation, the wrong segment hearing the pitch).

5. Reprice the base last, with sequence and story. Grandfather them entirely, or glide-path them over 6 to 12 months with dated notice. Tell the story before the invoice: what improved this year, what's coming, why the number moves. Annual contracts get their term honored to the day. And loyalty can be priced too: a permanent discount off the new rate keeps the trust and most of the margin. What you may not do is let the increase announce itself in the billing email. The invoice is the last place the story should land, never the first.

6. Set the tripwire. Write the churn number and the date that would pause the rollout, while you're calm. Then stop relitigating every angry email, because the wire is watching so you don't have to. One founder's version: "base churn over 6% in any month pauses the glide." It never fired. They usually don't.

Three honest exceptions, because a page that only ever says "charge more" is a slogan, not a method:

• When the churn you fear is measurement noise. Twelve customers and one cancellation is a data point, not a trend. A raise decision needs a denominator.
• When the real problem is the segment. If your customers can't pay more because they're the wrong customers, repricing is a detour around the actual call, which is /focus.
• When you're monetizing before value lands. If activation is broken, a higher price just measures the disappointment faster.

• Asking customers what they'd pay. They answer as negotiators, never as data.
• Pricing against your own bank account instead of the customer's alternative. Your $49 feels expensive to you because you remember being broke. Their alternative is a $70k hire.
• Reading three loud emails as the market. Count the silent renewals too. The angry are always louder than the retained.
• Discounting your way into a segment problem and calling it pricing strategy.
• Years of dread about a reversible decision. The ruin check on new-customer pricing almost always clears: the worst case is a paused test and some apology emails. Nobody dies. The cost that actually goes unpriced sits in the health currency: years of thin margin is years of thin sleep, and that bill arrived monthly while you were being brave about $49.

Project analytics SaaS, $49 a month, 300 customers. Close rate 87%, complaints near zero, delivered value by the founder's own audit around $700 a month per customer. The silence is the finding. New signups move to $79: close rate dips to 81%, nobody blinks on calls. Two steps later new customers pay $119, and pushback finally hits about a fifth of prospects. That's the number; park there. The base gets the full sequence: grandfathered 12 months at $49, then a glide to $89 with a permanent 25% legacy discount, 90 days of dated notice, and the story ships first, a letter naming the year's three biggest features and the two the new price funds. Base churn after the glide: 2%, indistinguishable from baseline. New MRR up 58% in two quarters. The tripwire never fires.

The scary version of this call lived entirely in her head. That's where most of them live.