I built a content calendar that fills itself in (prompt included)

What does a content calendar need to do?

Strip away the dashboards and a content calendar answers three questions: what am I publishing, where, and when? For most creators, founders and small teams that's the whole job. You need a list of ideas, a channel against each one, a status so you know what's drafting versus scheduled, and a date so nothing slips.

The hard part was never the idea. It's the upkeep. A calendar is only useful if it reflects what's really happening, and updating statuses and dates by hand is the chore that gets dropped the week things get busy. That's the same trap we hit with the CRM we built last time: the structure is easy, the maintenance is what kills it.

How do you build a content calendar without a template?

Three steps, all in plain language:

1. Connect AgentDocs to your AI agent. It works in Claude and ChatGPT over a single link, with no install and no card.
2. Describe the calendar you want. Tell your agent the channels you post to and the few things that matter for each piece (the idea, the channel, the status, the publish date, who owns it). It creates a Database with those fields: a real structured table, not a wall of text.
3. Start filling it. "Add a LinkedIn post about the new pricing page, drafting now, target next Tuesday." Your agent files it in the right columns.

You never open a settings panel and you don't start from a template you have to bend to fit. The structure comes from the conversation, and you can change it later by asking.

Can the AI keep the calendar up to date?

Yes, and this is the part that makes it stick. Once the Database exists, the everyday moves are all sentences:

• Add an idea: "Quick one for the newsletter, a behind-the-scenes on how we ship, no date yet."
• Move it along: "The launch post is written, schedule it for Friday morning."
• Mark it done: "The Tuesday LinkedIn post went live, mark it published."
• See the gaps: "What's scheduled for next week, and what's still sitting in Idea?"

Because your agent both reads and writes the same Database, the calendar reflects reality without you doing the row-finding and typing. Telling it what happened is the update.

What does the AgentDocs Database give you here?

A Database is a real structured table with typed columns, not a chat thread your agent has to re-read each time. So a status is a status it can filter on, and a publish date is a date it can sort and check against today. That's what lets you ask "what's overdue?" or "what's drafting for August?" and get a straight answer.

Because your agent reads and writes the same table, you can pull the calendar into a Sheet for a quick export, or have it draft the next post straight from the brief in the Notes column, with no copy-paste between tools. A Notion- or Coda-style workspace gives you nice calendar views, and you can keep using one. The difference here is that your AI agent does the upkeep, so the calendar matches what you're really publishing.

What does it cost?

AgentDocs has a free tier with no per-seat fees. You connect over one link with no install and no card, and there's a Pro tier with generous fair-use limits for heavier use. Billing isn't switched on yet, so it's a low-friction way to try the idea on your own pipeline. It's a new product, so pricing may change as it settles.

The exact prompt

Paste this to your AI agent once AgentDocs is connected. Edit the fields in brackets to match how you work:

Build me a content calendar in AgentDocs.

Create a Database called "Content calendar" with these columns:
- Title / idea
- Channel [e.g. Blog, LinkedIn, X, Newsletter, YouTube]
- Status [Idea, Drafting, Scheduled, Published]
- Publish date (date)
- Owner
- Notes / brief
- Link

Rules for keeping it current:
- When I tell you about a piece of content, find the right row (or add one),
  and update Status, Publish date and Notes.
- A new idea starts as Status: Idea with no date until I set one.
- When I say something is written or queued, set it to Scheduled with a date.
- When I say it went live, set it to Published and add the Link.
- Keep one row per piece, and flag anything Scheduled whose date has passed.

Then confirm the table is set up and ask me for my first few ideas.

That's the whole thing. No template to download, no fields to wire up. You describe it, your agent builds it, and from then on you just tell it what's happening.

This is the second in our "Built in AgentDocs" series, real things built by talking to an AI agent, with the prompt included every time. Next up: a weekly review doc your agent drafts from the week's notes.