Prompts / Sales & Business Development

Claude prompt for an upsell email response

This prompt produces a concise response that recommends an appropriate expansion based on the prospect’s stated needs. Use it after a real conversation, renewal discussion, or product-use signal gives you evidence for the offer.

PromptOpen ChatGPTOpen Claude
Write a personalized upsell email response to a current prospect or customer. Recommend an expansion only when it directly addresses a documented need; do not invent pain points, usage, ROI, urgency, approval authority, or customer quotes.

Recipient and relationship: [RECIPIENT AND CONTEXT]
What they have said or done: [EVIDENCE]
Current product or service: [CURRENT SOLUTION]
Expansion I can offer: [UPSELL OFFER]
Commercial details and limits: [COMMERCIAL DETAILS]
Desired next step: [NEXT STEP]

First, identify the strongest evidence-supported reason to raise the offer. If the evidence does not justify an upsell, say so and draft a helpful non-upsell response instead.

Write one email of 120–170 words with: a specific subject line; a first sentence that acknowledges the recipient’s stated situation or prior action; a short bridge from that evidence to one relevant capability; a concrete explanation of what changes with the expansion, including scope, implementation, pricing, or timing only where supplied; and one low-friction call to action. Use one primary offer, not a bundle of unrelated features.

Keep the tone useful and direct. Do not use false scarcity, exaggerated outcomes, manipulative urgency, or unsupported savings claims. If price, contract changes, data handling, implementation requirements, or eligibility are unknown, do not imply certainty; suggest the appropriate next conversation or attachable information instead.

After the email, add “Why this is relevant” with two bullets that quote or closely paraphrase only the evidence I supplied, and “Claims to verify” with any statements that need confirmation before sending.

Ask up to 3 clarifying questions only if a required input is missing. Before answering, check that each benefit maps to supplied evidence and that the requested next step is proportionate to the relationship stage.

Fill in

PlaceholderWhat to enterExample
[RECIPIENT AND CONTEXT]State the recipient’s name, role, company, relationship stage, and relevant conversation context.Priya Shah, operations director at Acorn Benefits; she is evaluating renewal options after a quarterly business review.
[EVIDENCE]Paste notes, emails, usage facts, or quoted needs that support the offer.Priya said her team manually exports reports for regional managers each Friday and asked whether scheduled reports can be customized by region.
[CURRENT SOLUTION]Describe what the recipient currently buys or uses and its known scope.Acorn uses the Standard plan for 35 administrators, including basic reporting.
[UPSELL OFFER]Describe the single added product, tier, service, or capacity you want to recommend.Analytics add-on with scheduled regional reports, custom dashboards, and onboarding support.
[COMMERCIAL DETAILS]Provide verified price, term, implementation, eligibility, or contract details and note what is unknown.Verified add-on price is $600 per month on an annual amendment; onboarding takes two remote sessions. Regional dashboard availability needs solutions-engineering confirmation.
[NEXT STEP]State one concrete action you want the recipient to take, such as a 20-minute review or approval to send options.Ask for a 20-minute working session next week to confirm report requirements and review the add-on.

How to use

  1. Paste the prospect’s actual words or documented usage signals, along with only confirmed product and pricing details.
  2. Read the “Claims to verify” section and remove or confirm every uncertain statement before sending.
  3. Choose one next step that fits the relationship stage, such as a requirements call before asking for an amendment.
  4. Follow up with: “Write a polite follow-up if Priya has not replied after five business days; do not add new claims.”

Variations

Renewal expansion

Use this when an account is approaching renewal and has documented expansion needs.

Variation
Draft a 140-word renewal email for [RECIPIENT] at [COMPANY]. Their renewal date and current agreement are [RENEWAL CONTEXT]. Evidence of an unmet need is [EVIDENCE]. The relevant expansion is [OFFER], with verified commercial terms [TERMS]. Ask for [NEXT STEP]. Acknowledge the renewal without treating it as automatic. State only confirmed pricing, scope, and timing. Output a subject line, email, two evidence links, and claims to verify. Ask up to 3 questions only if required inputs are missing. Check that every benefit is tied to evidence and the ask fits the renewal stage.

Post-demo response

Use this after a prospect asks about a higher-tier capability during a demo.

Variation
Write a concise post-demo response to [RECIPIENT]. During the demo, they asked about [DOCUMENTED QUESTION] because [CONTEXT]. Their current evaluation scope is [CURRENT SCOPE]. The relevant higher-tier option is [OFFER], and verified details are [TERMS]. Invite them to [NEXT STEP]. Produce a subject line and a 100–140-word email. Do not claim the feature solves a problem unless they stated it, and do not promise implementation details that are unconfirmed. Ask up to 3 questions only if necessary. Check that the message answers their question before making the offer.

Usage-based expansion

Use this when verified usage indicates the customer may need more capacity or support.

Variation
Draft an email recommending a capacity or service expansion for [RECIPIENT] at [COMPANY]. Verified usage data is [USAGE DATA], current plan limits are [CURRENT LIMITS], and the available expansion is [OFFER AND TERMS]. Explain the operational implication of the data without exaggerating risk, then ask for [NEXT STEP]. Output a subject line, 120-word email, and claims to verify. Do not imply that usage will continue at the same rate or that service will stop unless confirmed. Ask up to 3 questions only if required details are missing. Check that all numeric claims exactly match the supplied data.

Tips

  • Use the customer’s own stated problem as the bridge to the offer; a generic feature recap reads like an untargeted sales sequence.
  • Recommend one expansion with a clear operational change, not a list of upgrades that forces the recipient to do the matching work.
  • Separate confirmed commercial terms from assumptions about implementation, procurement, or ROI before an email goes out.
  • For a late-stage buyer, ask for a scoped review or a decision path; for an early-stage buyer, ask for the information needed to assess fit.

FAQ

Should an upsell email mention price?

Mention it when the price is confirmed and it helps the recipient assess the offer. If pricing depends on scope or approval, say that plainly rather than guessing.

How personalized does an upsell response need to be?

One specific reference to a documented need or use case is more valuable than several generic compliments. Do not manufacture familiarity.

What if I have no evidence the customer needs the add-on?

Do not force an upsell. Send a helpful response to their current question or ask a discovery question that can establish whether the offer is relevant.

Related prompts

All Sales & Business Development prompts →

Get a few prompts like this every week

Something Big is a free AI newsletter read by 70,000+ professionals. About three short emails a week with prompts and tools that work, plus what changed in AI and what to do about it.