Non-Profit · CTO · After Interview
Referral Request for Non-Profit CTO: After Interview
Use this referral request template when you're emailing a CTO in Non-Profit (after an interview). Someone just evaluated you as a person, not a product. The email has to sound like the same human they met. 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?
- Explain why they'd look good for making the intro.
- 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.
- Reference a real moment from the conversation and connect it to how you'd do the work.
- Include a forwardable paragraph.
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. Within 24 hours. Same day is better. For this combo, treat "Within 24 hours" 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. After three touches with different value, send a breakup and archive.
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. Tone: Precise. No slogans. It's fine to be a little dry.
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. Proof that lands: improved second-gift conversion 17% with thank-you notes that named the program, not the CRM. Proof that lands: improved second-gift conversion 17% with thank-you notes that named the program, not the CRM.
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.
- Never send a referral ask from a brand-new relationship.
- Time it for Within 24 hours. Within 24 hours. Same day is better.
- Don't imply their mission is inefficient. Help them tell it better.
What mistakes should I avoid with this after interview note?
- Asking 'who do you know?' is lazy and gets no names.
- Don't recap your whole résumé. They were in the room.
- 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 interview scenario compare?
| Dimension | For this template |
|---|---|
| Best send window | Within 24 hours |
| 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 thank you | A thank-you is part of it. The rest should show you understood the role. |
| Unlike after meeting | The power dynamic is different. Don't 'check in on next steps' like a vendor chasing a PO. |
What should I copy and send?
Copy-ready template
Subject
Need a warm path into [team]
Body
Hi [First Name], I'm looking for a warm intro to [specific role] who owns [pain], and you came to mind because [reason]. In Non-Profit, that usually shows up as donor follow-up that feels automated and grant calendars that punish delay. If now is a bad time, don't spend political capital on this. Given this is after an interview, reaffirm interest and ask for the timeline if they didn't give one. 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
Thank them for a specific part of the conversation, add one example you didn't get to, and restate interest in the actual work. Keep it under 150 words. Then stop. Daily pings after interviews read as panic, not enthusiasm. 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.