LaunchWeek.ai

Back to Day 4: Convert

Pricing Review Cadence: Stop Setting Pricing Once and Forgetting It For 3 Years

Most founders set pricing at launch, intend to "revisit later," and don't until customers churn or the team complains revenue is stuck. By then they've left $1-5M on the table over 2-3 years of unchanged pricing. The other failure mode: tinkering monthly, confusing the team and customers. The fix is a deliberate cadence — quarterly pricing review (5-min check); semi-annual audit (90-min); annual deep-revision. Done well, pricing tracks the value you create, not where it landed at launch. Done badly, pricing decays as features compound while price stays flat.

A working pricing-review cadence answers: when to revisit (not "when something feels off" — on a schedule), what signals warrant change (qualitative AND quantitative), how often to actually change (1-2x/year max for major; minor tweaks more often), how to communicate changes (most founders bury the lead), how to grandfather existing customers (or not), and how to test before broad rollout.

This guide is the playbook for ongoing pricing maintenance. Distinct from Pricing Strategy (initial design), Pricing Packaging Tier Design (tier structure), Raise Prices (the actual change), and Pricing Experiments (testing).

What Done Looks Like

By end of this exercise:

  • Quarterly 30-min pricing review on the calendar
  • Semi-annual 90-min audit with data inputs
  • Annual revision window (often Q4 → effective Q1)
  • Signal dashboard (close rate, win rate by tier, churn at price points, NRR)
  • Grandfather policy documented
  • Communication template for price changes
  • 1-2 hypotheses to test in next 6 months

This pairs with Pricing Strategy, Pricing Packaging Tier Design, Raise Prices, Pricing Experiments, Pricing Page, Annual Contract Negotiation, Renewal Negotiation Playbook, Customer Success Metrics Framework, Sales Discovery Call Playbook, Win Loss Analysis, Free to Paid, Activation Metric Definition, and Annual Planning & OKRs.

Why Pricing Drifts

Help me understand pricing decay.

The 6 reasons pricing-without-review goes wrong:

**1. Feature accumulation**
You ship 30+ features over 2 years.
Customers get the new features at original price.
Each feature reduces willingness-to-pay-more for the next.
By year 3: dramatic feature/price gap.

**2. Cost / margin shift**
Hosting, AI inference, support all change cost.
Original pricing assumed costs that shifted 30-50%.
Margin quietly compresses.

**3. Competitive pricing shift**
Competitors raise; commoditize; or undercut.
Your relative position drifts; you don't notice.

**4. Customer-mix shift**
Started SMB; now 30% mid-market customers.
Mid-market would pay 3-5x more for advanced needs.
Lower-tier captures their dollars; you leave money on table.

**5. Inflation**
2024-2025 inflation alone added 5-10% to "fair" pricing.
Companies that didn't adjust effectively cut prices in real terms.

**6. Value-perception evolution**
Year 1: novelty; price-sensitive.
Year 3: customers locked in; switching cost real; less elastic.
You can charge more without losing customers.

**The compound result**:

