Campaign Calendar Collision Guard
A single shared marketing calendar that catches collisions - two big sends to the same segment on the same day, overlapping promos, or a launch landing on a holiday - before anything gets scheduled.
A login-protected shared calendar where every planned campaign is checked against your own collision rules and blackout dates before it can be confirmed - conflicts pause for an owner to approve, reschedule, or override with a logged reason, and you can export a clean monthly CSV.
Before you start
- A Google Sheet or CSV of planned campaigns (name, owner, channel, segment, start/end dates, status)
- A holiday / blackout date list
- A list of your target segments
- Free Vercel, Supabase, and Resend accounts
The problem this kills
Your email calendar lives in one spreadsheet. Social has its own. Paid is a third tab nobody opens. So nobody sees the whole picture - until two big sends hit the same segment on the same morning, a promo overlaps another promo, or a launch quietly lands on a holiday when half your list is offline.
By the time someone notices the collision, the campaign is already scheduled or already out the door. You apologize, you reschedule, you lose momentum. The fix is never "work harder" - it's having one place that knows every planned campaign and refuses to let a new one clash without a human signing off.
What you'll build
A single shared marketing calendar that every planner uses. When someone drafts a campaign - name, owner, channel, target segment, start and end dates - the tool checks it against everything already on the calendar and against your blackout dates. If it collides, the entry lands in a "needs decision" state instead of being confirmed. A calendar owner sees the conflict spelled out, then approves it anyway, reschedules it, or overrides it with a logged reason. Only then does the slot turn green and confirmed.
You get a month view and a week view, automatic warnings on near-duplicate campaign names launching within a week of each other, and a one-click monthly CSV export in the exact columns your team already uses.
What's inside the Implementation Plan
The plan opens by interviewing you about your business - your channels, your real segment names, how you name campaigns, your busy seasons, and the collision rules that actually matter to your team (same segment same day? a cap of how many emails per week? which dates are blackout?). It reads a short tailored spec back to you and waits for your thumbs-up before building anything. Nothing in this plan is a generic template - the data model, the rules engine, and every screen are shaped by your answers.
From there it walks you, one copy-paste prompt at a time, through standing up the app, loading your campaigns, wiring the collision rules, building the approval gate, and shipping the calendar views and CSV export. You never write code - you paste prompts and answer questions.
The governance it includes (this is the point)
- Login so only your team can see or touch the calendar.
- Row-level security so each organization only ever sees its own campaigns - even on shared infrastructure.
- A complete audit trail - who drafted, who approved, who overrode and why, with timestamps.
- A human-in-the-loop approval gate - a colliding campaign cannot be confirmed until an owner reviews and resolves it. The tool flags; a person decides.
- Duplicate guards - the same campaign (name + start date) can't be entered twice, and you get warned about near-duplicate names launching within seven days.
Who it's for
Marketing ops leads, content managers, and small teams juggling email, social, and paid in separate calendars who are tired of finding out about collisions after they ship. If you can fill in a spreadsheet, you can build and run this.
You've got this - paste the first prompt and let the interview tailor it to your team.