Skip to content

Instantly share code, notes, and snippets.

@eonist
Created June 24, 2026 14:22
Show Gist options
  • Select an option

  • Save eonist/c593bbd4b0f13a6de277d1b4f61dfc2e to your computer and use it in GitHub Desktop.

Select an option

Save eonist/c593bbd4b0f13a6de277d1b4f61dfc2e to your computer and use it in GitHub Desktop.
outcome based pricing

The SaaS industry, particularly companies leveraging AI agents, is increasingly adopting outcome-based pricing models where customers pay for verified results rather than seats or usage limits. This shift typically falls into two categories: charging for specific jobs completed or charging based on tangible financial outcomes. l40

Customer Support and Resolution

Many customer service platforms are leading the transition to outcome-based pricing because the results are relatively easy to measure.

  • Zendesk and Intercom: Both platforms have introduced pricing models where customers are charged per successfully resolved support ticket handled by their AI agents, rather than paying for human agent seats or raw interaction volume. marcabraham
  • Sierra: This AI support company similarly bills businesses based on the number of successful customer query resolutions rather than charging for software licenses or cloud usage. l40
  • Smith.ai: Instead of charging by the hour or by the message, they charge for the specific outcome of generating qualified sales leads. linkedin

Financial and Revenue Impact

Companies that directly impact a customer's bottom line are tying their fees to the monetary value they deliver.

  • Riskified: This e-commerce fraud prevention platform aligns its pricing with direct financial benefits by charging a fee per fraud-free transaction or based on the percentage of fraud charges prevented. marcabraham
  • Flycode: A platform focused on preventing failed payments, Flycode monetizes its service by charging based on the actual amount of revenue it successfully recovers for the customer. marcabraham

Implementation Challenges

While outcome-based pricing guarantees ROI for the buyer, it is notoriously difficult to implement for all SaaS categories. For the model to work, the outcome must be strictly measurable, directly attributable to the software, and largely within the vendor's control. For example, even "resolved tickets" can be debated if a user simply abandons the chat out of frustration rather than satisfaction, making the definition of a successful outcome slightly ambiguous. linkedin

Are you exploring outcome-based pricing for a specific developer tool or CI/CD automation product you are working on?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment