The Pricing Migration Sequence: An 18-Month Quarterly Playbook

The piece I wrote on per-outcome pricing was the framework. This essay is the implementation manual.

I keep getting asked the same question by CPOs and CFOs at SaaS companies running $10M to $50M in ARR. "OK, we agree per-outcome is the future. We agree hybrid is pragmatic. But what does the actual eighteen months look like? Quarter by quarter. What do I do first? What do I tell the board? What does the gross margin curve look like? What breaks?"

This is that essay. I'm going to walk through the sequence I run, the way I run it, with the math and the political realities included.

For specificity, I'll use a hypothetical $20M ARR SaaS company as the worked example. Per-seat pricing, 110% NRR, 80% gross margin, 30 sales reps, mid-market and enterprise mix. Most of you reading this are within shouting distance of that profile. If you're materially smaller or larger, the sequence still applies; the absolute numbers change.

The short version

Eighteen months from "we have a pricing problem" to "we run hybrid outcome pricing." Six quarters. Each one has specific commitments, specific failure modes, and specific conversations. Q1 is internal alignment and the lead customer pilot. Q2 is hybrid live for new customers. Q3-4 is the migration of strategic and mid-market accounts in cohort waves. Q5-6 is the long-tail migration and the legacy tier sunset.

The gross margin trough is real and bottoms out around month 12 at about 58-65%, depending on how cleanly you execute. Recovery to 70%+ happens in months 18-30. The board has to know this curve before month one. The CFO has to be your closest partner. Ignore either and the migration fails politically before it can succeed financially.

The four conversations that decide whether this works: CFO (the trough math), CRO (comp rewrite), Board (pre-selling the trough), Lead Customer (the reference). Each takes six to eight weeks. None can be skipped.

This is the playbook.

Why per-seat is structurally dying

Quick frame so we agree on the problem.

Per-seat pricing assumes humans need licenses. AI agents collapse that assumption. One human-plus-agent does the work of three humans. If your pricing is tied to seats, your revenue shrinks the more value you deliver. That's not a temporary headwind. That's a structurally inverted incentive between your business and your customers' efficiency goals.

The market is responding. Sierra hit $100M ARR in two years on pure outcome pricing. Intercom moved Fin to $0.99 per resolution. HubSpot dropped AI pricing to $0.50 per resolution in April 2026. Per-seat as a share of SaaS revenue went from 21% to 15% in twelve months. Forty-three percent of SaaS companies already run hybrid models; analysts project sixty-one percent by year-end.

You don't get to decide whether this is happening. You only get to decide how cleanly you'll handle it.

The eighteen-month sequence

Quarter 1 (months 1-3): Internal alignment and the lead customer pilot

This quarter is invisible from outside the company. Internally, four things must happen.

1. Build the unit economics model. For each major SKU, model: current per-seat revenue per customer, projected per-outcome revenue per customer, current gross margin, projected gross margin per outcome (after inference cost, escalation labor, infrastructure). Run three scenarios: conservative, expected, aggressive. Most companies discover the per-outcome price is 1.5x to 3x the per-seat price for the same workload. That ratio is your transition opportunity.

2. Run the four conversations to first commitment.

• CFO: walk the gross margin trough math. Get them to commit to the trough as a planned investment, not a surprise.
• CRO: present the new comp plan in draft. Get their feedback. Don't finalize yet.
• Board: schedule a 30-minute slot in the next quarterly review titled "Pricing model evolution." Pre-read includes the trough math.
• Lead customer: identify the one strategic account most aligned with outcome pricing. Schedule a CPO-to-counterpart conversation.

3. Pick the lead pilot and the lead SKU. One workflow. Bounded, frequent, measurable. Support resolution. Sales meetings booked. Code review acceptances. The pilot SKU is the one you've already shipped that has clear outcome metrics.

4. Draft the contract template. Five things in writing: unit definition, dispute window, arbitration mechanism, committed minimum, price ceiling. Get general counsel involved early. The template will go through three drafts; budget six weeks.

Failure modes in Q1: the CFO is unconvinced and you proceed anyway. The lead customer pilot is too narrow to teach you anything. The unit definition is fuzzy and creates billing disputes in Q3.

Quarter 2 (months 4-6): Hybrid live for new customers

The lead pilot is signed. The unit economics model has held up. The board has reviewed the pricing memo and committed to the trough. Now you flip the switch for new business.

