Sign in

Long-Form Sales Letter Funnel

Sell a considered purchase with a complete text-driven sales argument.

Pro involved Offer Conversion

What it adds

Build a long-form sales letter funnel that works the full problem-agitate-solve arc in text, with proof, offer stack, and a checkout close.

What your builder is told to do

4

The actual instructions, in order.
  1. 1

    Extract the promise, the problem, the mechanism, the offer stack, and every supported proof point from the source files.

  2. 2

    Structure the letter: hook, problem, agitation, mechanism, offer, proof, bonuses, risk-reversal, FAQ, and close.

  3. 3

    Add multiple CTA anchors throughout the letter that all route to the same checkout.

  4. 4

    Include a tracking hook for scroll depth and the purchase conversion event, using only supported claims.

Edge cases it handles

4

The things an agent skips when you only say "build a long-form sales letter funnel".
  • If source files conflict, preserve the facts from the newest or highest-authority file and call out the conflict in the final summary.
  • Do not invent claims, testimonials, legal disclaimers, revenue numbers, scarcity, or guarantees that are not present in the provided files.
  • Use generic funnel strategy language only. Do not name or imply endorsement by any specific public marketer or brand.
  • If payment, email, analytics, or CRM integrations are missing, build clear placeholders and document the exact variables or endpoints still needed.

Definition of done

5

Your builder is required to check every one of these before reporting the work finished.
  • The funnel can be built from linked Markdown/source files without requiring the agent to guess the offer.
  • Every page or step has a clear primary action and one measurable conversion event.
  • The output includes page structure, copy blocks, component notes, and implementation tasks.
  • Mobile, tablet, and desktop layouts are accounted for.
  • The agent reports which source files it used and which assumptions remain unresolved.

Related funnel files

How it works

  1. 1

    Copy the link

    Grab the Markdown blueprint URL for this funnel 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 funnel into your app around the offer, 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 funnel file and tell it exactly which source docs and stack to use.