Content operations for SaaS teams

Most content programmes do not fail on strategy. They fail because the draft sat in someone’s inbox for nine days, the SME cancelled twice, and the piece published three weeks late with an edit nobody had time to do properly. Treat content as a production line with measurable cycle time and most of those problems become visible before they cost you a quarter.

What are the nine stages from idea to published?

Nine, and skipping any of them just moves the work somewhere less visible. Each needs an owner and an SLA, because a stage with no clock on it will expand to fill the month.

Stage nine is the one that separates a content operation from a content calendar. Without it, nobody ever learns whether the brief was right, and the intake scoring in stage one never improves.

Who owns what? The content RACI

Seven roles. In a small team one person holds three of them, which is fine as long as the accountability is still written down. Ambiguity here is what produces the piece that nobody owns and nobody ships.

Two deliberate choices in that table. The editor is accountable for the QA gate rather than the publisher, because quality must be someone’s job and publishers optimise for throughput. And the strategist is accountable for the day-30 review, which closes the loop back to intake scoring where it belongs.

What are the stage-level SLAs and what is a healthy cycle time?

Eighteen to twenty-five working days from approved brief to publish. That is the benchmark for a standard piece with one review cycle, and it is achievable for a team of three with a functioning process.

Measure cycle time per piece and chart the distribution, not the average. The average hides the problem. What you want to see is a tight cluster around 20 days with few outliers. A bimodal distribution, with half the pieces at 15 days and half at 45, usually means one review stage has no owner.

Rework rate is the companion metric. Count the share of drafts requiring a third revision round. Under 15 percent, your briefs are good. Above 30 percent, stop adding volume and fix the brief template, because every rework round consumes editor capacity you cannot replace quickly.

How do you calculate content capacity properly?

Work backwards from the editor, because the editor is the constraint in every content team I have seen.

One full-time editor sustains 8 to 12 substantive pieces a month. Call it 10. Each of those pieces needs roughly 0.6 to 0.8 writer-weeks, so ten pieces need about 1.5 to 2 writers. Briefs take a strategist half a day each, so ten briefs are 5 days, which is one strategist at roughly 25 percent allocation plus their other work.

That gives you the standard unit: one editor, two writers, a part-time strategist, ten pieces a month. Scale in whole units. Trying to get fifteen pieces out of one editor by adding a third writer does not work, and the failure is delayed enough that you will not connect cause to effect.

SME interview capacity is the other ceiling, and it is external to your team. If your product lead can do four interviews a month, you have four SME-led pieces a month, regardless of budget. Negotiate that number explicitly with whoever owns those people, and treat it as a fixed input to the plan rather than a variable you can push. The same constraint shapes what is realistic in vertical SaaS content, where subject expertise is less substitutable than in horizontal categories.

Which tool should run content operations?

Airtable, Notion or Asana. All three work, and they fail differently, so choose on the failure you can live with.

Tool	Strength	Where it breaks	Pick it when
Airtable	Per-piece metadata, views, reporting on cycle time	Drafts live elsewhere, so you get two sources of truth	You need to report on the process itself
Notion	Briefs, drafts and calendar in one place	Reporting is weak, and databases sprawl without discipline	The team already lives in Notion and volume is under 12/month
Asana	Task conventions shared with the wider marketing team	Content-specific metadata feels bolted on	Content sits inside a larger marketing org
The CMS itself	No handoff at all	Poor for anything before the draft stage	You publish under 4 pieces a month

The decision that matters is who owns the CMS handoff. If your publisher works in the CMS and your writers work in Google Docs, you need one system that tracks the piece across both, and that system should be whichever one the publisher will actually update. A perfect Airtable base that the publisher ignores is a reporting fiction.

Generative tools now sit inside several of these stages, mostly at research, outline and first-pass QA. Where they help and where they quietly degrade output is worked through in AI-assisted content production for SaaS. The broader tooling picture, including SEO, brief and QA tools, is in the SaaS content marketing tool stack.

What does the reporting ritual look like?

Two meetings and one dashboard. Anything more is process for its own sake.

Weekly, 30 minutes. Pieces in each stage, anything past SLA, SME bookings for the next two sprints, and blockers. This is an operations meeting. No discussion of topic quality, no strategy debate, no traffic numbers. Just where things are and what is stuck.

Monthly, 60 minutes. Published count against plan, cycle time distribution, rework rate, on-time publish rate, and the day-30 reviews for pieces published last month. This is where you decide whether to change the brief template, the writer mix or the intake scoring.

The dashboard. Six tiles: pieces published this month versus plan, median cycle time, rework rate, on-time publish rate, pieces in each stage, and SME interviews completed. Traffic and conversions belong on the performance dashboard, not this one. Mixing production metrics with outcome metrics makes both harder to act on, and the outcome side has its own benchmarks in SaaS content marketing benchmarks.

What this costs and what goes wrong

A ten-piece-a-month operation costs roughly $18,000 to $32,000 monthly fully loaded, depending on whether writers are staff or freelance and how much SME time you count. That is before design and distribution. The per-piece maths and the in-house comparison are in what SaaS content actually costs.

Three failure modes worth naming plainly.

Process theatre. A fifteen-field brief template, four approval stages and a weekly governance meeting for a team publishing six pieces a month. The process costs more than the content. Match process weight to volume, and strip a stage whenever you cannot name what it caught in the last quarter.

The heroic editor. One person holds the whole system together through personal effort and institutional memory. It works beautifully until they take a holiday. Document the brief template, the style rules and the publishing checklist, and have someone else run a full cycle once a quarter.

Refresh capacity never allocated. Every piece you publish becomes a piece you eventually have to update. Allocate roughly 20 percent of monthly output to refreshes from month twelve onward. Teams that do not end up with a library where a third of the pages are quietly wrong, which is worse than not having published them.

Where to start

If you publish fewer than eight pieces a month, do not build this. Use a shared calendar, one good editor and the editorial calendar template for SaaS teams, and get on with writing.

Above eight, instrument the nine stages, put an SLA on each, and start measuring cycle time and rework rate this month. You will find your queue problem within two sprints. Then read the SaaS content engine playbook for the volume side and the customer story engine for the format that most consistently justifies the interview overhead. The strategy that sits above all of this is covered across the SaaS content marketing hub.