---
title: Outcome Based
slug: outcome-based
docTags: 
createdAt: 2026-05-01T18:48:15.279Z
---

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**.

## The Scenario

You are building an **AI-powered customer support platform**.

Instead of billing for:

- API calls
- LLM tokens

You charge customers based on:

**Support tickets successfully resolved**

### Pricing Model

- $2.00 per support ticket resolved

Customers are charged based on results, not underlying usage.

## Core Concept

:::BlockQuote
System Activity (calls, tokens, etc.)  
→ Produces an Outcome  
→ Meter the Outcome  
→ Bill the Customer
:::

The key shift:

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

## Step 1: Define the Outcome

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

In this example:

- **Support Tickets Resolved**

This becomes your **meter**.

## Step 2: Create the Meter

### Where to Configure

- Go to **Meters**
- Click **Create Meter**

### Configure

- **Label**: Tickets Resolved
- **Meter Type**: Count

No dimensions required.

Each time a ticket is resolved, you will send:

- Meter value = 1

## Step 3: Create a Pricing Plan

### Where to Configure

- Go to **Pricing**
- Create a new pricing plan

### Configure

- **Name**: Support Outcome Plan
- **Billing Period**: Monthly

## Step 4: Add a Usage-Based Rate

### Where to Configure

- Add a **Usage-Based** rate

### Configure

- **Meter**: Tickets Resolved
- **Rate Model**: Per Unit
- **Rate**: $2.00

## Step 5: Assign the Plan to a Customer

### Where to Configure

- Go to **Customers**
- Assign the pricing plan to a customer

Once assigned, all metered outcomes will be billed.

## Step 6: Sending Usage (Conceptual)

Each time your system resolves a support ticket:

- Send a meter event with value = 1

If 50 tickets are resolved:

- Total usage = 50

## Example Outcome

If a customer resolves:

- 120 tickets in a month

### Billing Calculation

:::BlockQuote
120 tickets × $2.00 = $240
:::

## Why Outcome-Based Pricing

This model aligns pricing directly with **value delivered**.

Instead of charging for system activity:

- You charge for **what the customer actually cares about**

## Important Distinction

Outcome-based billing does **not replace** tracking underlying usage.

You should still track:

- API calls
- LLM tokens
- Other system activity

These are useful for:

- Cost tracking
- Optimization
- Internal visibility

For internal cost tracking and attribution, see:
[Workloads](docId\:XToRHVsoI2AOK1BZPwfDU)