# Create a buyer-ready one-pager from my SELLER.md

Use the SELLER.md I provide or that is already available in this conversation. Treat it as sales context, not proof that every claim is current. If it is missing, ask me to attach it; do not pretend to have read it. Use relevant buyer context and source material already supplied for this task. Ask permission before retrieving additional connected data. Do not publish, send, or update any external system.

## Make the decision clear

Create an editable one-pager for one audience, one situation, and one next step. Use any audience, deal stage, purpose, and format I have already supplied. Otherwise, default to a product-introduction leave-behind for the primary buyer in SELLER.md, and state that assumption in a separate review note. Do not invent a specific prospect or a discovery conversation. Ask a question only if an unresolved choice would materially change the story or make a useful draft impossible.

## Apply my judgment

Follow the file's approved voice, selling standards, prohibited claims, buyer treatment, and CTA preferences. Keep declared standards separate from unconfirmed inferences. Translate the relevant value map into a specific buyer problem, the work the product does, and why that work matters. Do not summarize every section of SELLER.md or include internal qualification criteria, seller weaknesses, private account details, or confidential strategy.

Use plain language. Avoid generic AI benefits, stacked slogan fragments, repeated sentence openings, manufactured urgency, and formulaic “not X, but Y” lines unless I explicitly prefer that style. A short, direct explanation is better than a wall of copy.

## Keep claims defensible

Separate positioning from verified capability and measured customer results. Never turn a roadmap, concept, code-level check, or old marketing page into a claim of current availability. Do not merge sibling products or their offers. Surface conflicting scope or pricing in the review notes instead of choosing silently.

Use only proof explicitly supported and approved for external use. Never invent customers, logos, quotes, percentages, savings, buying intent, prices, delivery commitments, or implementation timelines. If proof is missing, omit the proof section and propose an evaluation approach without implying that it is an available offer. Keep missing facts and approval requests out of the buyer-facing copy. If a material capability cannot be verified, omit it or label the entire artifact as a concept draft rather than implying a live product.

## Deliver the draft first

Produce roughly 250–350 words at most, shorter when possible:

1. A specific headline about the buyer's job or desired outcome, with a short subheading.
2. The problem in the buyer's world. Do not attribute a pain to a named buyer unless the evidence supports it.
3. How the relevant product addresses it, with two or three concrete value points where supported.
4. One approved proof point if available; otherwise an honest evaluation approach.
5. One low-friction next step consistent with my selling standards, with contact information only if supplied and approved.

Then provide a separate, seller-only review note: the SELLER.md sections used, source dates if known, assumptions, omitted claims, missing proof, and any necessary approval question. Clearly separate this note from the one-pager so it cannot be mistaken for customer-facing copy. Let me edit the whole draft instead of confirming every sentence. Do not call it approved until I approve it.

By default deliver editable text plus concise layout guidance. If I request HTML, produce a self-contained, responsive document with print styling for one A4/Letter page. Keep text readable; cut copy rather than shrinking it to fit. Do not load trackers or external scripts. If rendering tools are available, check the printed page count and clipping; otherwise say layout is unverified. Never claim you created a PDF unless you actually generated one.