Sales EmailTemplate

Consulting · CEO · Replied Then Silent

Meeting Request for Consulting CEO: Replied Then Silent

When a Consulting CEO goes quiet (replied then went silent), the right meeting request email does one job: make a reply cheaper than silence. They skim on a phone between meetings. If the first two lines don't name a business outcome, the rest never gets read. That's why this template leads with utilization, proposal win rate, and time to SOW

Last updated: 2026-09-02 · Reviewed by: Sales Email Template editors

We write templates the way we wrote emails on quota: short, specific, and easy to forward. When we cite research below, it is because the number changes how a buyer reads your note, not to pad the page.

Sources: HubSpot sales email benchmarks; Gong follow-up research

Why does this meeting request work for a Consulting CEO?

  • Promise notes so the meeting has a paper trail.
  • Speaks to proposals that stall in procurement and relationships that go quiet between projects instead of a generic "value prop."
  • Fits how a CEO actually reads: Keep the whole note under 70 words unless they asked for detail.
  • Quote their last sentence and answer it. People reply to their own unfinished thought.
  • Offer two times plus an async escape hatch.

When should I send this to a Consulting CEO?

If they agreed in principle, send times the same day while intent is warm. Give it a week unless they named a date. Then write on that date, not the day after you got impatient. For this combo, treat "5-7 days, or the date they named" as the default, then adjust around a small diagnostic can start in a week. a transformation waits on a sponsor. If you're emailing a CEO, Keep the whole note under 70 words unless they asked for detail.

What this CEO actually cares about

A CEO in Consulting is protecting time, reputation, and optionality. They skim on a phone between meetings. If the first two lines don't name a business outcome, the rest never gets read. The hook that earns a look is a P&L, risk, or competitive issue they already feel. The ask should stay at this size: one decision or a 10-minute yes, not a workshop. Delete trigger: A long origin story or a request to 'pick your brain.' Tone: Direct, adult, light on process jargon. Talk like a peer who did the homework.

How Consulting changes the note

Consulting buyers are partners and delivery leads selling expertise while protecting utilization. They've written prettier decks than yours. Compete on diagnosis and next step, not on adjectives. A credible proof point in this vertical sounds like: moved three stalled proposals to signature by isolating the real blocker in one email. Watch the language. Words that land here include SOW, utilization, workstream, sponsor, retainer, change request. Proof that lands: moved three stalled proposals to signature by isolating the real blocker in one email. Proof that lands: moved three stalled proposals to signature by isolating the real blocker in one email.

How should I customize this template before I send it?

  • Replace the pain line with a boutique firm whose last project ended well and then nobody asked for the next phase.
  • Keep the tone direct, adult, light on process jargon.
  • Don't offer 'anytime next week.' That's unpaid calendar Tetris.
  • Time it for 5-7 days, or the date they named. Give it a week unless they named a date. Then write on that date, not the day after you got impatient.
  • Don't call yourself a thought leader. Let the email be useful instead.

What mistakes should I avoid with this replied then silent note?

  • Calendly links with no agenda look like a trap.
  • Don't forward the whole thread with 'friendly bump' and nothing else.
  • Don't call yourself a thought leader. Let the email be useful instead.
  • A long origin story or a request to 'pick your brain.'

How does this replied then silent scenario compare?

DimensionFor this template
Best send window5-7 days, or the date they named
Ideal lengthKeep the whole note under 70 words unless they asked for detail.
Primary askone decision or a 10-minute yes, not a workshop
Industry metric to citeutilization, proposal win rate, and time to SOW
ToneDirect, adult, light on process jargon. Talk like a peer who did the homework.
Unlike no responseThey already spent social energy. Treat them like a conversation, not a lead.
Unlike after proposalYou may not have a document on the table yet. Don't invent a buying process.

What should I copy and send?

Copy-ready template

Subject

[Company Name] / utilization

Body

Hi [First Name],

I'd like 15 minutes to pressure-test [topic] against what you're already doing.

I'm writing because a new executive sponsor, a failed internal initiative, or a budget refresh. Agenda: 5 minutes on current [process], 5 on where [Your Product] would sit, 5 on go / no-go. I'll send notes after either way.

Given this is replied then went silent, ask if the blocker is timing, people, or the work itself.

Which of those two times is less annoying?

Best,
[Your Name]
[Your Title]
[Your Company]

Questions people ask before they hit send

Fifteen to twenty minutes. Thirty is easier for you and harder for them. If the first conversation earns it, you can ask for a longer working session later. Starting small gets more yeses. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Related templates

Want a custom draft instead? Try the email generator.