Follow up after sending pricing
Use a few days after sending pricing when the prospect has gone quiet, to address unspoken sticker shock.
Write a follow-up email sent after pricing, when the prospect went quiet.
Prospect: {{prospect_name}} at {{company}}.
The price I sent: {{price}}.
The value / outcome it delivers: {{outcome}}.
Likely silent concern: {{likely_concern}}.
The email should:
- Avoid assuming the price scared them off, but make it safe to say so.
- Re-anchor the price to the outcome in one sentence.
- Offer to walk through options or answer internal questions.
- Keep one clear, easy next step.
Under 90 words, calm and confident (no discount panic). Provide a subject line.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{prospect_name}}
- {{company}}
- {{price}}
- {{outcome}}
- {{likely_concern}}
Related prompts
You are an experienced B2B sales rep who writes short, human cold emails that get replies. Write a first-touch cold email to {{prospect_name}}, who is {{prospect_role}} at {{prospe...
You are a sales copywriter. Create three distinct cold email variations for the same prospect so I can A/B test them. Prospect: {{prospect_role}} at {{prospect_company}} What I sel...
You write natural LinkedIn connection notes that do not feel like a pitch. Write a connection request note to {{prospect_name}}, {{prospect_role}} at {{prospect_company}}. Reason f...
You are a social-selling expert. Build a 4-message LinkedIn DM sequence for a prospect who just accepted my connection request. Prospect: {{prospect_role}} at {{prospect_company}}...
You write follow-up emails that add value rather than nag. Write a follow-up to {{prospect_name}} who did not reply to my first email. Original email was about: {{original_topic}}...
You are a sales cadence specialist. Design a 5-email follow-up sequence for a cold prospect. Prospect type: {{prospect_role}} at companies like {{target_company_profile}} What I se...
0 Comments
Loading discussion...