Raising Prices on Existing Customers: My $18k MRR Diary

"I spent three weeks scared of the wrong customers. The ones who yelled stayed. The ones who left never said a word."

That is the line the founder kept coming back to when we talked through his pricing change, six months after he made it. He runs a bootstrapped B2B SaaS, an operations tool for small agencies, and he asked me to keep the product name private and change his first name. I will call him Adrian. Every number below is his own, self-reported from his Stripe dashboard and shared on the condition that I round and anonymize. Treat them as one honest operator's ledger, not a benchmark.

He had been stuck on the same prices since launch: $29 for the Core plan, $79 for Pro. By December 2025 he was at roughly $18,000 MRR across about 470 paying accounts. Every advisor, every Reddit thread, every pricing post told him the same thing: he was underpriced, and he should have raised prices two years ago. He knew it. He was also quietly terrified of the one thing none of those posts could promise, which is what happens to the customers who were already paying you when you change the deal.

This is what actually happened.

Quick answer

Raising prices on existing customers in 2026 is survivable, and usually net positive, if you segment instead of doing it all at once. In Adrian's case, a tenure-and-engagement-based increase (grandfather the founding cohort permanently, give everyone else six months, nudge retained accounts by less than the new-customer price) cost him about 4% of his existing base in churn over 90 days but lifted MRR roughly 16%, from about $18,000 to about $21,200. The customers who churned were overwhelmingly low-engagement accounts that had not logged in for weeks. The loud, angry repliers mostly stayed.

Why he finally raised prices

The trigger was not greed. It was math he could no longer ignore.

New support hires, a jump in his infrastructure bill, and two years of shipped features meant his gross margin was drifting the wrong way while his price sat frozen. Pricing is the most under-invested lever most bootstrappers have. Paddle's pricing research (the team that absorbed ProfitWell) argues that getting pricing right can be, in their words, "up to 7.5 times more powerful than acquisition" as a growth lever (Paddle, accessed July 2026). Adrian had spent two years pouring energy into acquisition and almost none into the price itself.

He ran the counterfactual in his Stripe data first: if even his newest cohort had signed up at a market-rate price, he would already be past $22k MRR. The gap was not a rounding error. It was a second part-time salary he was leaving on the table every month.

The plan: segment by tenure, not a flat hike

The advice he trusted least was "just raise it on everyone." The advice he trusted most came from operators who had actually done it and written the receipt afterward.

So he built a segmented plan instead of a flat one:

• New customers: Core moved $29 to $39, Pro moved $79 to $99, effective immediately.
• Existing customers: a six-month grandfather window, then a smaller nudge, Core $29 to $35 (not the full $39) and Pro $79 to $89, with 60 days notice before the new rate hit.
• The founding cohort: the earliest ~40 accounts who believed in the product when it was ugly stayed locked at their original price, permanently, and were told so by name.
• Annual plans: honored at their locked rate until renewal.

He modeled the blended outcome before sending a single email, tier by tier, the way you would with a pricing-ladder calculator like BudgetForge's three-ladder pricing model, so he knew his floor and his ceiling before he touched anyone's invoice. That preparation is the difference between a price change and a panic.

The week-one inbox

He sent the change to about 430 existing accounts in January 2026, excluding the 40 founders. Then he sat with his laptop open and braced.

The replies came fast. About 38 people wrote back. Roughly 22 were annoyed, 9 said some version of "I'll cancel," and 7 were genuinely fine with it, a couple even said it was overdue. The angry ones were articulate and specific, and for about 48 hours it felt like the whole base was revolting.

It was not the whole base. It was 38 out of 430, less than 9%, and even inside that 9% the loudest voices were not the ones who left.

What 90 days actually did to the numbers

Here is the honest before-and-after, rounded, as of April 2026.

He lost about 19 accounts over the 90 days that he could reasonably attribute to the increase, roughly 4% of the existing base. That churn cost him around $650 in MRR. But the retained accounts on the small nudge added about $1,900, and new customers signing at the higher price plus a handful of Core users who upgraded to Pro rather than pay the nudge added roughly another $1,650. Net, he was up about $2,900 MRR, a 16% lift, inside one quarter.

Who actually churned (the part nobody warns you about)

This is the finding Adrian wishes someone had told him before he lost sleep.

The accounts that silently canceled were, almost without exception, low-engagement seats: users who had not logged in for 45 days or more, teams that had clearly moved on and were quietly paying for a tool they had stopped opening. Losing them was not a wound. It was healthy churn he should have surfaced a year earlier.

Meanwhile, the loud repliers, the 22 annoyed and the 9 who threatened to leave, mostly stayed. At the 90-day mark, more than half of the "I'll cancel" crowd were still active subscribers. Compare that with the operator on r/SaaS who took the opposite route, doubling their price from $9 to $19 across the entire base at once and reporting that they lost roughly half their customers. Same instinct, very different execution, and the execution is the whole story. This is the same pattern I keep seeing in the retention numbers behind the-month-my-churn-doubled-at-20k-mrr-retention-diary: the scary-looking number and the real number are rarely the same customers.

The mistake he made

He is not going to pretend it was clean.

His first version of the announcement email quietly re-priced some annual plans mid-term, meaning a few customers who had paid a year up front were being told the rate had gone up before their renewal. That was wrong, and they were right to be angry about it. Within 72 hours he sent a correction, honored every locked annual rate until renewal, and personally apologized to the handful affected. He still lost about 2 accounts to that mistake, and, worse, a slice of trust he had to rebuild. If you change pricing, treat an annual commitment as a contract, not a suggestion.

The one takeaway

Do not grandfather everyone forever, and do not rip the bandage off everyone at once.

Segment by tenure and engagement. Protect the founding cohort by name. Raise the real money on new customers and expansion first, nudge retained accounts by less, and give long notice. Then, before you panic, actually read who churns. The people who yell are giving you their attention, which is the opposite of the problem. The people who leave without a word already left months ago. You are just making it official, and getting paid properly by everyone who stayed.

Keep reading

• the-month-my-churn-doubled-at-20k-mrr-retention-diary, the retention mirror image of this story.
• why-we-killed-our-saas-at-12k-mrr, what happens when the unit economics never recover.
• killing-7400-mrr-saas-solo-bookkeeper-founder-diary, another founder's honest call on a number that looked fine on paper.