1. Hybrid pricing goes live for new customers. Platform fee plus per-outcome overage. Committed minimums protect the forecast. The pricing page shows both. Sales is trained on the new motion.

2. Comp plan rewrite is published.

• New deals on the legacy SKU earn 50% of historical comp. (You want salespeople to think about the outcome alternative.)
• New deals on the successor earn 150% of equivalent ACV. (You want them excited.)
• Renewal accelerators on legacy disappear.
• Migration accelerators on successor are introduced.

The CRO will fight the 50% legacy comp number. Hold the line. The comp asymmetry is the lever that prevents the legacy product from quietly winning the next eighteen months.

3. Lead customer pilot graduates to public reference. With permission, the lead customer's results become a marketing asset. Logo. Quote. Outcome numbers. This single reference will close 30% of your enterprise deals in the next four quarters. Do not skip the work to make it a real reference, not a marketing fluffpiece.

4. Customer success retraining begins. CS leaders learn the dispute mechanism, the new SLAs, the outcome-quality dashboard. The CS organization will absorb most of the operational pain of the transition; train them before the pain arrives.

5. Board update. First public board acknowledgment of the trough. Three slides: the pricing change, the trough curve, the leading indicators (outcome volume, gross margin per outcome, lead customer reference progression). Establish that you'll report these numbers every quarter from now on.

Failure modes in Q2: comp plan rewrite gets watered down to keep the CRO happy, and salespeople keep selling legacy at full price. Lead customer reference is delayed by procurement and you lose six weeks of marketing momentum. CS team is not retrained and you create a dispute pipeline you can't service.

Quarter 3 (months 7-9): Strategic account migration begins

The new pricing motion is operating for new business. Now you start migrating existing customers. This is where the transition starts to feel real and where most companies start to lose their nerve.

1. Wave 1 migration: top 20 strategic accounts. The CPO, CRO, and account team meet with each strategic customer. Bespoke commercial conversation: here's how the new pricing works, here's the path for your account, here's what we'll do to make this clean. Each call takes 90 minutes plus follow-up. Twenty calls is a sixty-day project.

These are the customers that, if they leave, drop you 25%+ in ARR. The CPO has to be in every one of these conversations personally for the first quarter. Delegating this is the single biggest mistake I've seen.

2. The legacy product's roadmap shrinks. Engineering is now allocated 70/20/10 to successor / migration tooling / legacy maintenance. Legacy stops getting feature work. Legacy customers start to notice. Some will accelerate their migration. Some will start exit conversations with competitors. Plan for both.

3. Migration tooling ships. Self-service dashboards that show the legacy customer their projected outcome-pricing bill. A one-click migration flow that sets a committed minimum based on their historical usage. A FAQ that addresses the most common objections. The strategic accounts get bespoke; everyone else gets self-service. Build the self-service tooling now because Wave 2 will need it.

4. Pricing experiments begin on the agent product. Inference costs are dropping faster than you expected. Should you pass the savings to customers or hold the price? Run two cohorts at slightly different price points and measure conversion. The Jevons cliff is real; you'll be making this decision repeatedly over the next two years.

5. The gross margin trough is now visible on the financials. Q3 closes with blended gross margin somewhere around 65-68%. Down from 80% but not catastrophic. The board update notes the trough is on track. Leading indicators (outcome volume, migration percentage) are climbing. Stay calm publicly.

Failure modes in Q3: strategic account migration meetings are delegated to account managers and the customers feel underweighted. Legacy roadmap shrinks too fast and customers churn before migration tooling is ready. Pricing experiments are done sloppily and the data is unusable.

Quarter 4 (months 10-12): Mid-market migration and the trough bottom

Quarter four is the hardest. The trough is at its deepest. The team is tired. The legacy revenue is visibly shrinking. The board is twitchy. The CFO is asking detailed questions.

1. Wave 2 migration: mid-market accounts. Structured email campaign, webinar series, self-service migration tool. The pace is faster than Wave 1; you're moving 200-500 customers in a quarter. CS bears the brunt of questions and disputes.

2. The legacy tier sunset date is announced. Internal first (board and exec team), then external. Sunset is 12 months out. Legacy customers have a year to migrate or churn. The announcement crystallizes the urgency and accelerates Wave 2.

