Seats,Usage Outcomes

Outcome-based monetization.

Outcome billing is a consistency problem, an audit problem and a correctness problem. It's not a product feature.

You define the outcome. We handle the rest.

Outcomes are messy.
Billing them shouldn't be.

An outcome confirmed today can be disputed tomorrow. The billing layer needs to know that.

No more billing corrections at month-end

When a customer disputes a charge, the answer is already there. Timestamped, exact, complete. No manual reconstruction. No cross-referencing spreadsheets.

Finance and sales own the pricing model

Define conditions, set prices, adjust review windows from the dashboard. No sprint. When your sales team needs to offer a new outcome model, it is live the same day.

Any billing audit. Thirty seconds.

Pull the full history for any charge in seconds. Every event, every decision, in order. Show exactly why an outcome was billed or not. To customers, to auditors, to finance.

The integration

The outcome is settled for you.

Three steps. No custom billing logic to write.

Step 1

Configure the contract

Define the condition: what must be true for a charge to fire
Set the price, review window and timeout behaviour
Update it from the dashboard as your pricing evolves

Step 2

Send signals as they happen

One event call per signal from your application
Every signal triggers a fresh condition check
Corrective signals reverse the scheduled outcome in real time

Step 3

Billing fires automatically

When the window closes, the outcome is locked
Charge is added to the next billing cycle
Full audit trail stored: every signal, every decision

Read the docs

Success conditions

Express exactly what a successful outcome looks like

Define the condition in plain logic: what must be true, what must not be, what value must clear a threshold. Price, activity window, review window and timeout behaviour live alongside it in a single contract. Change any of it from the dashboard. No deployment involved.

active_for: 48h
review_window: 24h
price: $0.99
 
conditions: completed
            AND score > 3
            AND NOT disputed
 
on_timeout: confirm

Outcome tracking

Each potential charge has a defined path to settlement

Each potential charge opens when tracking begins. When the success condition is met, it enters a confirmation window. When that window closes, the outcome is locked. Your application sends signals. That's it.

OPEN

condition satisfied

↓

PENDING

review window open

↓

CONFIRMED

condition holds

↓

FAILED

condition broken

Confirmation window

Corrections land before the charge fires

A result can look successful and then fall apart. A correction arrives. A counter-signal comes in late. Every new signal triggers a re-check during the window. If the result no longer holds, the charge is cancelled. The window closes and settles it.

completedcondition satisfiedcharge scheduled

disputedre-checkedcharge cancelled

resolvedre-checkedcharge restored

window closescharge fires ✓

Audit trail

When a customer questions a charge, the answer is already there

Every signal received, every condition evaluation, every state transition. Recorded in order. Pull the history for any outcome and show exactly why it was charged or not. No reconstruction, no guessing.

outcome_4821CONFIRMED

started watching14:00

completed14:22

score 414:23

condition satisfied. review window open14:23

resolved18:04

charged $0.99next billing cycle

Use cases

Coding Agent