Minimum Viable Product: Development Email Calendar with Production Deadlines
The goal of this article is to outline a barebones development email calendar with production processes and deadlines included. These emails are in addition to a Welcome Series which is automatically sent to any new subscribers, and may also be sent to current readers if they have not already received a Welcome Series. An article on that topic will be forthcoming.
The strategy starts with two essential email types (active fundraising and relationship building emails) and then adds in a third email (Fireside Chats) to move donors into a more active relationship with the organization.
Relationship building emails can include passive donate options -a Support Org Button at the bottom of the email- or exclude the donate option and focus entirely on the primary CTA for the reader. I personally like to pair relationship-building emails with fundraising asks later on down the line. This is a common strategy seen in Inbound Marketing and the NextAfter/MECLabs systems.
Calendar Rules
2–3 emails a month (1-2 Relationship Building, 1 Ask)
No more than 1 email should go out a week. In the case of multiple audiences, this rule should also apply. -EG if a supporter is also a client, they should not receive an email from both lists on the same day. Depending on the size of the multiple audiences, I’d recommend moving those emails to a third day and send out emails to both mutually exclusive lists on the ideal day).
Production on emails should be completed 1-2 days before the email date. (Note: Many email platforms will not allow you to send an email in a shorter time than 24 hours.)
Master calendar should be constructed to include all known email dates. Lists should be mutually exclusive to allow multiple lists to email on the optimum dates.
(Current research indicates Sunday evening, Tuesday morning, Thursday afternoon).
Emails that are included on multiple lists should defer to their primary lists and receive the second list email on a second date
Email Elements
All Development emails have the following elements:
- Type: Relationship Building (Ask/No Ask), Donate, or Fireside Chat
- CTA: Donate or Edify
- CTA Type: Survey, download free content, article to read,
- Link: URL that the email will forward to
- Writer: The person who is actively writing the piece. This person will also likely be the signer but in larger orgs likely won’t be.
- Signer: This is the person who is putting their name to the email. Will likely be the org’s president, a department director, or a staff member who has high prestige
- Editor: This is the person who reviews the piece, tests the links, and likely schedules the email to go out. This person should not be both the writer and signer. This is to make sure that at least two people review the piece before it goes live.
- UTM Code: Useful for tracking the email’s performance
Special Type of Email (Fireside Chat)
Fireside Chats – This email is written by the president -or at least in the president’s voice- and specifically focus on financial supporters to build a relationship with them so that they see themselves as financial partners in the organization’s work.
This relationship is achieved by tying the mission, vision, values, and principles of the organization with products that the organization currently produces.
The short-term goal of the Fireside Chat email type is to edify the reader -mainly financial supporters- with content that will help them to more closely identify with the organization’s mission and give the reader a real understanding of what the organization does and accomplishes.
The long-term goal is that the reader identifies with the organization and feels a personal sense of ownership over the great work that the organization does. The financial supporter will feel a sense of pride and familiarity with the organization’s clients and the financial supporter will understand that they are not just passive investors but active partners in the organization’s work.
A note about language. While financial supporters can be called donors, I prefer to frame development as about converting financial supporters who passively invest in the organization into financial partners who share the organization’s values and see themselves as actively involved in promoting the organization’s work. You can read more about donors as financial partners here.
The Calendar
Month 1.
Week 1.
Week 2.
Week 3.
Week 4.
Week 5 (When applicable).
Month 2.
Week 1.
Week 2.
Week 3.
Week 4.
Week 5 (When applicable).
Month 3.
Week 1.
Week 2.
Week 3.
Week 4.
Week 5 (When applicable).
Month 4.
Week 1.
Week 2.
Week 3.
Week 4.
Week 5 (When applicable).
Month 5.
Week 1.
Week 2.
Week 3.
Week 4.
Week 5 (When applicable).
Month 6.
Week 1.
Week 2.
Week 3.
Week 4.
Week 5 (When applicable).
Month 7.
Week 1.
Week 2.
Week 3.
Week 4.
Week 5 (When applicable).