The short version: a month of DTC email plans itself once you stop asking what should we send and start assigning jobs to slots. Every campaign does one of four jobs (value, proof, product, community), the week has a rhythm that rotates them, the month has one theme that gives the rotation a spine, and the season overlays on top. Plan it in a single one-hour meeting using the agenda at the bottom, and the calendar stops being a creative crisis and becomes an assembly line that happens to produce good email. This is the planning SOP we run internally, in full: the four jobs with their copy shapes, the grid itself, the segmentation defaults backed by the published lift data, two worked months, and the metrics loop. The how-many-emails question gets its own post and calculator; this one assumes you have picked your number.
The four campaign jobs
Every campaign on the calendar declares one primary job before anyone writes a subject line:
- Value: the email that would be worth opening if you sold nothing. Education, how-tos, the guide content your vertical's welcome flow runs (routine education for beauty, rigging guides for outdoor, recipes for F&B). Value emails are why the list opens the other three types. Copy shape: one useful idea taught completely, product presence limited to the worked example, CTA soft (read more, shop the ingredient) rather than commanding.
- Proof: reviews, UGC, before-and-afters, customer stories, press. The believability layer, harvested by your post-purchase flows and spent here. Copy shape: the specific beats the general (one customer, one outcome, one honest timeline outperforms a wall of five-star quotes), and segment-matched proof beats generic proof everywhere the properties allow.
- Product: launches, restocks, bestsellers, seasonal pushes: the direct ask. Most brands' calendars are 90% this, which is exactly why their lists stop opening. Copy shape: one product or collection as the star, the price stated plainly, one CTA, per the launch sequence's announcement discipline.
- Community: the founder note, the behind-the-scenes, the customer spotlight, the mission update. Lowest direct revenue, highest replies and durable engagement, and the send that makes the brand feel run by people. Copy shape: plain-text-adjacent, first person, a real reply-to, and an actual question, because replies are this job's conversion event and they help deliverability besides.
The weekly rhythm
At the common two-to-three-sends-per-week cadence, the default week is: one product email, one value or proof email, and (at three) one flex slot that rotates community, a second proof, or the seasonal beat. The ordering matters less than the ratio: across a month, the list should receive roughly half job-one-through-three content for every direct product ask, because the non-product sends are what keep engagement (and therefore deliverability, per the engagement mechanics) healthy enough for the product sends to land. Brands at lower cadence keep the same ratio with fewer slots; the one-send-per-week brand alternates product and value weekly. The ratio is also the first diagnostic when the frequency guardrails trip: before cutting volume, check whether the calendar quietly drifted product-heavy, because ratio drift and cadence excess produce identical symptoms.
The grid: what the calendar physically is
One spreadsheet, five columns per send: date, job, topic (one line), audience, owner-and-status. Twelve to sixteen rows a month at typical cadence. That is the whole artifact, and its plainness is the point: the grid answers what is going out Tuesday at a glance, survives handoffs, and makes ratio drift visible by simply counting the job column. Anything fancier (the color-coded multi-tab planner) gets abandoned by February; the five-column grid outlives the person who made it. The vertical variants (supplements, fishing and outdoor) add one column each (the compliance check, the season block), never five.
The monthly theme
One theme per month gives the rotation a spine and cuts planning time in half, because every slot inherits its angle instead of starting blank: hydration month for the beauty brand (value: the barrier-repair guide; proof: dry-skin before-and-afters; product: the moisturizer line; community: the founder's winter routine). Themes come from three calendars stacked in priority order: the merchandising calendar (launches and restocks), the seasonal calendar (the vertical's real-world rhythm), and the education calendar (the topics your content pillars owe the list). A launch month's theme is the launch, per the launch takeover rule; a quiet month's theme is whatever education pillar is due.
The seasonal overlay
The theme system flexes for the calendar's hard points rather than fighting them: BFCM compresses the ratio toward product (the flow adjustments and vertical playbooks govern that window), gift seasons pull the proof-and-guide content forward per the occasion logic, and seasonal verticals plan pre-season, in-season, and off-season months as three different ratio profiles per the seasonal architecture: education-heavy before the opener, product-forward during, community-and-care after.
Segmentation defaults per job, and why they pay
The lift data makes segmentation a default, not a nice-to-have: segmented campaigns click 50% higher than unsegmented ones, 58% of email revenue traces to personalized and segmented sends, and segmented programs generate up to 760% more email revenue than batch-and-blast. The calendar pre-decides audiences so nothing ships to everyone by accident: product emails go to engaged segments (the unengaged window stays excluded, per the sunset rules), value and proof emails can stretch one engagement tier wider (they re-warm at low risk), community sends go to the engaged core, and every campaign respects the standing suppressions: active flow recipients in recovery windows, dunning profiles, and subscribers excluded from acquisition offers. The vertical properties (the goal, concern, species, and room fields the welcome flows capture) turn any campaign into two or three sharper versions when the content supports it, and the grid's audience column is where that decision gets made on purpose instead of at send time.
Worked month one: a beauty brand, hydration theme, 10 sends
Week one: value (the barrier-repair guide, concern-segmented) + product (the moisturizer line feature). Week two: proof (dry-skin before-and-afters with honest timelines) + product (the hydrating routine bundle) + flex: community (the founder's winter routine, replies invited). Week three: value (the humidifier-and-skincare myth-buster) + product (bestseller feature with reviews woven in). Week four: proof (UGC roundup from the month's post-purchase harvest) + product (the bundle's last call as the theme closes) + flex: the next-month tease. Ratio: six non-product-forward against four product; every value and proof send shipped in concern-segmented variants per the 50%-higher-CTR rule.
Worked month two: a supplement brand, launch takeover, 8 sends
The new SKU's launch month, run per the launch sequence: week one: value (the mechanism story as the tease's long-form companion) + product slot one: the tease itself. Week two: product slots two and three: early access and launch day + proof: the ingredient's research digest. Week three: product slot four: the proof follow-up with first reviews + community: the founder's why-we-built-it. Week four: value (the how-to-stack-it guide) + proof (week-one customer quotes). The launch consumed every product slot and the theme; the four-job ratio held anyway, which is exactly the point of the takeover rule.
The one-hour planning meeting
Monthly, same agenda, five parts: (1) ten minutes: last month's numbers by campaign job, clicks and revenue per send, not opens; (2) five: confirm the month's theme against the three calendars; (3) twenty: fill the grid, jobs first, topics second, subject lines never (those belong to the writer, later); (4) fifteen: audience and suppression check per slot, plus the flow-collision scan (no campaign lands on a segment mid-recovery-window); (5) ten: assign owners and deadlines. The output is a grid anyone can execute; the meeting never writes copy. Two failure modes to guard: the meeting that becomes a copywriting session (kill it at minute one; the grid dies when wordsmithing eats the hour), and the meeting that skips step one (a calendar that never reads its own results is a superstition generator).
What to measure
- Revenue and clicks per send by campaign job, monthly: the ratio tuning signal. Product sends winning on revenue while value sends win on clicks is the system working, not a problem
- Engagement trend of the sending segment (click reach: unique clickers over 30 days), the health metric the ratio protects
- Segmented-versus-generic lift on the sends that shipped both ways, your own version of the published 50% CTR gap, which funds (or retires) the segmentation work with your own data per the testing SOP
- Unsubscribe and complaint rate per send, watched against the campaign job: a value email generating product-email-level unsubscribes was mislabeled
- Reply volume on community sends, that job's real conversion event
- Theme-month performance versus unthemed months, the honest test of whether the spine is earning its planning time
Frequently asked questions
What should a DTC brand's email calendar contain each week?
A rotation of four jobs: value, proof, product, community, at roughly one direct product ask per one-to-two non-product sends. The ratio is the strategy; the topics fill in from the monthly theme.
What does the calendar document actually look like?
A five-column grid: date, job, topic, audience, owner. Twelve to sixteen rows a month. Plain enough to survive handoffs and make ratio drift countable at a glance.
Should campaigns be segmented by default?
Yes, wherever the content supports it: segmented sends click 50% higher and segmented programs out-earn batch-and-blast by documented multiples. The grid's audience column makes it a planning decision instead of a send-time afterthought.
How far ahead should the calendar be planned?
One month in detail, one quarter in themes. Further than that is fiction in DTC; less than that turns every week into a scramble.
How do launches fit the calendar?
A launch takes over the theme and the product slots, per the launch sequence's five beats, while the value and proof slots feed it. The four-job ratio holds even in launch months.
Who should run the planning meeting?
Whoever owns retention, with merchandising in the room. The agenda is five steps and an hour; the meeting fills a grid and assigns owners, and copywriting happens after, never during.
Does this replace flows?
No: flows are the automated floor (nearly 41% of email revenue from 5.3% of sends in Klaviyo's data), and campaigns are the variable layer on top. The calendar governs campaigns; the flow stack governs the rest.
Sources
- Mailmend. Email personalization and segmentation statistics.
- Klaviyo. Email marketing benchmarks.
- Mailflow Authority. Apple Mail Privacy Protection and engagement measurement.