Non-Profit · CTO · After Proposal
Referral Request for Non-Profit CTO: After Proposal
Use this referral request template when you're emailing a CTO in Non-Profit (after a proposal). There's a document in play. Silence usually means a missing owner, a budget puzzle, or a comparison you can't see. Keep the note aligned with Precise. No slogans. It's fine to be a little dry.
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 Non-Profit CTO?
- Give them cover to decline.
- 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.
- Ask for a specific profile, not 'anyone in your network.'
When should I send this to a Non-Profit CTO?
Ask after you've given them a reason to want to help, not after the first coffee. 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 protect reliability, security, and engineering time, so keep the ask at "a technical working session or a written teardown, not a 'vision call'."
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. Words that work: restricted funds, board, grant cycle, stewardship, program officer. A thread that ignores donor follow-up that feels automated and grant calendars that punish delay reads like every other vendor bump.
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.
- If they intro you, report back after the meeting.
- 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?
- Asking 'who do you know?' is lazy and gets no names.
- 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
Forwardable blurb inside, if you're open to an intro
Body
Hi [First Name], I'm looking for a warm intro to [specific role] who owns [pain], and you came to mind because [reason]. I'm writing because a gala, a grant deadline, or a board meeting with a gap in the packet. If now is a bad time, don't spend political capital on this. Given this is after a proposal, ask whether the hold is scope, price, timing, or people. 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
Grateful, specific, and light on pressure. Name the program the gift touched. Ask for a conversation when it's real, not after every newsletter. People give again when they feel remembered, not processed. 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.