Sales EmailTemplate

Legal · CTO · After Proposal

Breakup Email Template for Legal CTO: After Proposal

When a Legal CTO goes quiet (after a proposal), the right breakup email does one job: make a reply cheaper than silence. 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. That's why this template leads with intake conversion, realization, and time to first

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 breakup email work for a Legal CTO?

  • Ask permission to archive. It feels respectful and it creates a tiny action.
  • 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.
  • Offer to cut scope, split phases, or walk a second stakeholder through one page.
  • Take the pressure off. People reply to breakup emails because they're allowed to say no.

When should I send this to a Legal CTO?

Send it after the third unanswered touch, not after the first silence. On the review date you set. If you didn't set one, five business days. For this combo, treat "5 business days, or the agreed date" 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. 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.
  • Keep the tone adult. No 'I guess you're not interested' sulk.
  • Time it for 5 business days, or the agreed date. On the review date you set. If you didn't set one, five business days.
  • Don't write 'we'll crush opposing counsel.' It's TV, not practice.

What mistakes should I avoid with this after proposal note?

  • Sarcastic breakup emails feel clever to you and cheap to them.
  • Don't resend the PDF with 'just bumping this.'
  • 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 proposal scenario compare?

DimensionFor this template
Best send window5 business days, or the agreed date
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 demoThe commercial conversation has started. Be explicit about decision mechanics.
Unlike invoice reminderThey don't owe you money yet. Don't sound like collections.

What should I copy and send?

Copy-ready template

Subject

Okay to archive [Company Name]?

Body

Hi [First Name],

I don't want to keep landing in your inbox if this isn't useful.

I'm writing because a new practice group, a lost RFP, or a partner retiring with a book of work. If the timing is wrong, tell me a month and I'll come back then. If it's a no, that's genuinely fine.

Given this is after a proposal, ask whether the hold is scope, price, timing, or people.

Wishing you a clean quarter either way.

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

Questions people ask before they hit send

Send it after the third unanswered touch, not after the first silence. On the review date you set. If you didn't set one, five business days. 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.