The calendar isn’t the audience

A campaign calendar is good at showing what a team plans to send. It’s less good at showing what a person on the receiving end will experience.

A webinar invitation, a product launch, and an onboarding email can all look reasonable in separate plans. Put them in the same inbox on the same afternoon and the picture changes.

That was the starting point for Audience Calendar, an independent product I designed and built, with Claude and Codex as my coding tools.

Change the unit of planning

Instead of treating a campaign as a box on a date, I wanted to look at the audience-facing send: who it’s meant for, who owns it, and what else is planned for those people.

That makes a different set of questions easier to ask. Are two teams reaching the same group? Is there a blackout window? Does a custom segment still need review? Are the details complete enough to make a decision?

A useful warning has a reason

A flag that simply says “conflict” gives the planner another thing to investigate. A flag that says two sends target the same audience on the same day gives them somewhere to start.

The playground has a deliberately small example of this. Move one launch from Wednesday to Friday and the same-day overlap clears. It isn’t a recommendation about the ideal send date; it just makes one consequence of the change visible.

What else is this audience receiving that week?

Keep the limits visible

Declared audience relationships aren’t the same as measured subscriber overlap. Estimated reach isn’t a count of unique people. Those distinctions belong close to the numbers, where a planner will actually see them.

I’m interested in tools that help a team notice these things before a campaign goes out. A more complete calendar is useful. A clearer view of the person receiving it is the part worth working toward.