Sign in

Performance-Based Offer

Tie the fee to an agreed, measurable result so the buyer's downside is capped before the work even begins.

Free simple Service Offers

What it adds

The builder examines your tracking setup, historical metric records, and past compensation structures to design an offer where part of the price depends on a defined outcome, with baseline, measurement window, and attribution rules made explicit. It converts by shifting perceived risk onto the provider, while the published measurement definition prevents the ambiguity that normally kills these deals.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Inspect the tracking configuration and historical metric exports in the source files, and identify one metric that is unambiguously measurable, attributable to this work, and already being recorded reliably.

  2. 2

    Define the metric on the page in a single precise sentence, including its data source, so there is no interpretive room later.

  3. 3

    Publish the baseline methodology: which historical period establishes the starting point, how it is calculated, and when it is locked. State the baseline as a method, not as a promised number.

  4. 4

    Structure the fee in two visible parts — a base component covering delivery cost, and a variable component triggered by defined movement in the metric — and explain what each part pays for.

  5. 5

    Specify the attribution rules: the measurement window, what counts and what is excluded, how external factors are handled, and who has access to the reporting.

  6. 6

    Describe the qualification requirements honestly, since this model only fits buyers with sufficient volume and working tracking. Make disqualification an explicit, respectful outcome of the fit check.

  7. 7

    Set breakpoints: on mobile show the fee structure as two stacked cards with the measurement definition pinned above them; on tablet present base and variable components side by side with attribution rules below; on desktop use a three-region layout — metric definition, fee structure, attribution rules — visible together without scrolling on a standard wide viewport.

  8. 8

    Provide one next action — request a measurement fit check — and describe exactly what that check evaluates.

Edge cases it handles

5

The things an agent skips when you only say "build a performance-based offer".
  • Tracking is unreliable or incomplete — state that a tracking remediation step must precede the engagement and how it is handled.
  • The metric moves for reasons outside the work — define the exclusion and adjustment rules before purchase.
  • The buyer changes strategy mid-window and disrupts measurement — define what happens to the variable component.
  • Seasonality distorts the baseline — describe the baseline period selection rule that accounts for it.
  • The buyer requests a purely variable fee with no base — state why a base component exists and what it covers.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • Exactly one metric is defined, in one sentence, with its data source named.
  • Baseline calculation is described as a method with a stated lock point, and no target figures are invented.
  • Base and variable fee components are separately visible with distinct explanations.
  • Attribution window, inclusions, exclusions, and reporting access are all stated.
  • Qualification requirements are explicit enough that unfit buyers self-select out.
  • Mobile stacked, tablet side-by-side, and desktop three-region layouts each render as specified.
  • The builder reports which source files it relied on for tracking and metric history, and flags every measurement assumption left unresolved.

Related offer files

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.