Sales EmailTemplate

Legal · CTO · Replied Then Silent

Referral Request for Legal CTO: Replied Then Silent

A referral request email asks someone to make an intro by doing the work for them: who, why, and a forwardable blurb. For Legal teams, the version that works for replied then went silent has to respect Solicitation rules vary by jurisdiction. Write to the CTO like they already have a full calendar and a reason to be cautious.

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 referral request work for a Legal CTO?

  • Explain why they'd look good for making the intro.
  • Speaks to business development that feels like ambulance chasing, plus intake that leaks hours instead of a generic "value prop."
  • Fits how a CTO actually reads: 90 words is plenty if the substance is real. Don't pad.
  • Quote their last sentence and answer it. People reply to their own unfinished thought.
  • Include a forwardable paragraph.

When should I send this to a Legal CTO?

Ask after you've given them a reason to want to help, not after the first coffee. 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 partners move slowly unless a matter is on fire. respect that. If you're emailing a CTO, 90 words is plenty if the substance is real. Don't pad.

What this CTO actually cares about

A CTO in Legal is protecting reliability, security, and engineering time. They look for architecture, failure modes, and whether you'll create toil for their team. Fluff is a ranking signal that you don't know the work. The hook that earns a look is an incident class, a security gap, or a cost line they already hate. The ask should stay at this size: a technical working session or a written teardown, not a 'vision call'. Delete trigger: Calling it 'AI-powered' with no description of the system. They protect reliability, security, and engineering time, so keep the ask at "a technical working session or a written teardown, not a 'vision call'."

How Legal changes the note

Legal buyers are partners, GCs, and practice managers who bill time and guard reputation. Solicitation rules vary by jurisdiction. Don't give legal advice in the email. Don't ask them to forward confidential facts. A credible proof point in this vertical sounds like: raised consult-booking rate 22% for a 14-attorney firm without spamming inboxes. Watch the language. Words that land here include intake, matter, engagement letter, conflict check, realization, origination. If you cannot name a new practice group, a lost RFP, or a partner retiring with a book of work, wait until you can. If you cannot name a new practice group, a lost RFP, or a partner retiring with a book of work, wait until you can.

How should I customize this template before I send it?

  • Replace the pain line with a boutique firm that wins work from referrals and then goes quiet on the referrer.
  • Keep the tone precise.
  • Never send a referral ask from a brand-new relationship.
  • 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 write 'we'll crush opposing counsel.' It's TV, not practice.

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

  • Asking 'who do you know?' is lazy and gets no names.
  • Don't forward the whole thread with 'friendly bump' and nothing else.
  • Don't write 'we'll crush opposing counsel.' It's TV, not practice.
  • Calling it 'AI-powered' with no description of the system.

How does this replied then silent scenario compare?

DimensionFor this template
Best send window5-7 days, or the date they named
Ideal length90 words is plenty if the substance is real. Don't pad.
Primary aska technical working session or a written teardown, not a 'vision call'
Industry metric to citeintake conversion, realization, and time to first draft
TonePrecise. No slogans. It's fine to be a little dry.
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] / intake conversion

Body

Hi [First Name],

This is an ask. I tried to make it easy to say no.

I'm writing because a new practice group, a lost RFP, or a partner retiring with a book of work. Blurb you can paste: '[Your Name] helps [audience] with raised consult-booking rate 22% for a 14-attorney firm without spamming inboxes. They asked if you'd be open to a short intro about [topic].'

Quote their last sentence and answer it. People reply to their own unfinished thought.

Thanks either way. I know intros cost you something.

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

Questions people ask before they hit send

Lead with intake conversion, realization, and time to first draft. That's the language this buyer already reports. If you can't connect your email to business development that feels like ambulance chasing, plus intake that leaks hours, you're asking them to do the translation work. They won't.

Related templates

Want a custom draft instead? Try the email generator.