Build a content calendar from competitor newsletters

A content calendar from competitor newsletters is not a copy job. It is reading a set of experiments other people already paid to run. When a rival sends a pricing teardown and the next fortnight three more do the same, that is not a coincidence, it is a demand signal you can schedule against. Most calendar advice starts with a blank grid and a brainstorm. This starts with eight weeks of other people's send logs.

I have built these for our own sends and rebuilt them for clients, and the pattern holds: the topics a serious newsletter returns to are the topics that earn engagement, because editors drop what does not work fast. So the recurring slot is the tell. Below is how to pull that signal out of a tracked set and turn it into a four-week grid you can actually publish from.

Why competitor sends beat a blank-spreadsheet brainstorm

A brainstorm produces ideas ranked by how good they sound in a meeting. A competitor's send history produces ideas ranked by what an editor chose to ship again. Those are different lists. The second one is a leading indicator because a newsletter that keeps a monthly "state of the market" issue has already tested it against its own open and click numbers and kept it. You are reading the output of a decision, not the decision itself.

There is a second reason. Recurring slots reveal editorial commitments, and commitments are predictable. If Lenny's Newsletter runs a deep dive every Tuesday and a lighter roundup on Thursday, you can plan around that rhythm months out. A blank calendar gives you no such anchor. This is the same logic behind our competitor content gap analysis, only pointed forward instead of backward: gap analysis tells you what is missing, cadence reading tells you when it will be missing next.

What to pull from each newsletter you track

Five fields per send is enough. Date, topic, subject-line theme, call-to-action type, and send day with time. That is the whole log. Everything useful downstream comes from those columns.

• Cadence: how many sends per week, and whether it holds or drifts. A steady 2 per week means something different from a burst of 5 before a launch.
• Recurring topic slots: the issue that comes back on a schedule. Weekly market recap, monthly teardown, quarterly report.
• Subject-line themes: curiosity, number-led, direct benefit. We score these on every tracked send, and the mix tells you what a rival believes drives their opens.
• Call-to-action type: subscribe push, product link, sponsor slot, reply prompt. The CTA rhythm shows where the newsletter earns its money.
• Send day and time: the input to timing, covered in depth in our competitor send-time analysis.

Log the send day even when it looks random. Across the senders we track, the "random" ones usually resolve into a two-day window once you have six weeks of data. Substack and beehiiv writers drift more than Mailchimp and Kit senders on a corporate schedule, but almost everyone has a home base once you plot it.

From tracked feed to a four-week grid, step by step

The method is five steps, and the first four are cheap. Only the last one asks you to make a call.

1. Pick 5 to 8 rivals. Direct competitors plus one or two adjacent senders whose craft you rate. Fewer than five and one weird sender warps the average. More than eight and the topic clusters turn to mush.
2. Log eight weeks of sends. Eight weeks is the shortest window that surfaces a monthly slot twice, which is what you need to trust it is a slot and not a one-off.
3. Cluster the topics. Group the 80 to 120 sends you now have into 6 to 10 themes. The count of sends per theme is your demand ranking.
4. Mark the cadence gaps you can own. Find weeks where a theme with strong pull went quiet across the whole set. That silence is a slot nobody is serving.
5. Slot your calendar. Put the high-pull themes on the days the set clusters around, then fill the gaps you found in step 4 with your own angle.

Steps 1 through 3 are mechanical, and this is where tracking competitor newsletters with a tool saves the eight weeks of manual inbox logging. Step 4 is the one that pays. A gap is worth more than a crowded theme, because a crowded theme means you are the fifth voice that fortnight while a gap means you are the only one.

Reading cadence and the seasonal spikes

Cadence is the base layer, spikes are the interesting part. Base cadence tells you the normal week. In our send-frequency benchmark the common settling point for B2B senders is 1 to 2 issues a week, and most of the set you track will sit there. The days themselves cluster too. Tuesday through Thursday holds for the senders we score, which lines up with the industry patterns in our best-day-to-send breakdown.