Started with reasonable pricing. After 2-3 years no review:
- Margins down 10-30%
- LTV / CAC ratio declining
- Win rate inflated (you're cheap)
- Sales not pushing tier up (no incentive)
- Competitors charging 2-3x for similar value

For my company:
- Last pricing change date
- Top decay symptom

Output:
1. Decay diagnosis
2. Lost-revenue estimate
3. Urgency

The unforced error: "we'll change pricing once we have product-market fit." PMF is a moving target. Pricing should evolve with PMF, not wait for some imaginary stable state.

The 3-Cadence Framework

Help me set the cadence.

The 3 cadences:

**Quarterly: 30-min check-in (light)**

Owner: founder + CFO/finance
Format: review dashboard; no decisions usually
Look at:
- Win rate by tier
- New-MRR by tier
- Churn rate by tier
- Average ACV trend

If nothing material changed: done in 15 minutes.
If something flagged: schedule deeper review.

**Semi-annual: 90-min audit (medium)**

Owner: founder + CFO + sales lead + CS lead
Format: data review + 3-5 hypotheses

Inputs:
- Detailed metrics (above) trended 6 months
- Win-loss data (specifically: "we lost on price X times")
- Sales feedback ("we're leaving money on table because...")
- CS feedback ("customers say tier is too expensive / too cheap")
- Competitor pricing scan (manual; 30 min)
- Activation per tier
- Expansion patterns

Outputs:
- Decision: keep / minor adjustment / plan major revision
- Hypotheses to test
- Action items

**Annual: revision window (heavy)**

Owner: founder + leadership team
Format: 2-4 weeks of work; effective Q1 typically

Activities:
- Deep customer interviews (10-20)
- Competitor full audit
- Margin / unit-economics analysis
- New tier consideration
- Tier renaming / restructuring
- Communication plan
- Roll-out plan (existing customers vs new)

Most companies: only the major revision lands; quarterly + semi-annual feed into it.

For my company:
- Cadence today
- Calendar slots

Output:
1. Calendar template
2. Roles
3. Inputs per cadence

The discipline: calendar it like board meetings. Quarterly + semi-annual + annual = 4 calendar slots / year. Block them; show up; have data. Without calendar discipline, "we'll review later" never becomes "we reviewed."

Signals That Warrant Pricing Change

Help me read the signals.

The qualitative signals (heard in sales / CS):

- "Competitor X charges 2x and we're winning anyway" → underpriced
- "We lose 30%+ of deals on price" → overpriced (or wrong target)
- "Customers don't ask about price" → underpriced
- "We're at the top of our pricing range and team feels good" → likely too cheap
- "Customers buy and immediately negotiate" → priced reasonably; expected
- "Customers ask for [feature] in our base tier" → re-evaluate tier boundaries

The quantitative signals:

**Win rate**:
- > 30% on inbound → likely underpriced (raise; lose 5-10% to gain 30% per-deal value)
- 15-25% → healthy
- < 10% → overpriced or wrong target

**Negotiation rate**:
- < 20% of deals get discount → priced low (raise)
- 20-50% → healthy
- > 60% → priced high; consider lowering OR adjust list to negotiated

**Tier mix**:
- 80% on entry tier → mid/top tier doesn't differentiate enough
- Roughly even mix → tiering works
- > 50% on top tier → entry tier is too cheap or top tier has too much

**NRR by tier**:
- Higher NRR on premium → premium customers expand; raise other tiers toward parity
- Higher NRR on entry → entry attracts good customers; consider gating less

**Churn by tier**:
- High churn on entry, low on premium → premium gets value; raise entry
- High churn on premium → premium isn't worth premium price

**ACV trend**:
- Avg ACV stagnant 12+ months → no upmarket movement; new tiers needed?
- Avg ACV climbing → mix shifting; pricing is working

**Time to expansion**:
- Customers expand within 6 months → priced right; tier-up natural
- Customers expand only at renewal → tier boundaries too sticky

For my dashboard:
- Top 5 signals to track

Output:
1. Signal dashboard
2. Trigger thresholds
3. Action per signal

The signal that compounds: discount rate. Track every deal's discount %. Anything > 30% sustained = your list price is wrong; either lower OR reset your floor. Discounting damages the brand if pervasive.

Communicating Price Changes (the Hard Part)

Help me announce price changes.

The principles:

**1. Don't bury the change**

Bad: 6-paragraph email; "Pro tier will now be $99/mo (was $79/mo)" buried in paragraph 4.
Good: subject "Pricing update: [tier] now $99/mo (was $79/mo) — effective [date]"

**2. Explain why**

Acceptable reasons:
- "Cost of underlying infrastructure has increased"
- "We've shipped 12 major features since last pricing"
- "We're investing in support to better serve you"

Unacceptable:
- "Inflation" alone (sounds like cop-out)
- "Just because" (no respect)
- Defensive ("don't worry it's still less than competitors")

**3. Notice period**

Existing customers:
- 60 days minimum for monthly subscriptions
- 90 days for annual subscriptions (next renewal)
- Some companies grandfather existing for 1-2 cycles

New customers:
- Effective immediately on announcement
- Active in-flight quotes: honor old price for 30 days

**4. Grandfather policy (decide before announcing)**

Options:
- **Full grandfather**: existing customers keep current price forever
- **Time-bounded grandfather**: existing keep for 1-2 years
- **No grandfather**: everyone moves to new at next renewal
- **Tier-specific grandfather**: enterprise grandfather; SMB no

Trade-offs:
- Full grandfather = customer goodwill; permanent revenue gap
- No grandfather = max revenue; some churn risk
- Most companies: 12-24 month grandfather

**5. Exception escalation path**

Some customers will push back. Have an escalation:
- "We can hold price for [N] months"
- "We can offer [annual discount] at original price"
- "Let's discuss what's working / not working"

Don't make this universal; reserve for genuine push-back.

**Email template**:

Subject: Pricing update for [Plan Name] — effective [date]

Hi [name],

We're updating pricing on the [Plan Name] tier from $X to $Y, effective [date].

Why: [reason — be specific]

What this means for you: [Existing customer]: Your current price holds until [renewal date]. After that, you'll renew at the new price. [New customer]: You'll be on the new price starting [date].

Why now:

  • We've shipped [X feature], [Y feature], [Z feature] since 2024
  • Our infrastructure costs have grown [N%]
  • We're investing in [specific area]

If you have questions or concerns, reply to this email. We're happy to discuss your specific situation.

[Your name]


For my upcoming change: [details]

Output:
1. Notice timing
2. Grandfather decision
3. Email template

The mistake to avoid: vague price-change emails. Customers who notice the change feel disrespected; customers who don't notice churn quietly when their card is charged the new amount. Be direct; explain; honor commitments.

Testing Before Rolling Out

Help me test pricing changes.

The progression:

**Stage 1: Test with new sign-ups (no rollback risk)**

Show new pricing only to new visitors (cookie-based; 50/50 split or phased).
Measure:
- Conversion rate (sign-up → trial → paid)
- ACV
- Retention 30-90 days post-conversion

Run 4-12 weeks (long enough for cohorts to convert + retention signal).

If new pricing maintains conversion + improves ACV: roll to all new.

**Stage 2: Test with existing-customer renewals (gradual)**

When existing customers renew, present new pricing to a fraction first.
Measure:
- Renewal rate at new price
- Negotiation requests
- Churn

If renewal rate holds: extend.

**Stage 3: Full rollout**

All new customers on new pricing.
Existing customers grandfathered for committed period.
Communicate broadly.

**The tools**:

- **Stripe / Lago / Orb**: pricing-tier flags per customer
- **LaunchDarkly / Statsig / GrowthBook**: feature-flagged pricing
- **Custom DB column**: pricing_tier on each customer

**Anti-patterns**:

- Changing pricing without testing (loose money or lose customers)
- Testing too long (3+ months losing potential revenue)
- Testing without clear success metric
- Rolling out based on small sample (random variance)

**Statistical significance**:

For pricing tests, you typically need 200+ conversions per arm.
Indie scale: maybe 4-8 weeks for that.
Faster only via larger lifts (e.g. doubling price; signal in 50 conversions).

For my testing: [stage]

Output:
1. Test plan
2. Tools
3. Success criteria

The discipline: test small; commit big. 4-week test on 30% of new sign-ups gives you signal; full rollout follows. Lukewarm results: keep testing or revert. Don't half-deploy.

Common Pricing-Cadence Mistakes

Help me avoid mistakes.

The 10 mistakes:

**1. No cadence; "we'll get to it"**
Pricing decays; revenue lost.

**2. Tinkering monthly**
Confuses team and customers; no clear story.

**3. Burying change in announcement**
Customers feel deceived when discovered.

**4. No grandfather decision before announcing**
Field exceptions case-by-case; inconsistent.

**5. Raising without explaining why**
Customer trust erodes.

**6. Ignoring competitor pricing scan**
Drift goes unnoticed.

**7. No testing before rollout**
Either lose money or lose customers.

**8. Too many tier changes at once**
Customer cognitive overload; hard to explain.

**9. Quarterly review without data**
Platitudes instead of signals.

**10. Annual revision without execution**
Plan made; never shipped; another year lost.

For my approach: [risks]

Output:
1. Top 3 risks
2. Mitigations
3. Process changes

The single most-painful mistake: 3 years without raising prices. Inflation alone made you cheaper. Customers expanded usage at original price. Margins compressed. Competitors moved up. Recovery: 2-3 cycles to claw back.

What Done Looks Like

A working pricing-review cadence delivers:

  • Quarterly 30-min checks (calendared; data-driven)
  • Semi-annual 90-min audits with leadership team
  • Annual revision window (Q4 → effective Q1)
  • 1-2 deliberate price changes per year (not 0; not 12)
  • Signal dashboard tracking win rate / NRR / discount rate / tier mix
  • Grandfather policy documented; consistently applied
  • Price changes tested before rollout (40-60% on new sign-ups first)
  • Communication template; honest about why
  • 60-90 day notice for existing customers
  • Average ACV trending up; margin protected; revenue per customer growing without churn spike

The proof you got it right: at year 3, your average customer pays 30-50% more than at launch — and they're happier (more features, better support). New customer ACV is well-positioned. Sales doesn't dread negotiations. Margin holds.

See Also

← PreviousPricing Page OptimizationNext →Product-Led Growth (PLG) Playbook