PlaybookPrompts

Write an email your champion can forward internally

Sales & Outreach championdeal-managementinternal-selling

Champions often want to sell internally but don't know what to say. This prompt writes an email in the champion's voice that they can forward to a CFO, IT leader, or executive—covering the business case without sounding like vendor marketing.

Prompt
You are a ghostwriter for a B2B deal champion. Write an internal email the champion can forward (or lightly edit) to get buy-in from a key internal stakeholder.

Deal context:
- Champion's name and title: {{CHAMPION_NAME_TITLE}}
- Internal recipient's name and title: {{RECIPIENT_NAME_TITLE}}
- Our product/vendor: {{OUR_PRODUCT}}
- The business problem being solved: {{BUSINESS_PROBLEM}}
- Quantified value or expected outcome (use numbers if available): {{VALUE_CASE}}
- The specific concern this recipient is most likely to have: {{RECIPIENT_CONCERN}}
- Stage of the deal (evaluation / final approval / budget sign-off): {{DEAL_STAGE}}

Write the email following these steps:
1. Write in first person from the champion's voice—not from our company
2. Open with the business problem, not the product
3. Address {{RECIPIENT_CONCERN}} directly in paragraph 2—don't bury it
4. Summarize the value case in one concrete sentence with numbers
5. State a clear ask (review, 30-minute conversation, budget approval) with a suggested timeframe
6. Keep the email under 150 words

Then add a 'Coach's note' (not part of the email): flag any claim in the email that the champion would need to verify or soften before sending.
Variables to fill in
  • {{CHAMPION_NAME_TITLE}}
  • {{RECIPIENT_NAME_TITLE}}
  • {{OUR_PRODUCT}}
  • {{BUSINESS_PROBLEM}}
  • {{VALUE_CASE}}
  • {{RECIPIENT_CONCERN}}
  • {{DEAL_STAGE}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{CHAMPION_NAME_TITLE}}{{RECIPIENT_NAME_TITLE}}{{OUR_PRODUCT}}{{BUSINESS_PROBLEM}}{{VALUE_CASE}}{{RECIPIENT_CONCERN}}{{DEAL_STAGE}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.