Rewrite a weak product description into a conversion-focused landing page brief

What this solves

Raw product notes usually describe features, not why users should care. This prompt forces positioning, proof, objections, and CTA decisions.

Here is the typical pattern of a weak product description: "Our AI meeting note cleaner supports transcript import, generates summaries, creates tasks, and exports to Notion." This tells the reader what the product does, but not why they should use it. The reader has to do all the work — translating features into personal value. Most visitors will not bother.

A conversion-focused brief flips this around. Instead of "transcript import," it should say "Stop losing action items between Zoom calls." Instead of "export to Notion," it should say "Your meeting notes automatically land in your existing workflow — zero extra setup." This prompt automates that translation, producing a structured brief that any copywriter or AI tool can turn directly into page copy.

Test input

Reusable asset

Expected output

A structured landing brief with hero promise, section outline, proof requirements, and first-pass CTA copy.

When you run the prompt against the test input above, expect output structured like this. The target user becomes "Remote team leads drowning in manual note-taking." The painful current workflow surfaces as "Teams spend 20 minutes per meeting rehashing decisions because no one wrote the action items down." The core promise becomes "Your meeting notes, summarized and delivered to Notion in under 60 seconds — without anyone remembering to take notes." Objection handling covers "Will it miss context from my technical discussions?" with a proof point about domain-specific vocabulary handling. Page sections include: hero section (pain + promise), how it works (three steps), social proof placeholder ("X teams saved Y hours"), and CTA ("Stop taking notes. Start shipping.").

How to use this prompt step by step

Step 1: Gather your raw product notes. These can be bullet points from a spec sheet, a pitch deck slide, or internal feature documentation. The more specific the audience information, the better the output will be.

Step 2: Paste the reusable asset prompt into your preferred AI tool (ChatGPT, Claude, Gemini, or a local model). Append your product notes after the prompt — do not interleave them.

Step 3: Review the output. The prompt instructs the model to make reasonable assumptions and mark uncertain ones. Look for the marked assumptions first: if the model assumed a specific pricing model or user persona that does not match reality, correct it and regenerate.

Step 4: Turn the brief into page copy. Each "page section" in the output maps to one landing page section. Write copy against each section, keeping the core promise consistent throughout.

Step 5: Run the output through a readability check. Landing page copy should be at a 6th–8th grade reading level for most B2B SaaS products. If the AI-generated brief uses jargon, simplify it manually.

Comparison: raw notes vs. conversion brief

Here is the before-and-after for the test input to show exactly what changes:

Before (raw notes): Product: AI meeting note cleaner. Features: transcript import, summary, tasks, export to Notion. Audience: small remote teams. This is what most product descriptions look like — a feature list masquerading as messaging. It tells the reader nothing about why they should care or what problem it solves for their specific situation.

After (conversion brief — what the prompt produces):

— Target user: Team leads at 5–20 person remote companies who spend Monday mornings reconstructing last week's decisions from fragmented chat logs.
— Painful current workflow: Recording Zoom, sharing the transcript file, someone volunteers to write notes, notes end up in a doc no one reads, decisions get re-litigated in Slack.
— Core promise: One-click meeting capture → structured notes → Notion sync. No one ever asks "did anyone take notes?" again.
— Proof points: Handles domain-specific vocabulary, preserves speaker attribution, works with Zoom/Google Meet/Teams transcripts.
— Objections: "Will it miss decisions made off-the-record?" → No — imports transcript text, not audio. "Another tool to learn?" → Works inside existing Notion workflow.
— Page sections: Hero (pain headline + 3-step illustration), Benefits (save 5 hours/week, never lose an action item), How It Works (import → summarize → export), FAQ (objections with honest limits), CTA (free trial with no credit card).

The difference is clear: the "before" is feature-oriented and passive. The "after" is user-oriented and strategic. It is not just copy — it is a positioning document that forces you to decide who you are selling to and what argument will close them.

Common mistakes and how to avoid them

Three common pitfalls when using this prompt and how to fix each:

Mistake 1: Vague audience input. If you tell the prompt "Audience: developers," the brief will be generic. Be specific: "Audience: solo freelance developers billing monthly retainers, using Notion for client management, skips meetings when they run long." Specific audience input produces a brief that reads like it was written for one person — because good landing pages speak to one archetype.

Mistake 2: Accepting the first output unchanged. The prompt asks the model to mark assumptions. Read those marks. If the model assumed "users are tech-savvy" but your audience is non-technical managers, regenerate with correction. The brief is a starting point, not a finished asset.

Mistake 3: Skipping the objection handling section. The most effective landing pages address objections before the reader forms them. If the prompt output says "no significant objections identified," your input was probably too vague. Add at least one real objection you have heard from potential customers and regenerate.

Limits and notes

Works best when the product has a clear audience and one concrete use case. It cannot invent real proof; missing proof must be marked. The prompt is also limited by the model's knowledge of your specific market — it will make assumptions about competitor positioning and pricing that may not match reality. Always review the "marked assumptions" section of the output carefully before using it in production. For products with highly technical audiences (developers, engineers), consider adding a note to the prompt to use technical language and avoid marketing fluff.

Related reading

More on product messaging and monetization: