Write sales copy for a specific offer using only the facts I provide. The copy must help the right buyer decide, not pressure every reader. Do not invent testimonials, customer names, performance results, scarcity, competitor comparisons, guarantees, or legal, medical, financial, or safety claims. Ideal buyer and buying situation: [AUDIENCE] Offer and what is included: [OFFER] Price, terms, and fulfillment details: [TERMS] Evidence, customer language, and differentiators: [PROOF] Main objections or alternatives: [OBJECTIONS] Desired action and page format: [CALL TO ACTION] Start with a brief message map: buyer problem, cost of leaving it unresolved, credible promise, mechanism, proof, objections, and action. Then write the final copy in this order: headline; subhead; 3 benefit sections with explanatory body copy; “What you get” bullets; “Who it is for / not for”; objection-handling section; proof section; terms or qualification details; and final CTA. Keep it 450-650 words unless my requested format calls for another length. Translate features into operational outcomes, but distinguish a capability from an outcome that depends on the customer’s actions. Use specific evidence only where supplied. If a price, deadline, refund policy, or availability detail is missing, insert [CONFIRM DETAIL] rather than guessing. Make the CTA state the next action and what happens after it. Before answering, check that each material claim is supported by [PROOF] or [TERMS], and that the copy addresses the stated objections without making unsupported comparisons. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [AUDIENCE] | Describe the buyer, their situation, and the problem they are trying to solve. | Operations managers at 20-80 person agencies who lose time chasing project status across email and spreadsheets. |
| [OFFER] | State what you sell, what is included, and how it is delivered. | A setup service that configures a shared Airtable project dashboard, templates, and two team training sessions. |
| [TERMS] | Provide price, contract or refund terms, timing, and any limits you can substantiate. | $2,400 fixed fee; setup completed within 14 business days after access is provided; no ongoing contract. |
| [PROOF] | Paste factual proof such as verified results, product details, approved testimonials, or customer language. | Includes a live dashboard, intake form, workload view, and documented handoff. One approved client quote: “We stopped asking where every project stood.” |
| [OBJECTIONS] | List the concerns, alternatives, or reasons buyers delay. | We already use spreadsheets; implementation will disrupt the team; Airtable may be too complex. |
| [CALL TO ACTION] | State the action you want and the format you need, such as a landing page or email. | Book a 20-minute fit call; write a landing page. |
How to use
- Give the model approved proof and terms before asking for persuasive language.
- Check every number, quote, time promise, and policy against its source before publishing.
- Replace any broad benefit with the specific mechanism that makes it plausible.
- Follow up with: “Rewrite this for a buyer who knows the problem but is comparing alternatives.”
Variations
Cold email
Use for a one-to-one outreach email where relevance matters more than a long product explanation.
Write a cold email to [RECIPIENT ROLE] at [COMPANY] about [OFFER]. Relevant public or supplied context: [CONTEXT]. Proof I can use: [PROOF]. Desired CTA: [CTA]. Write a subject line and a 90-130 word email. Open with a specific, non-creepy observation, connect it to one plausible operational problem, state one relevant capability, and make a low-friction ask. Do not claim to know internal results, fabricate personalization, use false urgency, or imply the recipient requested contact. Check that every fact about the company came from my context.
Product page
Use for a self-serve product page that must explain fit, constraints, and purchase terms.
Write product-page copy for [PRODUCT] for [BUYER]. Features: [FEATURES]. Supported outcomes and proof: [PROOF]. Price and purchase terms: [TERMS]. Limitations or exclusions: [LIMITATIONS]. Produce a headline, short introduction, feature-to-benefit sections, specifications, fit guidance, FAQs, and CTA. Keep it 500-700 words. Do not turn a feature into a guaranteed outcome or omit a material limitation. Mark missing commercial details as [CONFIRM DETAIL]. Check every claim against the supplied facts.
Sales call brief
Use before a discovery or demo call when you need useful questions rather than a scripted pitch.
Build a sales-call brief for [PROSPECT TYPE] considering [OFFER]. Known context: [CONTEXT]. Likely alternatives: [ALTERNATIVES]. Approved proof: [PROOF]. Create a 30-minute agenda, 8 discovery questions, 3 qualification signals, and a recap email outline. Questions should uncover process, impact, decision process, timing, and constraints without assuming a pain point. Do not make outcome promises or treat a prospect’s public information as confirmed internal fact. Check that every proof point is approved and relevant to the prospect type.
Tips
- Put the buyer’s decision context in the opening, not a generic description of your company.
- Proof works best when it explains conditions and mechanism; a result without context can read as a promise.
- Address a real alternative such as doing nothing, using a spreadsheet, or hiring internally instead of adding vague “why us” language.
- A CTA should state the commitment level, such as a demo, trial, purchase, or consultation, and what follows.
FAQ
Can AI write sales copy without customer testimonials?
Yes. Use product facts, process detail, limitations, and customer language you are allowed to use; do not manufacture social proof.
Should I ask for several audiences in one prompt?
Create the first draft for one buyer and one situation. Separate variants prevent the copy from becoming generic.
Can AI create urgency?
Only use urgency tied to a real deadline, capacity limit, or price change you can document.