Foundation Program Officer Grant Exploration Email

Role: Senior Philanthropic Partnerships Director with 15+ years securing institutional funding.

Context

• Nonprofit name: {{nonprofit_name}}
• Target grantmaker: {{target_foundation}}
• Program area: {{program_area}}
• Shared impact goal: {{shared_impact_goal}}
• Key proof point or metric: {{pilot_metric}}
• Recipient officer: {{recipient_officer_name}}

Task

Draft a cold outreach email to {{recipient_officer_name}} at {{target_foundation}} to establish strategic mission alignment in {{program_area}} and secure an exploratory 15-minute briefing call.

Method

1. Analyze {{target_foundation}}'s published funding priorities regarding {{program_area}}.
2. Open with a personalized, non-flattering reference to a specific initiative or white paper funded by {{target_foundation}} that mirrors {{shared_impact_goal}}.
3. Position {{nonprofit_name}}'s approach as a direct answer to an unaddressed structural barrier in the field.
4. Introduce the measurable intervention backed by {{pilot_metric}} to validate execution capacity.
5. Explicitly state that this outreach is to explore programmatic synergies rather than an unsolicited grant application.
6. Frame a low-friction call-to-action requesting a 15-minute introductory conversation during upcoming grant planning windows.
7. Provide two clear, compelling subject line options tailored to program officers.

Constraints

• MUST keep the email body between 150 and 220 words.
• MUST NOT ask for a specific monetary contribution or submit an unprompted proposal.
• Subject lines MUST be under 50 characters and avoid generic buzzwords like "Synergy" or "Partnership Request".
• Tone must be collegiate, respectful, and peer-to-peer.

Output format

• Subject Lines (2 distinct options)
• Salutation
• Email Body (3-4 concise paragraphs)
• Sign-off and Professional Signature Block

Self-review

1. Did I reference {{shared_impact_goal}} and {{pilot_metric}} seamlessly without sounding transactional?
2. Is the email strictly under 220 words?
3. Does the call-to-action respect the program officer's workflow and evaluation cycle?