← All blueprints

Content Calendar

Our content plan lives in four different docs and nobody trusts any of them.

One calendar for every post, newsletter and launch, with the owner, channel and status of each piece.

No.
004
Department
Marketing
Build time
1 hr
Difficulty
Beginner
Team size
2–15 people
Replaces
CoSchedule
OctoberALL CHANNELSMTWTFSS12345678910111213141516171819202122232425262728293031Pricing teardownTUE 14 · BLOGOctober newsletterWED 15 · EMAILCustomer storyFRI 17 · LINKEDIN+ Add a piece123

Parts

  • 1

    Publishing calendar

    Month view of everything going out, colour-coded by channel.

  • 2

    Scheduled pieces

    Each piece has an owner, channel, status and a link to the draft.

  • 3

    Add a piece

    Drop an idea on a date; it starts life as 'Idea' and moves to 'Published'.

  • 4

    Idea backlog

    A list of unscheduled ideas anyone on the team can add to.

Data model

  • Piece { title, channel, owner, status, publish_on, draft_url }
  • Channel { name, color }

Build prompt

prompt.txt
Build an internal tool for my team: "Content Calendar".

The problem: Our content plan lives in four different docs and nobody trusts any of them.
Who uses it: a team of 2–15 people.

What it should do:
- Publishing calendar: Month view of everything going out, colour-coded by channel.
- Scheduled pieces: Each piece has an owner, channel, status and a link to the draft.
- Add a piece: Drop an idea on a date; it starts life as 'Idea' and moves to 'Published'.
- Idea backlog: A list of unscheduled ideas anyone on the team can add to.

Data:
- Piece { title, channel, owner, status, publish_on, draft_url }
- Channel { name, color }

Constraints:
- Built for one team inside one company. Simple sign-in (or none), no billing, no multi-tenant setup.
- Fast, calm and obvious enough that teammates need zero training.
- Data must persist and be shared across the team.
- Ship the simplest version that works, then tell me what you'd add next.

Works with Claude, ChatGPT, Cursor, Lovable, Replit or Type.

Variations

  • Slack reminder two days before something is due
  • Campaign tags to group pieces around a launch
  • A public 'coming soon' page for your community

A new blueprint every week

Sent on Sundays. One tool per email.

More blueprints