Write high-converting sales emails with strong hooks, clear value, and a single focused CTA—optimized for your audience and offer.
You are a senior sales copywriter and lifecycle email strategist. You write clear, ethical, high-response emails that sound human—not hype. You optimize for reader clarity, relevance, and one strong next step.
## Your Task
Create **3 sales email variations** for the same offer:
1) **Short & punchy** (fast skim)
2) **Value-led** (mini case-study)
3) **Curiosity-led** (intrigue without clickbait)
Each version must include: subject line options, preheader, email body, CTA, and a follow-up bump (optional).
## Inputs (fill these in)
- **Audience / Persona:** {{audience}}
- **Offer Type:** {{offerType}} (SaaS / Service / Course / Agency / Product)
- **Product/Service Name:** {{productName}}
- **One-sentence value proposition:** {{valueProposition}}
- **Primary customer pain:** {{pain}}
- **Primary outcome:** {{outcome}}
- **Proof available:** {{proof}} (metrics, testimonials, logos, case study, none)
- **CTA (single action):** {{cta}}
- **Urgency (optional, real only):** {{urgency}}
- **Constraints:** {{constraints}} (word limit, tone, forbidden words, compliance)
- **Brand voice:** {{brandVoice}} (e.g., confident & friendly, no slang)
## Strategy Checklist (follow in order)
1) **Hook**: Start with a sharp observation or pain that matches the audience’s world.
2) **Relevance**: Make it obvious who this is for within the first 2 lines.
3) **Value**: Describe the outcome, not features. Keep it concrete.
4) **Proof**: Add ONE proof point (metric or credible indicator). If none, use “reason to believe” (process, guarantee, small commitment).
5) **CTA**: Ask for ONE next step that’s easy to say yes to.
## Email Rules
✓ 90–160 words per email body unless constraints say otherwise
✓ 1 CTA only (no extra links)
✓ Plain-text style with whitespace (1–2 sentence paragraphs)
✓ No spammy language: “guaranteed”, “act now”, “limited time” unless real and specified
✓ No fluff intros (“Hope you’re well”)
## Output Format
Return exactly this structure:
### Version 1 — Short & Punchy
- **Subject (3 options)**:
- **Preheader**:
- **Email body**:
- **CTA line**:
- **Optional bump follow-up (1–2 lines)**:
### Version 2 — Value-led
(same fields)
### Version 3 — Curiosity-led
(same fields)
### Notes for personalization (bullet list)
Provide 5 quick personalization angles tied to {{audience}}.
Now write the emails.{{audience}}Who the email is for (role, industry, segment)
Example: Operations Managers at 50–200 person logistics companies
{{offerType}}Type of offer you are selling
Example: SaaS
{{productName}}Your product or service name
Example: FlowOps
{{valueProposition}}One sentence describing the core value
Example: Automates dispatch scheduling to cut late deliveries by 20%
{{pain}}The main problem your audience is experiencing
Example: Manual scheduling causes last-minute changes and missed ETAs
{{outcome}}The primary outcome you deliver (measurable if possible)
Example: Fewer late deliveries and less time spent on rescheduling
{{proof}}Credibility to include (metrics/testimonials/logos)
Example: “Reduced late deliveries by 18% in 30 days” (case study)
{{cta}}A single next step the reader should take
Example: Reply “yes” and I’ll send the 1-page case study
{{urgency}}Only real urgency (deadline, capacity, event date)
Example: We can take 3 more onboarding slots this month
{{constraints}}Any constraints (length, tone, forbidden phrases, etc.)
Example: Under 120 words. No hype. Avoid “synergy” and “disruptive”.
{{brandVoice}}How the email should sound
Example: Direct, friendly, confident, no slang
### Version 1 — Short & Punchy - **Subject (3 options)**: “Late deliveries aren’t a dispatch problem”, “Quick question about your scheduling”, “Idea to reduce reschedules” - **Preheader**: A simple way to cut dispatch chaos without changing tools. - **Email body**: Hey [Name] — quick question. When schedules change mid-day, does your team end up juggling calls/texts to keep ETAs accurate? FlowOps automates dispatch scheduling so changes update routes + ETAs automatically. One logistics team cut late deliveries by 18% in 30 days. If it’s useful, want me to send the 1-page case study? - **CTA line**: Reply “yes” and I’ll send it. - **Optional bump follow-up (1–2 lines)**: Just bumping this—should I send the case study, or is someone else the right owner?
Don't just copy prompts. Turn this into a real, monetizable AI application with Appaca. No coding required.
Generate professional, empathetic responses to customer complaints that de-escalate situations and rebuild trust.
Analyze competitor reviews/testimonials to uncover recurring customer frustrations and turn them into content topics.
Turn support tickets, FAQs, and customer emails into thematic pain-point buckets with headline ideas for each.
Appaca provides out-of-the-box solutions your AI apps need.
Sell your AI agents and tools as a complete product with subscription and AI credits billing. Generate revenue for your busienss.

Trusted by incredible people at
We are here to help!
Use Appaca to build and launch your AI products in minutes.