Sign in

Proof-Led Offer

Lead with the evidence you already have, arranged so each claim sits next to the artifact that supports it.

Pro moderate Special Offer Structures

What it adds

The AI builder audits your existing documentation, delivered work, metrics exports, and customer communications, then builds a page where evidence precedes assertion at every turn. It converts because skeptical buyers stop searching for the catch when the substantiation is adjacent rather than collected at the bottom. The goal is to shorten the verification loop for buyers who have been burned by overclaiming.

What your builder is told to do

7

The actual instructions, in order.
  1. 1

    Read the supplied evidence files and build an inventory table of every artifact available: what it shows, when it was produced, and whether it is cleared for public display.

  2. 2

    Discard every artifact without a clearance record. Unapproved customer material must never be rendered, even in blurred or anonymized form, unless the source files document that permission.

  3. 3

    For each cleared artifact, write the narrowest claim it actually supports. Resist widening; a screenshot of one workflow supports a statement about that workflow, not about outcomes generally.

  4. 4

    Compose the page as claim-and-artifact pairs. If an artifact is unavailable for a claim you want to make, cut the claim rather than making it unsupported.

  5. 5

    Add provenance metadata to each artifact — date, scope, and what it is — displayed with the artifact rather than in a footnote.

  6. 6

    Include a stated limitations note describing what the evidence does not establish, which increases credibility more than additional proof would.

  7. 7

    Set responsive rules: on mobile each claim-artifact pair is a full-width card with the artifact tappable to enlarge and provenance below it; on tablet pairs render two-up with equal heights; on desktop pairs alternate in a staggered layout with artifacts at readable scale and provenance inline.

Edge cases it handles

5

The things an agent skips when you only say "build a proof-led offer".
  • An artifact contains identifiable third-party data; redact per the source clearance rules or exclude it.
  • Metrics exports are dated well in the past; display the date prominently rather than omitting it.
  • The strongest evidence is under NDA; note the category of evidence that exists without disclosing contents.
  • Multiple artifacts support the same claim; choose the most specific one and note the rest in the assumptions report.
  • No cleared evidence exists at all; build the page around verifiable process documentation and report this constraint explicitly.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • Every claim on the page has a supporting artifact within the same block.
  • No artifact appears without a clearance record in the source files.
  • Provenance date and scope are displayed with each artifact.
  • A limitations note stating what the evidence does not prove is present.
  • No outcome, revenue, or testimonial content is generated that is absent from source files.
  • Mobile, tablet, and desktop each render artifacts legibly with provenance attached.
  • The builder reports which evidence files it used, which were excluded for clearance reasons, and which claims lack support.

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.