What each part of the prompt does
- Current alternative as an input
- People do not compare you with nothing; they compare you with the spreadsheet or tool they already use. Naming that alternative lets the problem section describe a frustration the visitor actually has.
- Fixed section order
- The seven sections follow the questions a visitor asks while scrolling: what is it, do I have this problem, how does it work, why this one, who else uses it, what about my doubts, what now. Each answers one question.
- Placeholders for proof
- Invented testimonials are a common failure in AI landing page copy and a real legal and trust risk. The proof section asks for visible placeholders, so you fill them with quotes and numbers you can stand behind.
- Objections answered on the page
- Four doubtful questions with direct answers handle pricing worries, switching effort and trust before the visitor leaves to search for them. Write down the questions sales calls actually get and add them to the product details.
Variations to try
Same idea, one thing changed.
Two hero openings to test <task>Write the copy for a landing page for [PRODUCT NAME], section by section. Then write a second hero and problem section that leads with the cost of doing nothing instead of the outcome, so I can test the two openings against each other.</task> <product> - What it does, in plain words: [WHAT IT DOES] - Who it is for: [AUDIENCE] - What they use today instead: [CURRENT ALTERNATIVE] - Three things it does better, with proof where I have it: [DIFFERENTIATORS] - The action I want visitors to take: [MAIN ACTION] </product> <sections> 1. Hero: a headline under 10 words that names the outcome, a subheadline of one or two sentences that says how, and the button text. 2. Problem: three short lines describing the visitor's current frustration in their own words. 3. How it works: three steps, each with a short title and one sentence. 4. Features: one block per differentiator, each a heading plus two sentences that link the feature to a result. 5. Proof: placeholders marked "add a real quote" or "add a real number" wherever proof belongs. Do not write testimonials or figures yourself. 6. Objections: four questions a doubtful visitor would ask, each with a direct answer. 7. Final call to action: one sentence and the button text again. </sections> <rules> Write for [AUDIENCE], using their words, not ours. Plain verbs, short sentences, no superlatives such as "best" or "revolutionary". Every claim must come from the product details above. </rules>
Short waitlist page <task>Write the copy for a landing page for [PRODUCT NAME], section by section.</task> <product> - What it does, in plain words: [WHAT IT DOES] - Who it is for: [AUDIENCE] - What they use today instead: [CURRENT ALTERNATIVE] - Three things it does better, with proof where I have it: [DIFFERENTIATORS] - The action I want visitors to take: [MAIN ACTION] </product> <sections> 1. Hero: a headline under 10 words that names the outcome, a subheadline of one or two sentences that says how, and the button text. 2. Problem: three short lines describing the visitor's current frustration in their own words. 3. How it works: three steps, each with a short title and one sentence. 4. Final call to action: one sentence and the button text again. Keep the whole page under 250 words. It is for a waitlist before launch, so there is no proof yet. </sections> <rules> Write for [AUDIENCE], using their words, not ours. Plain verbs, short sentences, no superlatives such as "best" or "revolutionary". Every claim must come from the product details above. </rules>
If the result isn't right
- Copy [AUDIENCE] wording from support tickets or sales call notes; Claude mirrors the vocabulary it is given.
- If the headline names a feature instead of an outcome, reply "rewrite the headline as the result the user gets".
- Paste the finished copy into your page builder before styling it; long sections are easier to spot as text than in a design.