Price increases don’t fail on the number. They fail on the story.
Most pricing projects we run involve material price changes. Often a doubling or a tripling. Occasionally a 5×. The question is rarely can you raise prices — the data almost always says yes. The question is: how do you tell the customer base in a way that doesn’t cost you the customer base?
After ~200 projects, the same pattern shows up. The increases that hold are the ones that come with a story the customer can repeat to themselves and to their boss. The increases that don’t hold are the ones that arrive as a number.
Three steps. Million-dollar accounts and self-serve users alike.
The three steps
Most price increases fail on step one.
Worked example
How we 3×’d prices for a SaaS client with <2% churn impact
A B2B SaaS client serving mid-market operations teams. Stable customer base, low churn, NPS in the 60s. The list price hadn’t moved in three years; the product had shipped two major new capability lines in that window. The willingness-to-pay data said the list price was roughly a third of fair value.
The plan: a 3× list-price move, paired with a packaging rebuild (three tiers, new boundaries), grandfathering for any account older than 18 months on a two-year glidepath, and an ambassador tier for the top 30 long-tenured customers.
Frame: the new pricing reflects what the product became, not what it was. Pair: every tier gained something net new at the new price — not just a higher price for the same thing. Recognize: the long-tenured 30 got named, kept on old pricing through the glidepath, and given a small advisory role on the next packaging release.
Result: 3× list-price lift on new sales. Net churn impact across the existing base: under 2%. The accounts that left were not the long-tenured ones — they were a small middle band that the new tier structure had quietly priced out, which the data had predicted.
