How to Audit Your SaaS Stack for the Coming Outcome-Pricing Wave (A Six-Question Framework)
Zendesk's announcement at Relate 2026 last week was easy to read as a single company picking a clever pricing experiment. It isn't. It's the first big customer-service vendor charging per resolved ticket instead of per agent license, and once one major SaaS player commits to outcome-based pricing for real, the conversation changes for every vendor in your stack.
If you run procurement, finance, or ops at a company that's spent the last decade buying seats, the next twelve months are going to involve some uncomfortable conversations. Here's a six-question framework for getting in front of them before the renewal cycle catches you flat-footed.
1. What is the actual outcome this product produces?
Start every audit here. Most SaaS contracts describe what the product is, not what it produces. The first useful exercise is rewriting the value of each tool in your stack in outcome terms: not "Zendesk is our support platform" but "Zendesk resolves customer issues." Not "Salesforce is our CRM" but "Salesforce surfaces qualifying signals that turn into closed deals."
If you can't articulate the outcome in one sentence per vendor, you're paying for access to a tool category, not for results. That's fine until someone shows up offering to charge you only when the outcome lands. At that point, the access fee starts to look strange.
2. Would my company pay more or less under outcome-based pricing for this vendor?
This is the math question. Do it now for each vendor in your top ten by spend, before they do it for you.
For each one: estimate the volume of outcomes the product currently produces (resolved tickets, closed deals, completed documents, sent campaigns). Multiply by what a plausible outcome price might be (look at Zendesk's $1.50 to $2.00 per resolution as a rough anchor for the customer-comms category). Compare to your current seat or platform cost.
You'll get one of three answers. We'd pay much more (which means the vendor will eventually move to outcome pricing and you'll be paying a lot more for the same thing). We'd pay much less (which means the vendor won't move to outcome pricing voluntarily, but a competitor might). Or roughly the same, which means the audit is still useful because it forces you to count the outcomes for the first time.
3. Is this vendor positioned to make the shift before a competitor does?
The vendors that can plausibly move to outcome pricing share three properties: their outcomes are countable, attributable, and verifiable. Zendesk could do this because tickets are a unit, they happen inside the platform, and the platform can verify whether they were resolved.
Compare your vendor against those three. Marketing automation tools have outcomes (campaigns sent, opens, conversions) but attribution is messy. Project management tools have outcomes (tasks completed) but the work happens elsewhere. CRM has outcomes (deals closed) but the human salesperson is the actual producer. Each gap is a place where outcome pricing is harder to ship cleanly, which gives you a timeline read: vendors with messier attribution will move later.
If your vendor scores low on all three, they probably won't transition for two or three years. If they score high, expect a pricing announcement within the next twelve to eighteen months.
4. What does my contract say about pricing model changes?
Read the renewal clauses with fresh eyes. Most enterprise SaaS contracts have language about "changes to pricing or product structure" with a notice period. That language was written for "we're raising prices by 8 percent." It probably also covers "we're moving from seats to outcomes."
The thing to look for: whether your renewal is locked at the current model for the full term, whether the vendor can convert you mid-term, and what notice they owe you. If your vendor surprises you with an outcome-pricing pivot and you have no contractual protection, you'll be on their new model whether the math works for you or not.
If you're renewing in the next quarter, this is the right week to add a clause about pricing-model stability for the contract term. Most legal teams will push back, but the cost of the clause is small and the value if the vendor pivots is large.
5. Am I overpaying for seats that don't produce outcomes?
The hidden weakness of seat pricing is that it bundles users who produce a lot of outcomes with users who barely log in. You've been paying the same per seat for both. Outcome pricing exposes this immediately because the low-output seats just stop showing up in the bill.
For each tool, run a usage audit: which seats produced 80 percent of the outcomes last quarter? In most categories the answer is uncomfortable. The fix isn't necessarily cutting the low-usage seats, because some of them are still important for occasional work. The fix is recognising that you've been subsidising those seats out of the high-output users' productivity, and that subsidy disappears the moment the vendor switches model.
The action item: identify the seats that contribute less than 10 percent of outcomes, and have a real conversation about whether they justify their share of the bill under either pricing model.
6. If a new entrant launched today at outcome pricing for the same problem, would we switch?
The final question is the gut check. Imagine a competitor of your current vendor launches tomorrow with the same feature set, charging only for verified outcomes (refunded if not delivered). Would you migrate?
If yes, you're paying for something you don't trust to deliver, and the vendor's only protection is switching cost. They'll feel the pricing pressure even before the competitor exists, because the question now lives in your head.
If no, your vendor is producing enough genuine differentiated value that pricing model is secondary. Those vendors are safe. There aren't many of them.
The honest answer for most of your stack will be "we'd switch if the migration wasn't painful." That's the warning sign. Switching costs are the only thing holding the relationship together, and outcome-priced competitors are about to make migration easier on purpose.
What to do with the answers
The output of this audit is a ranked list: vendors that are at high risk of pivoting to outcome pricing soon (where you should add contract protection), vendors that probably won't pivot but where competitors might (where you should keep an eye on the market), and vendors that genuinely produce outcomes you'd happily pay per-result for (where you might even initiate the conversation yourself, because outcome pricing usually saves the buyer money in the first year).
You don't need to act on all of it this quarter. You do need to know where you stand before your CFO asks why a Zendesk-shaped surprise just landed on next year's budget.
For what it's worth, this shift maps cleanly onto why the AI Employee category is interesting: when your worker is an AI you bought on a fixed license with your own API keys, the outcome math is transparent from day one. No seat subsidy, no opaque platform cut, no surprise pricing pivots. The same conversation you're going to have with your SaaS vendors is the one this category was built to skip entirely.
Want to test the most advanced AI employees? Try it here: https://Geta.Team