3. Q4 board update. The trough is at its bottom. Blended gross margin around 58-62%. Board members will ask whether the transition is working. The answer is in the leading indicators: outcome volume up X%, percent of legacy revenue migrated up Y%, gross margin per outcome up Z basis points, lead customer expansion revenue at $W. Show the recovery curve. Walk through what month 18 looks like. Maintain the narrative.

4. The CFO's seasonal forecast. Outcome revenue is now variable in a way the legacy revenue wasn't. The CFO needs to model seasonality, customer cohort behavior, and inference cost curves. This is where the CFO's tooling has to upgrade. Most companies discover their FP&A stack is not built for variable revenue at this point.

5. Internal morale management. Fourteen months in, the team is asking whether this is working. Show them the leading indicators. Celebrate the strategic account references. Run an internal Q&A. The team's belief in the transition is now load-bearing for execution.

Failure modes in Q4: the board sees the trough and panics. The CFO's models can't keep up with variable revenue. Internal morale cracks. The CRO starts hinting that "maybe we should slow this down."

Quarter 5 (months 13-15): Trough recovery starts

Pricing tooling is mature. Mid-market is mostly migrated. The agent product's outcome volume has scaled enough that inference costs are amortizing. Recovery starts being visible.

1. Wave 3 migration: long tail. The remaining legacy customers (small accounts, low ACV, high count) get the public announcement and a clear deadline. Self-service only. Some will churn. That's expected. The unit economics of the long tail were marginal anyway; losing the bottom decile improves blended margin.

2. Outcome quality investments. With volume scaled, you can now invest in outcome quality (better evals, better routing, better escalation handling). Each quality improvement compounds margin: better quality means fewer disputes, faster customer onboarding, lower CS load.

3. Pricing experiments on the agent product mature. You now have data on price elasticity at scale. Decide: hold prices and capture margin as inference falls, or pass savings and capture share. The right answer depends on competitive position; both are defensible. Document the decision.

4. CS organization is rebuilt around outcome quality. The CS team that survived the trough is now the team that owns outcome SLAs, dispute resolution, and customer education. CS becomes strategic again, with senior leaders and a real budget.

5. Q5 board update. Trough is past. Blended gross margin recovering toward 65%. Outcome revenue is now 60%+ of total revenue. The narrative shifts from "we are managing the trough" to "we are scaling the new model." The board's questions get easier.

Failure modes in Q5: long-tail migration is sloppy and you absorb a wave of negative public reviews. Outcome quality investments get deprioritized for new feature work and your dispute rate stops improving.

Quarter 6 (months 16-18): Sunset and the new normal

The legacy product has a public sunset date six months out. The migration is mostly complete. The agent-native product is the company's primary revenue driver.

