Questions worth asking before you trust a tool with your content.

The calendar is in here — multi-view, by beat, channel, or author — and it's good. But a calendar only tells you what's due. Rundown runs the whole loop around it: deciding what's worth making, moving it through production, sharpening it, publishing, and tracking what worked. The calendar is one stage, not the product.

Content-ops tools (DivvyHQ, Kapost, GatherContent) route work through a pipeline — assign, approve, publish. Rundown does that, more lightly, but it isn't the point. The point is a teammate that helps you make the content better: ideation, coverage strategy, and editorial feedback that ops tools don't touch.

A hand-built setup tracks your content; it doesn't help you make it. Rundown gives you the planning views, status, and assignments your spreadsheet does — plus the things you can't build in Airtable: coverage-gap detection against your archive, and a Desk Editor that reads your drafts. One tool instead of a spreadsheet plus ten tabs.

No. Desk Editor critiques — it surfaces questions, scores sections, and offers suggested lede or headline replacements you can copy if you want them. It never modifies your draft in place, never auto-publishes, and never approves work on your behalf. Your team writes where they already do; Rundown reads, plans, and sharpens around it.

You shouldn't trust it blindly, and we don't ask you to. The companies that embarrassed themselves used AI to write articles and shipped them under bylines without review. Rundown does the opposite — it reads what your humans wrote and asks the questions a senior editor would. Every finding cites the paragraph, sentence, or phrase it's about, so you can verify in five seconds whether it's right.

Team is flat per workspace — writers, editors, freelancers, legal, designers, and clients are all included. You only move tiers when you exceed the per-month critique volume or need agency- or newsroom-specific features. We deliberately avoid per-seat pricing because it punishes the workflow we want you to have: invite everyone who touches a piece.

Your team keeps writing and making things where they already do — Google Docs, your CMS, Canva. Rundown is the planning, workflow, and editorial layer around it. WordPress and Ghost are native at launch; Webflow, Beehiiv, and Sanity follow. Anything else? We export clean HTML and Markdown that works with any CMS that takes a paste.

You upload 10–20 representative published pieces during setup. Rundown extracts your house-voice features — sentence-length distribution, specificity ratio, attribution patterns, lede conventions, archive themes — and uses them as the baseline for voice and continuity checks. The model never trains on your content; the voice profile is a structured set of constraints applied at inference.

U.S.-East hosted, SOC 2 in progress. Your drafts, assets, and critique history are workspace-scoped — no cross-customer training, no analytics-pixel tracking on your published pages. Reports are generated on demand against your own workspace and aren't shared. Full details in our privacy policy.

Yes. Fourteen days on the Team tier, no credit card required. We also run a design-partner program for newsrooms — six free months in exchange for active feedback. Reach out via the early-access form if you'd like to be considered.