Outcome-Based Pricing Migration: The Archetype Guide
By Ryan Vanshur
Outcome-Based Pricing Migration: How to Move Off Per-Seat, by Archetype
An outcome-based pricing migration is the pricing project most vertical SaaS teams will run this decade. Per-seat carried the industry for fifteen years. It is ending. Zendesk now charges $1.50 to $2.00 per successful AI resolution. Intercom prices Fin at $0.99 per resolution. On vendor pricing pages that once listed only plan tiers, outcome-based models are now live in production.
Your buyers have already shifted. According to Futurum's first-half 2026 survey, 43 percent of enterprise software buyers prefer consumption-based or outcome-based pricing models, and 27 percent specifically prefer outcome-based. Fewer than one in five still prefer per-seat. The pricing model that was the industry default is now the minority preference.
But here is what most guidance on outcome-based pricing migration misses: the shift is not one transition. It is five different migrations, one per GTM archetype. An enterprise procurement committee, an SMB community of owner-operators, and a self-serve funnel will each absorb "pay for the work, not the login" in completely different ways. Run the wrong migration for your motion and you convert a pricing upgrade into a churn event. Run the right one and you join the cohort that Pilot's study, reported in Monetizely's 2026 pricing guide, found growing revenue and net revenue retention approximately 38 percent faster than pure-subscription peers.
This guide walks you through each archetype's migration, the metering discipline that holds them together, and the exact first moves you need to make this week.
Why Your Outcome-Based Pricing Migration Differs by GTM Motion
The migration shape is not determined by your product. It is determined by your motion.
Your enterprise motion runs on twelve-month sales cycles and budget approvals locked in advance. Your SMB motion runs on referrals from owner-operators who compare notes at trade association dinners. Your product-led motion runs on frictionless self-serve. Same pricing shift, completely different failure modes.
This is why one-size-fits-all outcome pricing advice does not work. A vendor who applies enterprise migration discipline to an SMB market will lose referral trust by making the meter too complex. A vendor who applies PLG migration discipline to enterprise will lose procurement credibility by removing budget predictability. The mistake is not in moving to outcome pricing. The mistake is in moving the wrong way for your archetype.
Before you touch a single price, identify your primary GTM motion. Enterprise, SMB community, product-led growth, embedded fintech, or marketplace. That motion selection determines which path below is yours.
The Foundational Rule: Meter First, Bill Second
Every archetype's migration rests on a single unglamorous principle: run the meter invisibly for a full cycle before you change a single price.
Twelve months for most motions, or however long your customer's operating rhythm actually runs. The product counts completed work the entire time: claims processed, jobs scheduled, filings submitted. Nobody gets billed on it yet. The buyer watches the same dashboard and learns what the agent actually completes in a normal month. Your side learns the volume profile: which accounts are heavy, which are seasonal, where the outliers live.
This is not a stall tactic. This is engineering insurance. Vertical SaaS with embedded payments has run this discipline for fifteen years. You do not launch a take rate by guessing at volume. You watch the volume flow through the platform first, then price against a profile both parties have already stared at for a year.
Skip the metering year and every archetype's migration fails the same way: the first outcome-priced invoice is a surprise, and surprises at renewal have one direction. The interesting part is what happens after the meter runs, because from there the five archetypes diverge completely.
Enterprise: Floor Plus Kicker
Enterprise procurement exists to make spending predictable. The committee budgets annually, the CFO defends a number to the board, and the number cannot move mid-year without a memo nobody wants to write. Pure variable pricing attacks the premise of the entire process.
The migration that works is a committed floor plus an outcome kicker. The floor is a fixed annual commitment sized from the metering year, low enough to be defensible, high enough to cover your platform cost. It buys the buyer predictability and buys you baseline revenue. The kicker prices completed work above the committed volume, at a rate the buyer's own dashboard has already justified.
Migration sequence: Year one, the meter runs silently while the contract stays on the old per-seat model. Year two, the renewal lands with a floor the CFO can commit to the board and a kicker that only triggers when the agent completes more work than the committed baseline. The upside conversation is easy because the buyer's team has watched the completion dashboard all year.
Concrete example: A claims platform's metering year shows an insurer's team clearing 4,000 agent-completed adjudications a quarter, with a seasonal swing of about 15 percent. The floor commits to 3,200 per quarter, priced into a flat annual number the committee can budget. The kicker prices completions above that at a per-claim rate. Because the buyer watched the same dashboard produce those numbers all year, the kicker reads as earned upside instead of exposure.
Three disciplines keep it honest. Meter for the full twelve months before the first outcome invoice, no shortcuts. Let the platform fee carry support and infrastructure so the kicker prices labor and nothing else. And size the floor from observed volume, not from the quota you wish the account supported.
SMB Community: Simple Meter, Built to Share
In SMB community motions, referrals carry 40 to 60 percent of pipeline. The growth engine is one owner telling another owner what they pay and what they get, at a trade association dinner, in one sentence. Per-seat pricing survived that test for years because "I pay per tech" travels. "My pricing varies based on blended utilization tiers" dies before dessert.
The SMB migration has exactly one design constraint: the meter must be peer-explicable. I pay per job scheduled. I pay per claim processed. I pay per load routed. If the owner cannot repeat the meter to a competitor-friend in one breath, the meter is wrong.
There is a second constraint hiding inside the first. The owner has to be able to verify the count against their own records in thirty seconds. Jobs scheduled shows up in their calendar. Claims processed shows up in their carrier statements. The moment your invoice counts something the buyer cannot see in their own books, trust stops forming, and in this motion trust is the distribution channel.
The swap math matters more here than anywhere else. Say a field service shop pays $400 a month today for four seats, and the metering year shows them scheduling about 200 jobs a month. A two-dollar-per-job meter lands them at the same spend for the same usage, and the owner can do that arithmetic on a napkin. The goal of the first metered price is not margin expansion. It is proving the new unit tracks the old bill so closely that switching feels like relabeling, not repricing.
Do not run hybrid pricing here. Floors, kickers, and blended tiers belong in motions with procurement teams to read them. The SMB migration is a straight swap from one simple meter to another simple meter. Margin comes later, from volume growth the meter now captures automatically.
Product-Led Growth: Free Work Proves the Meter
Product-led growth lives on decisions a professional can make alone. A $29 monthly card charge clears without a meeting. "Variable pricing based on outcomes" triggers a conversation with a manager, and a required conversation is the one thing a self-serve funnel cannot survive.
The PLG migration solves this by making the meter itself the onboarding. Give away completed work, not gated features. Ten documents processed free. Twenty charts coded free. By the sixth document the prospect has watched the agent do real labor, seen the counter tick, and priced the value in their own head without a sales call.
Then the upgrade conversation is not "which plan fits your team." It is "how much work do you want done next month," which is a question the free tier already taught them to answer. The meter was proven before money entered the picture, and so the trust problem that kills outcome pricing elsewhere never forms.
The upgrade page changes shape to match. Instead of the three-column plan grid, it becomes a volume slider: the counter shows nine of ten free documents used, and the question on screen is how many the user wants processed next month, priced per document with the rate they have already watched earn its keep. The purchase decision stays solo, stays instant, and stays under whatever card-limit threshold your buyer can clear without a manager.
Your Archetype-by-Archetype Migration Checklist
Print this. Run it before any outcome-pricing design session, in order, and do not skip to question five.
Identify your primary motion. Enterprise, SMB community, PLG, embedded fintech, or marketplace. Write it down. The motion determines the migration. Every other answer downstream changes with this one.
Define the simplest unit of completed work. A claim, a job, a filing, a match, a resolution. If the honest answer is a blended index of several things, you do not have a meter yet. You have a dashboard.
Verify the buyer can audit the count in thirty seconds. Can your buyer check the count against their own records? Does it show up in their calendar, their carrier statements, their operations ledger? If not, the meter will be disputed at renewal.
Name what metering year needs to prove. Write down the volume profile you expect to surface, the seasonality you anticipate, and the edge cases you know will emerge. If you cannot name what the metering year is for, you will be tempted to skip it.
Size the minimum committed floor for enterprise, or zero for SMB. For enterprise, this is the number the CFO defends to the board. For SMB, possibly zero, because the meter is simple enough to trust bare. Deriving the floor from the metering data, not from quota pressure, is what keeps the migration out of the renegotiation pile.
Document the definition of "completed." Write it down and version it, because the first dispute will not be about the count. It will be about what the count means, and so the definition doc becomes the contract exhibit nobody thought they were writing.
Set a metering start date and commit twelve months. Do not shorten this. Do not run it dual with billing. One year of silent metering is the only path to a surprise-free renewal.
Brief your customer success team. They will get questions about the metering dashboard. They need to know the numbers are good, the meter is solid, and the pricing conversation is coming.
Frequently Asked Questions
Q: Can we run metering and billing at the same time in year one?
No. Split billing and metering. The moment you run billing metrics they become contentious, and contentious meters do not survive the first invoice dispute. Run them separately. Let the buyer watch the count for twelve months free. Then start billing against numbers both parties have already lived with.
Q: What if our enterprise buyer wants to lock in price now, before the metering year?
That is when you offer a metered pilot contract, which you were probably offering anyway. One year of metering at the old per-seat rate, with outcome counts visible on the dashboard but unbilled. By year two, the buyer renews on the metered model with floor and kicker. The buyer gets a price guarantee this year plus a fair price next year. You get a full year to prove the meter.
Q: Should we offer a discount if they adopt outcome pricing early?
No. Offering a discount to switch trains signals that the old model is still fine and the new model is an experiment. Price outcome-based meters as the primary option. Do not create a discount tier that signals the meter is secondary.
Q: What happens if our SMB buyer's volume drops after the first year?
Your meter is simple enough to defend. "Your jobs scheduled dropped 30 percent, so your bill dropped 30 percent." That conversation is honest. If you had tried to run a hybrid floor-plus-kicker model for SMB, the floor becomes the negotiation. Simple meters sidestep that entirely.
Q: How detailed should the completed-work definition be?
Detailed enough to survive a dispute with an accountant. Not so detailed that it requires a PhD to verify. A claims platform might define "completed adjudication" as: "An adjudication on which the agent generated the first-pass decision text, the agent applied coverage rules, and the agent routed the claim for final approval, as confirmed by an automated ledger entry timestamp matching the claim record in the customer's system." That is auditable. That is versionable. That is a contract exhibit.
Start Your Outcome-Based Pricing Migration This Week
You do not have to migrate your entire pricing this week. You have to start metering this week.
Pick your primary motion. Open your product roadmap or sprint board and add this task: "Enable outcome counting and dashboard visibility for [primary completed work unit], unbilled, running silent until [date one year from now]."
Brief your customer success and sales teams that this is coming. The meter is not secret. It is transparent. When customers ask why they see completion counts on their dashboard, the answer is: "We are learning your volume profile so we can price fairly in year two."
That is it. You have started the migration. Everything downstream follows from this one unglamorous decision: meter first, bill second.
The vendors who spend the next year learning to count the work, show the count, and price it in their motion's shape will own their categories by 2028. The ones who wait will spend 2027 explaining why they are still counting seats.
Learn More
To understand how outcome pricing breaks each vertical SaaS archetype and the strategic shifts it requires, read the complete framework on outcome-based pricing for vertical SaaS.
Get the Framework
The Vertical GTM Guild operates at the intersection of pricing strategy, GTM motion design, and the shift toward outcome-based business models. Get access to frameworks, playbooks, and operator-led research on how the top vertical SaaS teams are making this transition.
Subscribe to the Guild Letter for weekly operator briefs on GTM, pricing, and the shifts reshaping vertical SaaS. Each issue is grounded in real markets, not pricing-page theater.
Take the GTM AI Readiness Assessment to see where your GTM stands against this pricing shift and get a personalized roadmap for your motion.