1. Final migration push. Customers still on legacy get personal outreach. Some will migrate. Some will churn. Some will negotiate one-year extensions on legacy at premium pricing (you should accept these; they're cash and they end on a known date).

2. Sunset preparation. Engineering builds the actual sunset tooling: data export, account closure, final billing. Legal reviews customer contracts to ensure clean termination. Finance models the post-sunset P&L.

3. Post-sunset reorg planning. The maintenance team's roles end at sunset. Plan the reorg now. Some maintenance engineers transition to bridge or successor roles. Some get severance. Communicate transparently in month 17 with sunset in month 21 (giving people four months of runway).

4. Q6 board update. Trough is past. Gross margin at 70%+. Outcome revenue at 75%+ of total. NRR on the agent product is 130%+ (because outcome customers expand naturally with usage). The narrative is now: "we are the company that successfully migrated. Next chapter."

5. The new operating normal. The dual transformation operating model collapses to a single operating model focused on the agent product. The two clocks become one clock again. The successor team becomes the entire team. The maintenance team has graduated.

The four mandatory conversations, in detail

I called these out at the top. They're worth a more detailed treatment because they're where most pricing migrations actually live or die.

The CFO conversation

Three sessions, six weeks total.

Session 1 (week 1-2): present the unit economics model. Show the per-seat baseline and the per-outcome scenarios. Show the gross margin trough curve. Walk through the assumptions. The CFO will probe the assumptions hard. Welcome it. The conversation needs to end with both of you agreeing on the assumptions or with you returning with better data.

Session 2 (week 3-4): present the new comp set for board reporting. Pure-SaaS comps are wrong; the right comp set is companies in transition (Intercom, HubSpot, Atlassian, Sierra, Service-as-Software peers). The CFO commits to retraining the board on the comp set during the next quarterly review.

Session 3 (week 5-6): agree on the leading indicators that will go in every board deck for the next 24 months. Outcome volume, gross margin per outcome, percent migrated, lead customer expansion, NPS on the successor. The CFO and CPO co-author the format.

If you finish week six and the CFO still isn't bought in, do not proceed. Escalate to the CEO. The transition without the CFO has a near-zero success rate.

The CRO conversation

Two sessions plus a comp plan rewrite.

Session 1 (week 1-2): walk the upside math. Outcome pricing is typically 1.5x to 3x the per-seat price for the same customer. The CRO's quota math actually gets better, not worse, on outcome deals. Frame the comp plan rewrite as a way to make the CRO and the sales team the heroes of the new motion.

Session 2 (week 5-6, after comp draft): present the rewritten comp plan. Legacy comp at 50% of historical, successor comp at 150%, renewal accelerators on legacy gone, migration accelerators on successor introduced. The CRO will push back on the 50%. Hold the line. The asymmetry is the lever. If you yield, the legacy product will keep selling at full velocity.

The CRO also has to commit to the lead customer reference work. The reference is a sales asset. The CRO has to budget account team time to make the reference real, not just marketing-acceptable.

The board conversation

One quarterly slot, recurring forever.

Quarter zero (before any external move): a 30-minute slot in the quarterly review titled "Pricing model evolution." The pre-read is your unit economics memo. The presentation walks the trough curve, the leading indicators, the timeline, the lead customer pilot plan, and the strategic rationale.

The board's typical questions:

• What's the worst case? (Answer: the trough is 12 points deeper and 6 months longer. We've stress-tested. Cash position is X.)
• What do our investors think? (Answer: we briefed lead investor first, here's their reaction.)
• How does this affect the IPO timeline / fundraising / acquisition strategy? (Answer prepared in detail before the board meeting.)
• What if the agent product doesn't work? (Answer: we have a kill criteria. Here it is. Here's the cost of killing.)

After quarter zero, every quarterly board update has the same structure: trough position, leading indicators, what changed, what's next. The format is boring on purpose. Boring is what builds trust through a transition.

The lead customer conversation

One strategic account. Two-month process.

Week 1: CPO-to-counterpart call. Not a sales meeting. A working session. Walk through the new pricing model, the lead customer's specific workflow, the projected outcome math for their account. Ask honestly: would this be better for you? If yes, what would you need to feel comfortable being first?

Weeks 2-4: contract negotiation. Use your contract template. Adjust for the customer's specific concerns. Get the legal teams aligned. Bespoke commercial terms (e.g., a price cap for the first year, an extended dispute window) are appropriate; deviations from the unit definition are not.

Weeks 5-6: pilot launch. Run on outcome pricing for one workflow. Track everything. Build the operational muscles you'll need at scale.

Weeks 7-8: review and reference work. Document the customer's experience. Get explicit permission for case study, logo use, and one keynote-ready quote. The reference becomes the asset you use to sell the next twenty deals.

If the lead customer isn't right for outcome pricing, do not proceed. Find a different lead. The wrong lead customer reference will haunt you.

What goes wrong most often

Five failure patterns I've seen repeatedly.

One: the CFO conversation gets skipped or rushed. The CPO assumes the CFO will support the move because the strategy memo is sound. They don't run the unit economics jointly. The CFO sees the trough hit the financials in Q3 and panics. The board panics. The migration slows. Everything reverses by Q4. Solution: do the CFO sessions first, before anything else.

Two: the comp plan gets watered down. The CRO objects to the 50% legacy comp. The CPO compromises to keep the relationship working. The compromise means salespeople keep selling legacy at velocity. By Q3, the legacy revenue isn't shrinking on the planned curve and the trough takes longer than expected. Solution: the CEO has to hold the line. The CPO alone cannot.

Three: strategic account migration is delegated. The CPO is busy. The 20 strategic account calls get pushed to account managers. The customers feel underweighted. Some accept the new pricing under protest; others start competitor evaluations. Solution: the CPO has to be in the first 20 calls personally. There's no shortcut.

