A landing page has exactly one job: get a specific person to take one specific action. Everything on the page either serves that or dilutes it.

1. Decide the one action

Before any design. Is it "join the waitlist", "start a trial", "book a call", "buy"? One. If you have two, the page has two jobs and will do neither well.

2. Write the copy first

Design around finished words, never the other way round. You need: a headline saying what this is and who it's for, a subhead saying why it's better than what they do now, three to five specific benefits, proof, and the action repeated a few times down the page.

landing-copy.txt
Product: <what it does>
For: <who specifically>
They currently: <the painful alternative>
The one action I want: <action>

Write the copy. Headline under 12 words, saying the outcome not the
category. A subhead. Four benefit lines — outcomes, not features.
Three objections a sceptical visitor would have, and the line that
answers each. Button text that describes what happens on click.

No superlatives, no "revolutionary", no "seamlessly". Give me three
headline options with different angles.

3. Build it

landing-build.txt
Build this as one HTML file with inline CSS. No frameworks, no build.

Sections in order: hero with headline, subhead and button; benefits;
proof; FAQ answering the objections; final call to action.

Requirements: works from 320px up, loads in under a second, real
semantic headings, contrast passes 4.5:1, and the button is reachable
and pressable with a keyboard. Dark and light via prefers-color-scheme.

Here's the copy: <paste>

4. Ship and measure

Static hosting, free. Then the only measurement that matters: of the people who arrived, how many took the action? If it's under a few percent, the problem is nearly always the headline or the fact that the action asks for too much too soon.

Show it to one person for five seconds, then ask what it does and who it's for. If they can't say, the headline isn't finished.