How many times should I follow up with a CTO (after a meeting)?

Ask after you've given them a reason to want to help, not after the first coffee. Same day, within a few hours. Next morning is the backup, not the plan. 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.

Should I offer a referral fee in the email?

Only if that's already how you work and it won't make them look mercenary. Many operators prefer a clean intro. If you do mention a fee, keep it secondary to why the intro helps the other person. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

What belongs in a post-meeting follow-up?

Decisions, owners, dates, and anything you promised to send. Keep opinions out unless they asked for a recommendation. A forwardable recap does more for the deal than a paragraph about how 'great it was to connect.' Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Is it okay to send this referral request on LinkedIn instead of email?

Yes if this CTO is actually active there and the thread isn't about long attachments. Keep the LinkedIn version even shorter. Don't paste the full email. One context line and one question is plenty. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

What should I never say in a Legal referral request?

Don't write 'we'll crush opposing counsel.' It's TV, not practice. Calling it 'AI-powered' with no description of the system. Don't send a pitch deck they didn't ask for as a 'recap.' Those three mistakes show up constantly in Legal inboxes and they all read as "this was templated."

Legal · CTO · After Meeting

Referral Request Email Template for Legal CTO: After Meeting

The query is practical: what should a referral request email to a Legal CTO say for after a meeting? Start with a direct answer, add one proof point about business development that feels like ambulance chasing, plus intake that leaks hours, and close with confirm the next date or the open question.

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.
List what you heard, what you promised, and what you need from them, in that order.
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, within a few hours. Next morning is the backup, not the plan. For this combo, treat "Same day" 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. Tuesday through Thursday mid-morning local time is a safe default.

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 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.

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. A thread that ignores business development that feels like ambulance chasing, plus intake that leaks hours reads like every other vendor bump. 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. Same day, within a few hours. Next morning is the backup, not the plan.
Don't write 'we'll crush opposing counsel.' It's TV, not practice.

What mistakes should I avoid with this after meeting note?

Asking 'who do you know?' is lazy and gets no names.
Don't send a pitch deck they didn't ask for as a 'recap.'
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 meeting scenario compare?

Dimension	For this template
Best send window	Same day
Ideal length	90 words is plenty if the substance is real. Don't pad.
Primary ask	a technical working session or a written teardown, not a 'vision call'
Industry metric to cite	intake conversion, realization, and time to first draft
Tone	Precise. No slogans. It's fine to be a little dry.
Unlike after demo	A meeting might have been intro-only. Don't write a product recap they didn't see.
Unlike thank you	Gratitude can live in line one. The rest should be operational.

What should I copy and send?

Copy-ready template

Subject

Could you intro me to [role] at [Company]?

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.

Lock decisions, owners, and dates while memory is still sharp.

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

Name the situation and the business object, not your excitement. Something like "Could you intro me to [role] at [Company]?" outperforms "Just checking in" because a CTO can decide from the preview text whether it's worth opening. Keep it under 50 characters when you can.

Related templates

Want a custom draft instead? Try the email generator.