Four: the contract template is not rigorous. The unit definition is fuzzy. Disputes pile up in Q3-4. CS is overwhelmed. Customer trust takes a hit. Solution: invest the six weeks of legal review in Q1. The template is your operational backbone.

Five: the trough is not pre-sold to the board. The board sees the gross margin compress and assumes the transition is failing. They demand a pause. The pause is operationally fatal because once you stop migrating, the comp asymmetry stops working and salespeople return to selling legacy. Solution: pre-sell the trough in quarter zero. Reinforce every quarter. Make the trough boring.

The recovery curve, with numbers

The most useful thing I can leave you with is the actual shape of the gross margin curve, plus the leading indicators that should track alongside it.

Months 1-3: 78-82% gross margin. Pricing is stable. Migration hasn't started. This is your baseline.

Months 4-6: 73-77% gross margin. New customers are on hybrid. Inference costs are landing. Outcome volume is small. The trough begins.

Months 7-9: 65-70% gross margin. Strategic account migration is in progress. Migration tooling investment is high. Engineering is split. Outcome volume is climbing but inference per outcome is still high (you haven't optimized prompts and routing yet). Trough deepens.

Months 10-12: 58-65% gross margin. Bottom of the trough. Mid-market migration is happening at volume. CS load is highest here. Inference cost optimizations start helping. Some early-stage prompt tuning gains visible.

Months 13-15: 62-68% gross margin. Recovery begins. Outcome volume has scaled enough that inference is amortizing. Quality investments compound. Disputes are dropping.

Months 16-18: 67-72% gross margin. Long-tail migration done. Sunset announced. Outcome revenue dominates. Inference costs continue to drop industry-wide.

Months 19-24: 70-75% gross margin. New normal. Outcome pricing is the company's primary model. Margin is structurally lower than mature SaaS but applied to higher absolute revenue (because outcome pricing captured value the SaaS price was leaving on the table).

Leading indicators that should be improving the whole way:

• Outcome volume per customer (climbing)
• Gross margin per outcome (climbing as prompts and routing improve)
• Percent of legacy revenue migrated (climbing toward 100%)
• NPS on the successor product (steady or climbing)
• Lead customer reference expansion revenue (climbing)
• Dispute rate (falling)
• Customer migration to legacy churn ratio (climbing)

If three or more of these are flat or falling at the same time, the transition is in trouble and needs intervention. Run the quarterly reality check from the dual transformation essay.

What to try this week

If you're still on per-seat and you're considering the move, run this exercise on a single page before Friday.

1. Pick one of your major SKUs. The one that drives the most revenue, or the one most clearly aligned with an outcome unit.
2. Define the outcome unit in one sentence. "A resolved support ticket where the customer didn't escalate within 48 hours." "A qualified meeting booked through our system that converts to a discovery call." Get specific.
3. Estimate per-customer outcome volume per month.
4. Multiply by a price that's 5-15% of the customer's alternative (typically: human labor cost or competitor's per-seat price multiplied by efficiency gain).
5. Compare to the customer's current per-seat spend.

The ratio is your starting point. Now ask the four questions:

• Has the CFO seen this math?
• Has the CRO seen the new comp implications?
• Has the board been pre-sold on the trough?
• Is there a lead customer who would be willing to pilot?

The answers tell you exactly what your next quarter looks like.

The pricing migration is not a marketing exercise or a finance exercise. It is the most operationally exposing thing a company can do in the AI era. Run the sequence with discipline, or get displaced by someone who did.

---

The Pricing Migration Quarterly Tracker (the actual spreadsheet I use with operating teams) is at /toolkit/pricing-migration-quarterly-tracker. The Margin Recovery Curve Model is at /toolkit/margin-recovery-curve-model. The pillar handbook chapter that goes deeper on contract terms and dispute mechanics lives at /handbook/pricing-migration-18-month-playbook. The companion essays on cannibalization and dual transformation are linked from /cpo.

Further reading

• Sierra reaching $100M ARR on outcome pricing (Bret Taylor interviews)
• HubSpot moving AI pricing to per-resolution (SaaStr)
• Atlassian and HubSpot Join Shift From AI Flat Fees (The Information)
• The 2026 Guide to SaaS, AI, and Agentic Pricing Models (Monetizely)
• The Inference Cost Paradox (Artur Markus)
• L.E.K. Consulting: How AI Is Changing SaaS Pricing