Sign in

Outcome-Based Pricing

Tie the price to the result the buyer actually gets, so cost rises only when the value you promised has already shown up.

Pro involved Pricing & Packaging Offers

What it adds

From your delivery data, measurement methods, and historical results, the builder defines a priced unit of outcome, the measurement rule behind it, and the baseline it is compared against. It converts by moving risk off the buyer, since payment tracks a verifiable result rather than effort or access. The goal is closing buyers who reject fixed fees because they cannot predict the return.

What your builder is told to do

7

The actual instructions, in order.
  1. 1

    Read the delivery and measurement source files and list every outcome the operation can actually observe, discarding any that depend on data the buyer would not share or the system cannot verify.

  2. 2

    Select one outcome unit that is countable, attributable, and clearly caused by the work, then write its definition precisely enough that two parties reading it would count the same number.

  3. 3

    Define the baseline against which outcomes are counted, specifying the measurement window, the data source of record, and how pre-existing results are excluded.

  4. 4

    Set the price per outcome unit using the value equation: state the buyer's own value per unit from the source files, then price at a fraction of it that leaves an obvious margin for the buyer.

  5. 5

    Add the commercial guardrails both parties need, including a floor that covers delivery cost, a ceiling or tapering rate that keeps the arrangement viable at high volume, and the billing cadence at which counted outcomes convert to charges.

  6. 6

    Build the reporting surface that shows counted outcomes, the excluded ones with reasons, the running charge, and a dispute path, because trust in the count is what sustains this model past the first invoice.

  7. 7

    Specify responsive behavior: on mobile, lead with outcome count and current charge as two large figures and collapse methodology into an expandable section; on tablet, show the outcome ledger as a scrollable table with the charge summary pinned; on desktop, place the ledger, the running charge, and the measurement definition side by side so any figure can be traced to its rule.

Edge cases it handles

5

The things an agent skips when you only say "build a outcome-based pricing".
  • Outcomes influenced by the buyer's own concurrent activity need an attribution rule agreed before work begins.
  • A reversed, refunded, or cancelled outcome must have a defined clawback window and adjustment mechanic.
  • Exceptional months can produce a charge far beyond the buyer's expectation, which is why the ceiling or taper must exist before launch, not after the first surprise.
  • Measurement outages create gaps in the ledger and require a stated fallback rather than an estimate presented as a count.
  • If the source files contain no historical result range, the pricing per unit is unvalidated and must be flagged as provisional.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • Exactly one outcome unit is defined, with a written definition specific enough to count identically twice.
  • The baseline, measurement window, and data source of record are all stated.
  • A floor and a ceiling or taper are both present and visible to the buyer.
  • The reporting surface shows counted outcomes, exclusions with reasons, and the running charge.
  • Mobile, tablet, and desktop presentations of the ledger each match the specification.
  • No historical result, average, or projection appears that is not present in the source files.
  • The builder reports which source files supplied measurement and result data, and lists every attribution or baseline question it could not resolve.

Related offer files

Pricing & Packaging Offers

Multi-Product Bundle

Combine separate products into one subscription that solves a whole workflow, priced below buying each product on its own.

Build This Offer: Multi-Product Bundle

Pricing & Packaging Offers

Decoy Pricing

Steer buyers toward the plan you want chosen by adding a deliberately weaker option that makes the target look obviously better.

Build This Offer: Decoy Pricing

How it works

  1. 1

    Copy the link

    Grab the Markdown blueprint URL for this offer type.

  2. 2

    Give it to your builder

    Paste it into Claude Code, Cursor, Codex, or whatever AI builder is already working in your app.

  3. 3

    It maps, then builds

    Your agent reads the blueprint first, then builds the offer into your app around the product, audience, and stack.

Works with your stack

These blueprints are written to adapt. They tell the agent to detect your framework, match your existing design system, and use your source files instead of guessing the offer.

Need it tighter than that? Customize the offer file and tell it exactly which source docs and stack to use.