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 follow-up 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 follow-up?

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

How do I follow up with lawyers without sounding pushy?

Be useful and brief. Reference the matter type or operational pain, not a hype line. Give them an easy decline. Many will ignore anything that looks like a mass BD blast because their name is on the letterhead. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

How should a follow-up to a Legal CTO change for after a meeting?

Crisp recap energy. They should be able to forward it. Solicitation rules vary by jurisdiction. Don't give legal advice in the email. Don't ask them to forward confidential facts. The CTO is guarding reliability, security, and engineering time, so the ask should stay at "a technical working session or a written teardown, not a 'vision call'." If you copy a

Legal · CTO · After Meeting

Follow-Up Email Template for Legal CTO: After Meeting

A follow-up email for a Legal CTO (after a meeting) is a short message that reopens the thread without making them do extra work. A follow-up email is a short, context-rich message that reconnects after an earlier touch without restating the whole pitch. In this setting, that means speaking to business development that feels like ambulance chasing, plus intake that

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 follow-up work for a Legal CTO?

Restate the original reason in one line so they don't hunt the thread.
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.
Swap a meeting ask for a smaller yes when they went quiet.

When should I send this to a Legal CTO?

Give it 3 to 5 business days after the last note before you ping again. 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. After three touches with different value, send a breakup and archive.

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. Words that work: 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.

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.
Stop after three touches unless they gave you a reason to continue.
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?

The fastest way to get ignored is stacking three asks into one nudge.
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

Circling back on [Company Name]

Body

Hi [First Name],

I know your calendar is packed, so I'll keep this short.

In Legal, that usually shows up as business development that feels like ambulance chasing, plus intake that leaks hours. I sent a note on business development that feels like ambulance chasing, plus intake that leaks hours and didn't want it to die in the pile. Here's the 15-second version: raised consult-booking rate 22% for a 14-attorney firm without spamming inboxes.

List what you heard, what you promised, and what you need from them, in that order.

Worth a 10-minute look this week, or should I wait?

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

Questions people ask before they hit send

No. Repeat the reason you're relevant in one sentence, then add something new: a proof point, a tighter ask, or a way out. Replaying the first email makes you look automated. 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.