Outcome Based

This guide explains how to implement outcome-based pricing.

Instead of charging for underlying activity (API calls, tokens, etc.), you charge for a business outcome.

You are building an AI-powered customer support platform.

Instead of billing for:

You charge customers based on:

Support tickets successfully resolved

Customers are charged based on results, not underlying usage.

The key shift:

You are metering the result, not the individual steps that produce it.

Start by identifying the business event you want to charge for.

In this example:

This becomes your meter.

No dimensions required.

Each time a ticket is resolved, you will send:

Once assigned, all metered outcomes will be billed.

Each time your system resolves a support ticket:

If 50 tickets are resolved:

If a customer resolves:

This model aligns pricing directly with value delivered.

Instead of charging for system activity:

Outcome-based billing does not replace tracking underlying usage.

You should still track:

These are useful for:

For internal cost tracking and attribution, see: WorkloadsWorkloads