Email CTA Rewrite

The file

---
name: ai-optimized-email-cta-rewrite-for-high-conversions
description: >-
  A rewrite of your email call to action that uses curiosity and value to get more replies, casting the old way of working as the problem. Adapted from Daniel Disney.
  Task type: Create. Built for Sales.
  Use when the request sounds like "Email CTA Rewrite".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Outbound and Prospecting
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/ai-optimized-email-cta-rewrite-for-high-conversions
---

# Email CTA Rewrite

A rewrite of your email call to action that uses curiosity and value to get more replies, casting the old way of working as the problem. Adapted from Daniel Disney.

One job only: a rewrite of your email call to action that uses curiosity and value to get more replies, casting the old way of working as the problem. Anything outside that job belongs in another file in the Outbound and Prospecting suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- old email cta
- answer

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
You will be re-writing an existing email call-to-action (CTA) into a more effective, funnel-based CTA designed to convert more people. The key is to use curiosity and value to entice the reader to engage, while positioning the "old way" of doing things as the enemy and the customer who wants change as the hero.

Here is the existing email CTA:
<Old Email CTA>
{$OLD_EMAIL_CTA}
</Old Email CTA>

To re-write this into a high-converting, funnel-based CTA, follow these steps:

1. Begin by setting the context in your <scratchpad> on why using a funnel-based CTA is important for increasing conversions. Explain the psychology behind using curiosity and value to draw people in.

2. Next, in your <scratchpad>, identify what the "old way" of doing things is that this CTA is positioning as the enemy. Also identify how the ideal customer is being portrayed as the hero seeking a better "new way".

3. Then, draft your new funnel-based CTA in your <scratchpad>. Use curiosity and value to tease the reader and make them want to engage further. Position the "old way" as the problem and the "new way" as the desirable solution. But keep it professional.

4. Once your draft CTA is ready, provide it as the final <answer>, formatted properly with line breaks, bold/italics as needed.

Remember, the key is to entice the reader without giving everything away, while making them the hero who recognizes the "old way" is the enemy holding them back from the better "new way" your product/service provides.
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/ai-optimized-email-cta-rewrite-for-high-conversions
- Suite: https://www.therevenueaireport.com/agent-skills/suites/outbound-and-prospecting
- Publication: The Revenue AI Report, https://www.therevenueaireport.com