Sales EmailTemplate

Legal · CTO · After Demo

Referral Request Email Template for Legal CTO: After Demo

A referral request email for a Legal CTO (after a demo) is a short message that reopens the thread without making them do extra work. A referral request email asks someone to make an intro by doing the work for them: who, why, and a forwardable blurb. In this setting, that means speaking to business development that feels like ambulance

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?

  • Give them cover to decline.
  • 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.
  • Replay the two moments they leaned in, and the one concern they named.
  • Ask for a specific profile, not 'anyone in your network.'

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. Same day with the recap. A value bump 3 days later if they went quiet. For this combo, treat "Same day, then 3 days if silent" 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. If your note would embarrass them in a team channel, rewrite it.

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. Partners move slowly unless a matter is on fire. Respect that. Words that work: intake, matter, engagement letter, conflict check, realization, origination. Partners move slowly unless a matter is on fire. Respect that.

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.
  • If they intro you, report back after the meeting.
  • Time it for Same day, then 3 days if silent. Same day with the recap. A value bump 3 days later if they went quiet.
  • Don't write 'we'll crush opposing counsel.' It's TV, not practice.

What mistakes should I avoid with this after demo note?

  • Asking 'who do you know?' is lazy and gets no names.
  • Don't send a 19-page deck that relitigates features they skipped.
  • 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 after demo scenario compare?

DimensionFor this template
Best send windowSame day, then 3 days if silent
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 after meetingThey have product context now. Speak to what they saw, not to a generic intro.
Unlike after proposalPricing may not be on paper yet. Don't jump to 'ready to sign.'

What should I copy and send?

Copy-ready template

Subject

Legal note on business development that feels like ambulance chasing, plus intake that leaks hours

Body

Hi [First Name],

If you're willing, I wrote a blurb you can forward as-is.

The version of this that matters for partners, GCs, and practice managers who bill time and guard reputation is raised consult-booking rate 22% for a 14-attorney firm without spamming inboxes. If now is a bad time, don't spend political capital on this.

Replay the two moments they leaned in, and the one concern they named.

If you want changes to the blurb, tell me and I'll rewrite it.

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

Questions people ask before they hit send

Ask after you've given them a reason to want to help, not after the first coffee. Same day with the recap. A value bump 3 days later if they went quiet. After that, send a breakup note and archive it. A CTO who wants it will answer a clean close more often than a fifth bump.

Related templates

Want a custom draft instead? Try the email generator.