Sales Page Structure Planner
Plan the belief sequence of a long sales page before writing a single line.
Plans a long form sales page as an argument: the ordered beliefs a reader must accept, the section delivering each, the proof required, where price belongs, and the two points most likely to lose the reader.
Ready-to-use prompt
The prompt
Copy it as-is, then swap the bracketed placeholders for your own details before running it.
Role: You are a direct response strategist planning a long form sales page.
Context:
- Offer, price and what is included: {{offer}}
- Audience, and what they have already tried: {{audience}}
- The belief they hold now that would stop them buying: {{blocking_belief}}
- The belief they must hold at the point of purchase: {{target_belief}}
- Proof inventory: {{proof}}
- Guarantee and risk reversal: {{guarantee}}
- Price objection strength, low, medium or high: {{price_objection}}
Task: Return an outline only, no finished copy.
1. The belief sequence: the ordered list of beliefs the reader must accept, from current to purchase-ready
2. For each belief, the section that delivers it, its job in one sentence, and roughly how many words it needs
3. The proof required for each belief, and whether the inventory covers it
4. The order of sections, with the reason this order and not another
5. Where the price is introduced, and what must be established first
6. Objection handling placement, each objection at the point it naturally occurs
7. The two highest risk drop-off points and the transition that reduces each
Rules:
- Never introduce price before the value belief is established, and name that belief.
- Every section must map to exactly one belief, sections that map to none get cut.
- Where proof is missing, mark PROOF GAP rather than planning a section that cannot be written.
- Keep the whole output as structure, do not draft the copy.
- Label unsupported audience assumptions separately from supplied facts.
- Give a total word budget excluding omitted sections.
- Distinguish evidence of process from evidence of customer outcomes.
Finish with: the shortest version of this page that would still work, and which sections it keeps.Estimated results
Editor's note
Why this prompt matters
Long sales pages are usually written forward, section by section, and the result is length without progression — the reader is 2,000 words in and holds the same beliefs they arrived with. The alternative is to design the argument first. This prompt produces structure only and deliberately refuses to draft copy, because the useful work here is deciding which beliefs must change, in what order, and what evidence each one requires. Where that evidence does not exist it says so, which converts a writing task into a much more honest content-collection task.
Anatomy
Prompt engineering breakdown
Role
Context
Goal
Constraints
Output format
What you'll get
Expected output
Scenario and planning inputs
Hypothetical offer: a $600 guided proposal workshop for independent consultants, including two working sessions, a proposal template, and feedback on one draft. Readers have tried downloading templates but still struggle to explain their fees. Blocking belief: “A better proposal is just prettier formatting.” Target belief: “Structured guidance can help me explain scope and value clearly enough to justify this purchase.”
Assumed proof inventory: an annotated sample proposal, the workshop agenda, and a facilitator walkthrough. No testimonials or revenue results. Assumed guarantee: a refund requested before the first session; no performance guarantee.
Belief sequence and section plan
| Belief to establish | Section and its job | Words | Proof coverage | |---|---|---:|---| | 1. My difficulty may be the argument, not the layout. | Diagnosis: distinguish presentation problems from unclear scope and value. | 150 | Annotated sample illustrates the distinction, not its prevalence. | | 2. There is a concrete way to improve that argument. | Mechanism: map the proposal decisions taught in the workshop. | 200 | Agenda and walkthrough cover the process. | | 3. I can see what better reasoning looks like. | Demonstration: explain the reasoning behind selected sample annotations. | 250 | Sample supports demonstration, not sales outcomes. | | 4. Guided application offers enough value to consider paying. | Offer fit: connect sessions, template, and feedback to those decisions. | 200 | Agenda confirms delivery; sample makes the intended output tangible. | | 5. I understand the cost and can judge affordability. | Price: present $600 alongside inclusions and participation requirements. | 100 | Offer details cover cost; earnings claims remain unsupported. | | 6. I understand the remaining commitment and risk. | Decision: clarify refund limits and the next step. | 150 | Written guarantee terms required before publication. |
Order, price, and objections
Diagnosis precedes mechanism because another template pitch would reinforce the blocking belief. Demonstration precedes inclusions so the package has a meaningful reference point. Price follows belief 4, the explicit value belief; more scrolling alone cannot establish it.
Place “I already have templates” at mechanism, “Will this win clients?” at demonstration, and affordability at price. Mark client-win claims PROOF GAP; omit any results section rather than imply evidence exists.
Highest-risk transitions
- Mechanism → demonstration: move from abstract process to one annotated decision.
- Offer fit → price: connect each inclusion to its practical use before asking readers to evaluate cost.
Shortest viable page
Keep all six beliefs; compress diagnosis and mechanism, use one demonstration, and shorten inclusion details. Cut repetition, not the evidence or refund limits.
Under the hood
Why this prompt works
Mapping each section to exactly one belief gives you a deletion rule, which is what long pages lack. If a section maps to no belief it goes, regardless of how well written it is. Deriving price placement from the value belief rather than from a scroll position fixes the other standard error — pages that name a price before the reader has any framework for judging it get abandoned at that line, and the analytics show a drop-off without explaining it. The PROOF GAP output then prevents the worst outcome: a beautifully argued page resting on evidence nobody has.
Model fit
Best AI models for this prompt
Claude
Best here. Strongest at sequencing beliefs and most honest about proof gaps.
ChatGPT
Reliable structure but occasionally begins drafting copy; restate the outline-only rule.
Gemini
Useful when you paste a competitor sales page and want to compare argument order.
When to use
- Before briefing a writer on a 1,200-word-plus sales page.
- When observed mid-page exits suggest an argument worth investigating.
- Before assigning different sections to multiple writers.
- When existing proof must support a newly positioned offer.
When not to use
- For short landing pages; use a landing-page copy prompt.
- With no proof; collect usable evidence before planning persuasion.
- While pricing or inclusions are still changing.
- To diagnose exits conclusively; use analytics and customer interviews.
- For regulated claims without qualified human review.
Get more from it
Pro tips
- 1
Write the belief sequence first; cut sections that merely lengthen it.
- 2
Turn each PROOF GAP into an evidence-collection task before drafting.
- 3
Build the shortest viable version first; extend only for unresolved objections.
- 4
Place price after the named value belief, never at a predetermined scroll depth.
- 5
Separate illustrative samples from customer outcomes in your proof inventory.
- 6
For a second pass, challenge the weakest belief transition without adding sections.
- 7
Supply actual refund exclusions; otherwise risk-reversal planning may promise too much.
Don't ship this
Common mistakes
✗ Writing the page forward, section by section.
Fix — Sequence the beliefs first; the section order follows from them.
✗ Keeping a well-written section that maps to no belief.
Fix — Apply the deletion rule — length is not the goal.
✗ Planning sections you have no evidence to support.
Fix — Collect the proof flagged in the gap list first.
People also ask
Frequently asked questions
Q.Why does this prompt refuse to write copy?
Because the failure in long sales pages is argument, not prose. Planning the belief sequence first gives you a deletion rule for sections and a research brief for evidence, and drafting too early hides both.
Q.What is a PROOF GAP?
A belief the page must establish that your current evidence cannot support. It marks work to do before writing rather than a section to write around, which is what usually happens instead.
Q.Where should the price appear?
After the belief that makes the price make sense. The prompt names that belief explicitly, so price placement follows the argument rather than a fixed scroll depth.