Spikes break the base pattern, and they cluster. Watch for the fortnight before Q4 when the whole set lifts send frequency for buying-guide and roundup content, and the first two weeks of January when planning and prediction issues stack up. When you see four rivals raise cadence in the same window, that is the market pulling, not four editors having the same idea by chance. Plan a heavier publishing week into that window and a lighter one into the flat stretches, usually mid-summer, when the same set goes quiet.

The 60/40 rule: mirror versus your own bets

Here is the honest cost of this whole method, and it is the part most competitor-tracking advice skips. A calendar built from competitor sends lags. You are always reading what already shipped, so if you mirror everything, you publish a cycle behind and your newsletter reads like a slower echo of four better-known ones. That is a real risk, not a hypothetical.

So cap the mirroring. Roughly 60 percent of your slots track the demand you read from the set, and 40 percent go to bets no competitor is running. The 40 percent is where you get ahead of the pattern instead of trailing it, and it is where your own first-party data and opinions live. I would rather ship a calendar that is 60 percent mirror and genuinely on time than one that is 90 percent mirror and permanently late. The split is a dial, not a law. If your niche moves slowly, push mirroring higher. If you have a real data advantage, spend more of the grid on original bets and let the set catch up to you.

A worked example: six B2B SaaS newsletters

Say you track six B2B SaaS newsletters for eight weeks and end up with 94 sends. Clustering gives you six themes: product teardowns (24 sends), pricing and packaging (11), hiring and team (9), fundraising commentary (8), tactical how-tos (31), and market recaps (11). Teardowns and how-tos dominate, and both cluster on Tuesday and Wednesday. Pricing ran heavy in weeks 2 and 3, then went dark for a month.

That dark month is your slot. Pricing had clear pull, then the whole set dropped it, most likely because it is harder to write than a how-to. So you slot a pricing piece into week 5 on a Wednesday, with your own numbers, when nobody else in the set is covering it. The teardown and how-to slots you fill on the crowded days but with a format the set is not using, maybe a short annotated screenshot series instead of long prose. If you want to see how to reverse a single rival issue into its underlying choices, our Panoramata comparison walks through where a timeline view helps and where scoring the actual send content pulls ahead.

The grid that falls out: weeks anchored on Tuesday and Wednesday high-pull themes, one owned gap slot per fortnight, and roughly four in ten slots held for your own material. That is a calendar you can defend in a planning meeting, because every row points at a send that already happened.

Frequently asked questions

How do I turn competitor newsletters into a content calendar?

Track 5 to 8 rivals for about eight weeks, log every send with its date, topic and call to action, then cluster the topics. The recurring clusters become your calendar rows and the send days become your slots. Reserve 30 to 40 percent of your own slots for topics none of them are running, so you are not always a cycle behind.

How many competitors should I track for content planning?

Five to eight is the useful range. Fewer than five and one erratic sender skews the pattern. More than eight and the topic clusters blur together because you are averaging across too many editorial voices. Pick direct rivals plus one or two adjacent senders you admire.

How far ahead can a competitor-based calendar plan?

Four weeks reliably, eight weeks for seasonal beats you can see coming, such as Q4 buying guides or January planning content. Past that the signal decays because competitors change their own plans. Treat the near weeks as fixed and the far weeks as pencil.

Should I copy competitor newsletter topics?

No. Copy the demand signal, not the content. If four rivals all ran a pricing teardown in the same fortnight, that tells you the topic has pull right now. Your job is to publish into that window with a sharper angle, your own data, or a format they did not use.

What tools track competitor newsletter cadence?

Newsletrix logs every tracked send and scores its subject line, call to action, send day and topic, which is the raw material for a calendar. Panoramata offers a timeline view of the same idea. You can also do it by hand in a spreadsheet if you subscribe to each rival and log sends as they land.

Related reading