Decision Playbook

Should I raise my prices by 20%?

Should you raise SaaS prices 20%? Validation strategy for £200K ARR. Reduce churn risk with segment-based pricing & customer research.

Last updated:

Who This Is For

You've built something real—£200k ARR, 180 paying customers, solid product-market fit with an NPS of 42—but you're feeling the squeeze between your 62% gross margin and the hiring pressure of a 12-person team that needs to grow. Your competitors are charging £65–£90 for similar products while you're at £49, and it's been eighteen months since your last price increase, yet you're acutely aware that your biggest customer represents 8% of revenue, making any misstep feel riskier than it would at a truly scaled company. This is the decision that separates founders who stay stuck from those who confidently grow: you need to know whether a 20% price rise will unlock the margin breathing room your team needs without triggering churn you can't afford.

What the Board Says

Maria Santos
"Implement immediate 18% price increase to £58/seat (capturing £9/seat margin improvement = £108K annual revenue at current 1,000 seats), paired with 90-day value communication sprint. Defer second pricing adjustment until NPS reaches 55+ (likely 9-12 months). Structure as: (1) Month 1: Customer research (15-20 win/loss interviews) to identify perceived vs. actual value gaps; (2) Months 2-3: Sales enablement and marketing repositioning to articulate existing differentiation; (3) Month 4: Price increase with transparent roadmap of planned improvements; (4) Months 5-12: Execute product enhancements targeting top 3 feature gaps identified in research."
Maria Santos

"Delay the 20% price increase for 3 weeks to conduct validation sprint."

"Delay the 20% price increase for 3 weeks to conduct validation sprint. Execute in parallel: (1) Segment 180 customers into ARR quartiles and map top 30 accounts by revenue, renewal date, usage trend, and competitive vulnerability; (2) Survey 25-30 customers across segments on price sensitivity using hypothetical scenarios ("How would you respond to a 15-20% increase?"); (3) Interview your CS team to quantify intervention capacity (accounts per CSM, current workload, bandwidth for 40-50 proactive conversations). Set go/no-go threshold: proceed with 20% increase only if validation shows <10% revenue-weighted churn risk and CS can handle 2x normal intervention volume."
Sarah Kim

"Conduct immediate customer value research (15-20 interviews over 2 weeks, budget £3-5K), then implement a conditional pricing strategy: If research shows primarily messaging gaps (customers undervalue existing features), execute immediate 15% increase to £56 with improved value communication."

"Conduct immediate customer value research (15-20 interviews over 2 weeks, budget £3-5K), then implement a conditional pricing strategy: If research shows primarily messaging gaps (customers undervalue existing features), execute immediate 15% increase to £56 with improved value communication. If research reveals genuine product gaps, implement modest 10% increase to £54 with transparent 6-month improvement roadmap, then reassess for additional increases only after NPS reaches 50+."
Henrik Sørensen

"Reject the 20% immediate increase."

"Reject the 20% immediate increase. Implement a conservative two-phase approach: (1) Immediate 10% increase to £54 (positioning as inflation/cost adjustment, not value increase), (2) Conditional second phase to £65-70 only after achieving NPS 55+ through documented product improvements. Simultaneously commission win/loss analysis (15-20 customer interviews within 30 days) to identify specific competitor advantages and validate which features justify premium pricing."
Leila Mansour

"Reject immediate 20% price increase."

"Reject immediate 20% price increase. Conduct 3-week validation sprint before any pricing decision: (1) Calculate actual revenue-weighted churn risk by mapping top 30 accounts (by ARR) against renewal timing, usage trends, and competitive exposure; (2) Survey 25-30 mid-tier customers on price sensitivity using conjoint analysis (test 10%, 15%, 20% increases); (3) Assess CS team capacity to handle 40-50 proactive retention interventions. Decision gate: If revenue-weighted churn risk exceeds 12% OR top-10 account concentration exceeds 45% of ARR, implement tiered increase (10% for top quartile, 20% for bottom three quartiles) instead of blanket approach."
Maria Santos

"NO-GO on 20% price increase."

"NO-GO on 20% price increase. Instead, execute 60-day parallel path: (1) Secure bridge financing ($120K credit line or investor advance) to fund 1 hire immediately; (2) Complete three audits (competitive pricing analysis, contract terms review, CAC-adjusted financial model); (3) Launch cost optimization sprint targeting $40K in non-headcount reductions. After 60 days, revisit price increase decision with complete data - likely outcome is targeted 8-12% increase on specific customer segments where competitive analysis confirms pricing power, not blanket 20%."
Leila Mansour

"REJECT current 20% price increase recommendation."

"REJECT current 20% price increase recommendation. Instead: (1) Secure $80-100K bridge funding within 30 days (credit line, investor advance, or deferred non-critical spending) to fund 1 immediate hire; (2) Complete 60-day audit sprint covering competitive pricing positioning, contract term limitations, and CAC-adjusted financial modeling; (3) Launch modified price increase in 90 days targeting only segments where audit confirms pricing power, with 8-12% increase (not 20%) for lowest-churn accounts first. If bridge funding unavailable, implement immediate cost optimization targeting $40K savings (defer marketing spend, reduce software subscriptions, delay office upgrades) while completing audits."

Recommendation

Executive Summary

The three deliberations converged on a single critical insight: the original 20% price increase recommendation rests on unvalidated assumptions that could destroy value. Sub-problem 1 exposed that 8% churn is unproven—real churn could be 12-15%, cutting your net benefit from £21K to near-zero. Sub-problem 2 revealed your NPS of 42 indicates a value perception problem, not pure underpricing—competitors charge 33-84% more, but customers don't perceive equivalent value. Sub-problem 3 identified a devastating timeline flaw: the 6-9 month funding gap leaves you understaffed exactly when you need capacity, driving service failures and accelerating churn. The unified recommendation rejects the blanket 20% increase and instead executes a three-part parallel strategy: (1) validate actual churn risk and customer value perception through 3-week research sprint, (2) secure bridge funding to hire one person immediately and break the timeline death spiral, (3) launch a targeted 8-12% increase only on customer segments where competitive analysis confirms pricing power. This approach captures margin improvement while eliminating downside risk through validated decision-making.

Recommendation

Do not implement a 20% price increase immediately. Instead, spend 3 weeks validating your actual churn risk and customer value perception through targeted research, then execute a modified 8-12% increase on specific customer segments where you have confirmed pricing power.

How to actually do this

Bridge funding or £40K cost savings must be secured within 30 days. Without this, you cannot hire immediately and will remain trapped in the understaffing-driven churn cycle identified in sub-problem 3.,Validation sprint and competitive audit must run in parallel to compress timeline. Sequential execution delays decision gate to week 6+, pushing any price increase beyond quarter-end.,Customer success team capacity is a hard constraint. If CS cannot handle 40-50 proactive retention conversations during rollout, retention risk increases substantially. Assess capacity before committing to timeline.

Frequently Asked Questions

Run This Decision in Board of One

This framework is generic by necessity. Your version would reference your margins, your competitors, your constraints. That's what Board of One does.