Turn a messy feature list into a one-page product overview
Compresses a sprawling feature list into a one-page argument: problem, mechanism, proof, honest fit, and a single CTA — under 280 words with design notes per section. Because it asks where in the deal the page gets used, the copy matches a post-discovery send instead of reading like a trade-show brochure.
You are a product marketer who writes the one-pagers sales teams actually send after discovery calls. You know the failure mode intimately: someone crams twelve features, three fonts, and zero point of view onto a page and calls it collateral. A one-pager is not a brochure. It's an argument that fits on one page. Produce a complete one-pager draft, under 280 words of body copy total, structured exactly like this: 1. Header: product name plus a one-line value prop (buyer, outcome, mechanism). 2. 'The problem' — three bullet pains written in the buyer's own words, not vendor language. 3. 'How it works' — three steps maximum, each one sentence, mechanism-level not feature-level. 4. Proof block — one customer quote or metric, formatted to stand out. 5. 'Who it's for / who it's not for' — two lines that build trust through honesty. 6. Next step — one specific CTA, not 'contact us'. Also output a design note per section (what to emphasize visually) so whoever lays it out doesn't guess. Banned: feature laundry lists, 'best-in-class', 'end-to-end', paragraphs over three lines, and any sentence a buyer would need your onboarding docs to understand. Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time: 1. What's the product, and what outcome does it deliver? Paste your messy feature list if you have one. 2. Who receives this one-pager, and at what point in the deal — cold, post-discovery, or for a champion to circulate internally? 3. What are the three complaints you hear most from buyers about how they solve this today? 4. What's your strongest single proof point — a quote, a metric, or a named customer? 5. What's the exact next step you want the reader to take? Once you have my answers, write the one-pager. If I give you ten features, pick the three that serve the outcome and tell me why you cut the rest.
How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Paste your raw feature list into question 1 — messy is fine, curation is the model's job.
- 3
Answer question 2 precisely; a cold-send one-pager and a champion-circulation one-pager are different documents.
- 4
Review which features it cut and confirm you agree with its reasoning.
- 5
Hand the copy plus design notes to whoever owns your templates, or drop it into Canva or Figma yourself.
Best practices
Use real buyer complaints from call recordings for question 3 — Gong or Fathom snippets beat your own guesses.
One proof point, prominently placed, outperforms four squeezed-in logos; pick your strongest and let it breathe.
Keep the 'who it's not for' line — reps report it disarms skeptical buyers more than any feature claim.
Version the one-pager per segment by rerunning with a different answer to question 2 instead of making one page serve everyone.
Example: what this looks like in practice
An AE at a 90-person logistics SaaS needs a leave-behind for post-discovery follow-ups. He pastes a 14-feature list, says the reader is an operations director circulating it to a CFO, and gives three real complaints from calls: carrier invoices arrive in six formats, month-end close slips a week, nobody trusts the freight spend number. His proof point: 'Ryder-sized fleet cut invoice processing 70%'. The model keeps three features that serve those pains, cuts eleven, and returns a 260-word page ending with 'Forward this to whoever owns freight spend — then book the 20-minute audit.' The AE reports champions actually forward it, because for the first time the page argues instead of lists.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
Six things: a one-line value prop, the problem in the buyer's words, how it works in three steps, one strong proof point, an honest fit statement, and a single specific next step. Under 300 words total. Everything else — full feature lists, architecture diagrams, company history — belongs in other documents. A one-pager is an argument, not an inventory.
More sales copywriting & assets prompts
Generate an outcome-first value proposition buyers can repeat
Builds a complete value proposition system — primary line, three angle variations, a disqualifier, and channel-ready versions — instead of one throwaway tagline. The interview forces buyer, outcome, mechanism, and proof out of your head first, so the output is positioning you can defend, not word salad you'll rewrite next quarter.
Write a case study from a raw customer interview transcript
Turns a raw, rambling customer interview into a publish-ready case study — result-led headline, snapshot metrics box, four-part story, and verbatim pull quotes — while refusing to invent quotes or numbers. If the transcript is missing a strong metric, it tells you exactly what to ask the customer instead of papering over the gap.
Align your cold email and landing page so the click doesn't break the story
Audits your cold email and landing page side by side, finds where the story breaks between click and page, and fixes the cheaper side with minimum edits. The 'message spine' it outputs becomes a five-line contract both assets obey, so the next person who edits either one doesn't silently reintroduce the mismatch.