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

Don't follow a cold email the next morning. Give it 4 business days. 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.

Should I mention a mutual connection in a cold email?

Only if the connection would be comfortable with it. Name-dropping someone who barely knows you can backfire. If you do mention them, say exactly how you know them in one clause and move on. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

What if they go silent after receiving the proposal?

Assume a process problem before you assume a no. Ask which layer is stuck and offer a thinner version. If you get nothing after a breakup note, archive it. Endless bumps after a proposal train them to wait for a discount.

Is it okay to send this cold email 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 Non-Profit cold email?

Don't imply their mission is inefficient. Help them tell it better. Calling it 'AI-powered' with no description of the system. Don't resend the PDF with 'just bumping this.' Those three mistakes show up constantly in Non-Profit inboxes and they all read as "this was templated."

Non-Profit · CTO · After Proposal

Cold Email Template for Non-Profit CTO: After Proposal

A cold email for a Non-Profit CTO (after a proposal) is a short message that reopens the thread without making them do extra work. A cold email is a first-touch message to someone who didn't ask for it, so relevance has to show up before the pitch does. In this setting, that means speaking to donor follow-up that feels automated

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 cold email work for a Non-Profit CTO?

Give them permission to say you're early.
Speaks to donor follow-up that feels automated and grant calendars that punish delay 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.
Make the first ask smaller than a 30-minute call.

When should I send this to a Non-Profit CTO?

Don't follow a cold email the next morning. Give it 4 business days. 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 boards and grant windows set the pace. ignore that and you'll look amateur. 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 Non-Profit 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 Non-Profit changes the note

Non-Profit buyers are ED teams, development leads, and program directors stretching every dollar. Don't pitch like a VC. Mission language has to be specific to their programs, not a generic 'doing good.' A credible proof point in this vertical sounds like: improved second-gift conversion 17% with thank-you notes that named the program, not the CRM. Watch the language. Words that land here include restricted funds, board, grant cycle, stewardship, program officer. Buyers here measure success with donor retention, grant hit rate, and cost per dollar raised. Buyers here measure success with donor retention, grant hit rate, and cost per dollar raised.

How should I customize this template before I send it?

Replace the pain line with a development shop whose lapsed-donor emails all start with 'just checking in'.
Keep the tone precise.
Research one real trigger. Fake personalization is worse than none.
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 imply their mission is inefficient. Help them tell it better.

What mistakes should I avoid with this after proposal note?

Opening with your company story is how cold email dies.
Don't resend the PDF with 'just bumping this.'
Don't imply their mission is inefficient. Help them tell it better.
Calling it 'AI-powered' with no description of the system.

How does this after proposal scenario compare?

Dimension	For this template
Best send window	5 business days, or the agreed date
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	donor retention, grant hit rate, and cost per dollar raised
Tone	Precise. No slogans. It's fine to be a little dry.
Unlike after demo	The commercial conversation has started. Be explicit about decision mechanics.
Unlike invoice reminder	They don't owe you money yet. Don't sound like collections.

What should I copy and send?

Copy-ready template

Subject

CTO question on after proposal

Body

Hi [First Name],

If [pain] isn't a priority, you can delete this.

The version of this that matters for ED teams, development leads, and program directors stretching every dollar is improved second-gift conversion 17% with thank-you notes that named the program, not the CRM. I don't need a demo. I can send a 6-line teardown of how [Company Name] might approach donor follow-up that feels automated and grant calendars that punish delay.

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

If I sent a 1-page sketch, would you glance at 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 "CTO question on after proposal" 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.