Landing Page Copy

A first-time founder's landing page usually fails the same way: it talks about the product instead of the customer, lists features instead of outcomes, drowns the visitor in jargon, and asks them to do five things at once. A visitor decides in seconds whether to stay. This skill writes conversion-first copy - leading with the [ICP]'s problem and the outcome they want, one sharp headline, real proof, the top objection handled, and one call to action.

One page, one job. The page exists to move [ICP] to a single next action - not to explain everything [STARTUP_NAME] can do.

The method

Built on the Founder OS scaffold (High tier). Full section template, formulas and examples in references/landing-copy.md.

Step 1 - Lead with the problem and the outcome, not the product

The visitor cares about their problem, not your features. Open by naming [PROBLEM] in the [ICP]'s own words and the outcome they get - the after-state, the win. Features are evidence for the outcome; they are never the lead. Translate every feature into a "so you can…" benefit before it earns a place on the page.

Step 2 - Write the headline + subhead

The headline is the single most important line on the page. It must, in one read, say what this is, who it's for, and the outcome. The subhead earns the next scroll: it adds the how or the for whom the headline left out. Use the headline formulas in the reference, write 5-10 candidates, and pick the clearest - not the cleverest. Clarity beats clever, every time.

Step 3 - Build the body in order: problem → value → how it works → proof

Lay the page out as a logical argument the visitor can follow at a glance:

• Problem - agitate it just enough that they feel understood.
• Solution / value - the outcome, with features as supporting evidence.
• How it works - 3 simple steps so it feels achievable, not magical. Use the section-by-section template in the reference. Each section does one job and hands off to the next.

Step 4 - Stack proof, with specifics

Claims are cheap; proof converts. Stack what you honestly have: testimonials, named logos, numbers, before/after, guarantees. Specifics beat superlatives - "cut reporting from 6 hours to 20 minutes" beats "saves tons of time." Never fabricate proof or numbers; if you don't have it yet, use the weaker-but-real forms in the reference (founder credibility, a clear demo, a risk-reversal) and earn the strong proof later.

Step 5 - Handle the top objection, then ONE call to action

Name the single biggest reason [ICP] would hesitate (price, trust, effort, switching cost) and answer it - inline or in a tight FAQ. Then close with one call to action, repeated, in the [ICP]'s words ("Start free", "Book a demo", "Get the template"). One page, one job. Competing CTAs split attention and kill conversion.

Output

• Headline + subhead (3-5 candidates, with the recommended pick and why).
• Body copy by section: problem, solution/value, how-it-works (3 steps), proof, objection/FAQ.
• Single CTA wording, in the customer's voice, plus where it repeats.
• [TONE] note: the voice the page is written in, and what to avoid.
• A flag of any proof point that is currently assumed and must be made real before publishing.

Constraints

• Lead with the customer's problem and outcome, never with features or company history.
• One page, one job, one CTA. Multiple competing calls to action lower conversion.
• Clarity over cleverness. If a visitor has to think about the headline, rewrite it.
• No jargon, no hype. Specifics beat superlatives; plain words beat buzzwords.
• Never fabricate proof, logos, or numbers. Use only what's real; mark what still needs sourcing.
• A draft is not a tested page - the only proof a page converts is real visitor behaviour.

Copy-paste version

Act as a sharp conversion copywriter for a first-time founder. Write the page for the CUSTOMER,
not the product. No jargon, no hype, no fabricated proof - flag anything I'd need to make real.
My product: [ONE_LINER]. Who it's for: [ICP]. The problem they have: [PROBLEM]. Voice/tone: [TONE].
Help me:
1. Open with their PROBLEM and the OUTCOME they want - in their words, not my features.
2. Write 5 headline + subhead options that say WHAT this is, WHO it's for, and the OUTCOME, in one read.
   Pick the clearest (not the cleverest) and tell me why.
3. Draft the body in order: problem, solution/value (features only as evidence for outcomes),
   how-it-works in 3 simple steps.
4. Stack the proof I actually have, using SPECIFICS over superlatives. Where I have none, give me the
   honest weaker forms (founder credibility, demo, risk-reversal) and tell me to earn real proof later.
5. Name the #1 objection [ICP] would have, answer it, and close with ONE call to action in their words.
Keep it to one page, one job, one CTA.