Skip to content

Persuasive Proposal Email That Pre-Empts Objections

Pitch an idea to a decision-maker in a short email that leads with their priorities and addresses likely pushback up front.

Make it yours

Fill in each variable and watch the prompt update. Anything still in {{braces}} needs your input before you use it.

Fill in the blanks

0 of 5 filled

The idea you want approved.

Who decides, with role.

Goals or worries of the decision-maker.

Real facts, numbers, or examples you have.

What it costs or what you're asking for.

Live previewUnfilled
You are a persuasive but honest business writer.

I want to propose: {{proposal}}
Decision-maker: {{decision_maker}}
What they care about most: {{their_priorities}}
Supporting facts I can stand behind: {{evidence}}
Cost or ask: {{cost}}

Work in two steps:

Step 1 — List the 3 most likely objections {{decision_maker}} would raise, each with a one-line honest response. Use only the facts I provided; if a response needs information I didn't give, say "[need data: ...]" instead of inventing it.

Step 2 — Write the email:
- Subject line that states the benefit, not the topic
- Open with the problem in terms of their priorities (1–2 sentences)
- The proposal and the specific ask
- Weave in the strongest 2 objection responses naturally — don't label them "objections"
- Close with a low-friction next step (e.g., a 15-minute chat or a small pilot)

Constraints: Under 200 words for the email. Confident, not salesy. No exaggerated claims.
Open in Playground

Example

Example input

Filled prompt
You are a persuasive but honest business writer.

I want to propose: a 3-month pilot of a shared team inbox tool for the support team
Decision-maker: Dana, Head of Customer Support
What they care about most: first-response time, customer satisfaction scores, and keeping costs flat this year
Supporting facts I can stand behind: We found 14 customer emails last month that sat unanswered for over 48 hours because two people each assumed the other had replied. The tool offers a free 14-day trial and month-to-month billing.
Cost or ask: $12 per user per month for 6 users ($72/month)

Work in two steps:

Step 1 — List the 3 most likely objections Dana, Head of Customer Support would raise, each with a one-line honest response. Use only the facts I provided; if a response needs information I didn't give, say "[need data: ...]" instead of inventing it.

Step 2 — Write the email:
- Subject line that states the benefit, not the topic
- Open with the problem in terms of their priorities (1–2 sentences)
- The proposal and the specific ask
- Weave in the strongest 2 objection responses naturally — don't label them "objections"
- Close with a low-friction next step (e.g., a 15-minute chat or a small pilot)

Constraints: Under 200 words for the email. Confident, not salesy. No exaggerated claims.

Example output

Illustrative example response — written by Promptly, not generated live

Step 1 — Likely objections

  1. "We can't add costs this year." → $72/month, month-to-month, cancellable anytime; one retained customer likely covers it. [need data: average customer value]
  2. "The team won't adopt another tool." → Start with a 14-day free trial before paying anything.
  3. "Can't we just fix this with a process?" → The 14 missed emails came from two people assuming the other replied; assignment visibility is exactly what's missing.

Step 2 — Email

Subject: Stop losing support emails for $72/month

Hi Dana,

Last month, 14 customer emails went unanswered for more than 48 hours — not from lack of effort, but because two of us each assumed the other had replied. That hits first-response time and satisfaction scores directly.

I'd like to run a 3-month pilot of a shared inbox tool that shows who owns each email. It costs $12 per user ($72/month for our 6 people), billed month-to-month, so we can cancel anytime if it doesn't move our numbers.

We can also start with the free 14-day trial before spending anything, and I'll report back on response times.

Could we take 15 minutes this week to decide whether to start the trial?

Thanks, Alex

Why it works

  • Prompt chaining inside one prompt: listing objections first gives the model material to weave into the email, producing a more persuasive draft than asking for the email directly.
  • "Use only the facts I provided" plus a [need data: ...] marker is a simple guard against hallucinated numbers — the model flags gaps instead of filling them with invented statistics.
  • Framing everything around the decision-maker's priorities is what makes a proposal persuasive rather than just descriptive.

Techniques used