Sign in

Category Comparison Offer

Map the honest tradeoffs across the approaches a buyer is weighing, then show where yours genuinely wins.

Free simple Special Offer Structures

What it adds

Using your feature documentation, pricing sheets, and competitive research notes, the AI builder produces a comparison page that names real tradeoffs including the cases where another approach fits better. It converts because a comparison that admits limits is trusted, and trusted comparisons get shared into buying committees. The goal is to win buyers doing structured evaluation while filtering out those you would fail.

What your builder is told to do

7

The actual instructions, in order.
  1. 1

    Read the supplied comparison and product files and identify the buyer's real alternative set. Compare approaches and categories generically; do not name competitor companies or products unless the source files are authoritative and current.

  2. 2

    Derive the comparison criteria from the buyer's decision, not from your feature list. Use the criteria that appear in supplied sales notes or support tickets.

  3. 3

    Build the matrix with honest cells. Any cell where your approach is weaker must be marked as such; a matrix with no losses is discarded by evaluators.

  4. 4

    Add a "choose the other approach when" section listing the specific conditions under which a different option is the correct choice, sourced from documented churn or disqualification reasons.

  5. 5

    Write a short decision guide beneath the matrix that translates the criteria into two or three concrete buyer scenarios and names the fitting approach for each.

  6. 6

    Cite the basis for every factual cell — documentation, pricing page, or internal test — and date it, so the matrix can be audited and refreshed.

  7. 7

    Define breakpoints: on mobile the matrix becomes a per-approach card stack with criteria as labeled rows and a criterion filter at top; on tablet it renders as a scrollable table with the criteria column pinned; on desktop the full matrix displays with sticky headers and the decision guide adjacent.

Edge cases it handles

5

The things an agent skips when you only say "build a category comparison offer".
  • Pricing for other approaches is opaque or varies; describe the pricing model qualitatively rather than stating a figure.
  • A criterion where you lose is the buyer's top priority; keep it in the matrix and address it in the decision guide.
  • Source competitive notes are stale; mark the cell as unverified rather than publishing an outdated claim.
  • The comparison could be read as disparagement; keep language descriptive and avoid evaluative adjectives about other approaches.
  • Buyers arrive already committed to one approach; provide a direct anchor link to the relevant matrix row.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • Comparison criteria derive from documented buyer decision factors, not from an internal feature list.
  • At least one criterion honestly shows the offer's approach as weaker.
  • A "choose the other approach when" section is present and sourced from documented reasons.
  • Every factual cell carries a basis and a date.
  • No competitor company or product is named without authoritative, current source documentation.
  • Mobile, tablet, and desktop each make every criterion readable without horizontal page scroll.
  • The builder reports which comparison files it used and which cells are unverified or stale.

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.