You built an AI tool over a few weekends. Now you need a page that explains it, and you've been staring at "Supercharge your workflow with AI" for an hour. Landing page prompts for AI tools can get you a first draft in minutes, but only if you hand the model your facts. Without them it will write the page every AI landing page already has.
This post gives you a six-block page structure, a set of copy-paste prompts (one per block), and a checklist to review the output before it goes live. The prompts are untested templates: I haven't run them against a model for this post, so treat them as starting points and adjust.
What does a landing page for an AI tool need?
One reader, one job, one action. Everything else is decoration. A small AI tool page usually works with six blocks:
- Hero: who it's for, what they get, one button.
- Problem: the moment the visitor recognises.
- How it works: three steps, ideally with a screenshot or short demo.
- Proof: real evidence only (a demo, a sample output, early user quotes you have permission for).
- Limits and pricing: what it doesn't do, what it costs.
- FAQ: the objections people actually raise.
The limits block is the one most AI pages skip, and it's the one that builds trust. If your tool gets facts wrong sometimes, say so, and say how users can check (fact-checking AI answers has a method you can link).
Step zero: write your fact sheet
Models write generic copy when you give them nothing specific. Before any prompt, fill this in by hand. It takes ten minutes and it is the highest-value part of the process.
PRODUCT FACT SHEET (fill in yourself, do not ask a model to invent it)
Name:
One-sentence job it does (verb + object + for whom):
The one person it is for (job title, situation):
What they do today instead (the real alternative):
Three things it does well (observable, not adjectives):
Three things it does NOT do or does badly:
Input they give it / output they get:
Price and free tier (exact):
Data handling in plain words (what is stored, which model provider):
Real user quotes (word for word, with permission) or "none yet":
Real numbers I can prove (or "none"):
Every prompt below says "use only the fact sheet". That one line prevents most invented claims.
Prompt 1: hero headline and subhead
Untested template.
You are writing the hero section of a landing page for a small software tool.
Use ONLY the fact sheet below. Do not add features, numbers, customers or
claims that are not in it.
FACT SHEET:
[paste]
Write 5 options. Each option has:
- a headline of at most 10 words that says what the reader gets,
- a subhead of at most 25 words that says who it is for and how it works,
- a button label of at most 4 words that names the action (not "Get started").
Rules: no hype words such as "supercharge", "revolutionize", "next-level" or
"effortless". No exclamation marks. Each option must be usable only by this product, not by
a competitor. After the options, point to the one that is most specific and
say why in one sentence.
Why it works: the "usable only by this product" rule forces specificity, and the length caps stop rambling. Pick your option by reading it aloud: if you could swap in a competitor's name, cut it.
Prompt 2: the problem block
Start from a real moment, not a statistic. This prompt asks the model to write from your notes.
Untested template.
Write the "problem" section of a landing page in 80 to 120 words.
Reader: [one person from the fact sheet].
Use this raw material, which comes from real support emails or conversations:
[paste 3 to 5 real complaints or quotes]
Describe the moment of frustration in second person, using concrete detail from
the raw material. Do not invent statistics. Do not mention our product yet.
End with one sentence that names the cost of the current workaround in time or
effort, only if the raw material supports it; otherwise end on the frustration.
If you have no real complaints yet, say that instead of faking them. Talk to five people first. The prompt-engineering for marketing guide covers research prompts for exactly that gap.
Prompt 3: how it works in three steps
Untested template.
Turn this description of how the tool works into exactly three steps for a
landing page. Each step: a 3 to 6 word title and one sentence of at most 20
words. Describe what the USER does and sees, not what the AI does internally.
Do not use the words "AI-powered", "intelligent" or "magic".
DESCRIPTION:
[paste your actual flow: input, what happens, output]
Then suggest, for each step, what screenshot or short clip would prove it.
The last line matters. A screenshot of a real output beats any sentence. Make the shots yourself, using a sample input you're happy to show publicly.
Prompt 4: the limits and honesty block
Models will not volunteer your tool's weaknesses. Ask directly.
Untested template.
Write a "What it doesn't do" section for a landing page, 3 to 5 bullets,
plain language, no apologising. Base it ONLY on the "does NOT do" and
"data handling" lines of the fact sheet below. For each limit, add what the
user can do instead (a workaround or an alternative tool, named honestly).
FACT SHEET:
[paste]
This is the block people quote back to you in a good way. It also reduces refund requests, because buyers know what they are getting. If you take payments, align the page with your refund policy.
Prompt 5: the FAQ
Untested template.
Here are the questions real people asked me about the product (from emails,
DMs or comments):
[paste real questions, or "none yet"]
If real questions exist, write a concise answer to each using only the fact
sheet. If a question cannot be answered from the fact sheet, write
"NEEDS FOUNDER ANSWER" instead of guessing.
If there are no real questions yet, list the 8 most likely objections a skeptical
visitor would have (price, privacy, accuracy, lock-in, who is behind it) as
questions only, with no answers. I will answer them myself.
The "NEEDS FOUNDER ANSWER" instruction is the safety valve. It turns a silent hallucination into a visible gap you can fill.
Prompt 6: critique the whole page
Use a fresh conversation so the model isn't defending its own draft.
Untested template.
Act as a skeptical first-time visitor who found this page from a search.
Read the page below. Reply with:
1. What you think the product does, in one sentence (from the page alone).
2. The first thing you did not believe.
3. The first question you wanted answered that the page does not answer.
4. Any sentence that could appear on a competitor's page unchanged.
5. Any claim that sounds invented, with the sentence quoted.
PAGE:
[paste]
Compare answer 1 with what you intended. If they differ, the page is the problem, not the reader.
Self-review checklist
Run this before you publish. Tick every line yourself; do not ask the model to tick them for you.
- A stranger can say what the tool does after five seconds on the hero.
- Every number on the page is one I can prove today.
- No testimonial, logo, user count or "as seen in" that I did not earn.
- No phrase that would fit on any competitor's page.
- The limits block names at least two real limits.
- Data handling is stated: what is stored, which provider processes it, how to delete.
- Price and free tier are exact, including any usage cap.
- One primary button, same label every time it appears.
- Hype words searched and removed: supercharge, revolutionary, next-level, effortless.
- Page loads and reads on a phone.
- A real person (not me) read it and described it back correctly.
What these prompts won't do
They won't find your positioning. They won't tell you whether anyone wants the product. They won't make a weak product convert, and I'm not claiming any conversion result from them. What they do is turn your facts into clean copy faster and flag the gaps. If you need the business side first, read the AI wrapper SaaS playbook.
Once the page is up, the next problem is getting people to see it. The usual launch venues have their own rules, which we cover in the Product Hunt and Hacker News launch playbook. Note one rule in advance: Hacker News's Show HN page says not to post landing pages, so the thing you show there is the product itself.
