# Build a content engine that ships twelve pieces a month > Three staffing models that all ship twelve pieces a month, with cost per piece, weekly cadence, quality gates and the point where more volume stops paying. Source: https://saas-marketing.net/playbooks/saas-content-engine/ Topic: SaaS Content Marketing Type: playbook Published: 2026-09-11 Last updated: 2026-09-11 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/playbooks/saas-content-engine/ ## Short answer Twelve pieces a month is reachable through three staffing models: an editor plus a freelance bench of six writers at roughly $900 to $1,600 fully loaded per piece, three in-house writers at roughly $1,400 to $2,200, or an agency retainer at $800 to $2,500 per article. The freelance bench is cheapest and most flexible, in-house wins on product depth, and agencies win on speed to start. Hire the editor before the second writer. ## Key takeaways - An editor plus a six writer freelance bench ships twelve pieces a month at roughly $900 to $1,600 fully loaded per piece. - Three in-house writers cost more per piece but produce the product depth freelancers take six months to develop. - Editing capacity caps a SaaS content team, not writing capacity, so hire the editor before the second writer. - Two quality gates matter: brief approval before writing starts and fact check before publish. Everything else is preference. - Freelance rates run roughly $0.40 to $1.20 a word, and the top of that band is usually cheaper per result. - Past roughly fifteen pieces a month most SaaS sites get more return from updating and deepening existing pages. --- Twelve pieces a month is not a hard number to hit. It's a hard number to hit twelve months running without the quality collapsing in month four, which is what usually happens when a founder hires one writer and calls it a content program. Three staffing models get you to twelve. They cost differently, they break differently, and the right one depends on whether your constraint is money, product depth or time to start. ## The three models, priced Same output, three cost structures. Fully loaded means writer fee plus editor time plus subject matter expert time plus design and publishing, which is the only number worth comparing. The freelance bench at twelve pieces a month works out around $13,000 to $19,000 monthly: six writers producing two pieces each at $700 to $1,100 per piece, plus one editor at roughly $8,000 to $10,000 fully loaded, spread across the output. The three-writer in-house team costs $22,000 to $28,000 monthly loaded including the editor, and it buys you something the bench does not. That something is product depth. A freelancer on their second piece about your API writes accurate, generic content. An in-house writer eight months in, who sits in on support calls and knows which feature the sales team keeps apologising for, writes things your competitors structurally cannot copy. If your differentiation is technical, pay for that. Agencies win on one dimension: you can be publishing in three weeks. They lose on institutional memory, because the writer who finally understood your product gets rotated to another account. I'd use an agency for a bounded project, a pillar rebuild or a glossary buildout, and not as the permanent engine. **$900 to $1,600** Fully loaded cost per published piece running an editor plus a freelance bench ## Hire the editor before the second writer This is the position I'd argue hardest for. Content teams cap on editing capacity, not writing capacity. The math is simple. One editor can take a piece from submitted draft to publishable in 60 to 120 minutes if the brief was good, and four to six hours if it wasn't. At twelve pieces a month that's between 12 and 72 hours of editing, which is the difference between a part of one person's job and most of two people's. Writers are easy to add. Editors who can hold a voice, kill a weak angle and fact check a product claim are not. The failure pattern is visible from outside. A company hires two writers, output doubles, and the founder becomes the bottleneck because everything routes through them for approval. Six months later the founder stops reading drafts carefully, quality drifts, and someone concludes content doesn't work. If drafts wait more than three days for a review, your engine is not a production problem, it's a scheduling problem. Put the review slot in a recurring calendar block and treat a missed review the way you would treat a missed standup. ## The weekly operating cadence Twelve a month means three a week, which means the pipeline has to hold about nine pieces at different stages at any moment. Run it on a fixed weekly rhythm and the queue stops needing management. **One week in the engine** Keep the whole thing in one place. Notion and Airtable both work; what matters is that brief, draft, SME notes, status and publish date live in one record, not across Google Docs, Slack threads and someone's inbox. The [editorial calendar template](/templates/saas-editorial-calendar-template/) has the field structure, and [content operations for SaaS teams](/guides/saas-content-operations/) covers governance once more than four people touch the process. ## Brief to publish: what the pipeline actually contains Seven stages, and the first one carries most of the weight. | Stage | Owner | Time | Fails when | | --- | --- | --- | --- | | Brief | Editor or strategist | 60 to 90 min | Written as a keyword and a word count | | SME interview | Writer | 30 min + 30 min notes | Skipped, producing generic content | | Draft | Writer | 4 to 8 hours | No access to the product | | Edit | Editor | 60 to 120 min | Brief was vague, edit becomes a rewrite | | Fact check | Editor or second reader | 20 to 40 min | Nobody owns it explicitly | | Design and publish | Ops or writer | 30 to 60 min | Images and internal links added later, then never | | Distribution | Marketing | 30 min | Treated as optional | A real brief runs 400 to 700 words. It names the reader, the specific question the page answers, the angle nobody else has taken, the three sources to use, the internal links to include and the thing the page must not say. A brief that says "write 1,800 words on SaaS onboarding, target keyword saas onboarding best practices" guarantees a piece that reads like every other piece on the topic, and costs you four extra editor hours to fix. The standards that briefs should enforce are in [editorial standards for SaaS content teams](/guides/saas-editorial-standards/). Thirty minutes with a support lead or a solutions engineer produces the specifics that make content defensible: the actual objection, the real error message, the migration that took three weeks. Transcribe with Descript or Loom and keep the recordings. They become customer stories later, which is the input to a [customer story engine](/playbooks/customer-story-engine/). ## The two quality gates that matter Gate one is brief approval. Nothing gets assigned without a named reader, a confirmed angle and a stated reason the page will be better than what currently ranks. This gate is cheap to run and prevents the most expensive failure, which is a finished draft on the wrong premise. Gate two is fact check before publish. Every number traced to a named source, every product claim verified against the current build, every competitor statement checked against their live pricing page. Assign it to a named person. Shared responsibility here means nobody does it, and a wrong number about Ahrefs or HubSpot in a comparison page is the kind of error that gets screenshotted. Everything else, the tone edits, the headline debates, the two rounds of stakeholder comments, is preference. Preference should not block publishing. Where AI drafting is in the mix, the fact check gate matters more rather than less, and [AI assisted content production](/guides/ai-assisted-content-production/) covers where in the pipeline it holds up and where it doesn't. ## Where more volume stops paying Somewhere between fifty and eighty published pages, the arithmetic flips. New pieces enter a library that is already decaying, and the refresh you're not doing costs more than the piece you are publishing. Signals that you've hit it: pages from eighteen months ago losing positions faster than new pages gain them, your best performing page having no internal links pointing at it from anything published this year, and a keyword list where the remaining terms are all either very low intent or contested by sites with far more authority. At that point reallocate. Six new pieces and six substantial updates per month usually beats twelve new ones, because a refreshed page carries existing links, history and index status. It's also more defensible against AI answer engines, which cite depth and specificity rather than recency alone. What that means for how pages are written is covered in [writing content that AI answer engines cite](/guides/content-for-ai-answer-engines/). One honest cost to name: this model has no slack in it. Twelve pieces a month with one editor means a two week illness puts you four pieces behind and you will not catch up, you will publish nine that month. Build the plan at twelve and communicate ten, or hire a second reader before you need one. ## What to do this week Cost your current per piece number properly. Writer fee plus editor hours times loaded hourly plus SME time plus publishing time, divided by pieces published. Most teams discover they're at $1,800 while believing they're at $600. Then pick the model that fits your constraint and staff the editor seat first. Benchmarks to compare against sit in [SaaS content marketing benchmarks](/research/saas-content-benchmarks/) and [what SaaS content actually costs](/research/content-cost-benchmarks/), and the strategy this engine serves is in [SaaS content marketing](/saas-content-marketing/). ## Frequently asked questions ### How much does it cost to produce a SaaS blog post? Fully loaded costs run roughly $900 to $2,200 per piece depending on model. That includes writer fee, editing time, subject matter expert time, design and publishing. The writer fee alone is misleading: a $600 freelance article that needs four hours of editor time and an hour of engineering review costs closer to $1,100 in reality. ### Should a SaaS company hire writers in-house or use freelancers? Use a freelance bench for volume and range, and hire in-house when product depth is the constraint. A freelancer writing about your API for the first time produces something accurate and generic. An in-house writer who sits near the product team six months in produces things a competitor cannot copy. Most teams under $10M ARR should run a bench plus one in-house editor. ### How many blog posts should a SaaS company publish per month? Eight to twelve is a productive range for most B2B SaaS teams with a dedicated editor. Below four you cannot build topical coverage in a reasonable timeframe. Above fifteen, quality usually slips unless editing capacity scales with it, and updating existing pages starts outperforming new ones. ### What is the right freelance rate for SaaS content? Between $0.40 and $1.20 per word for B2B SaaS work, with subject matter specialists at the top of the band. Paying $0.35 a word and spending six editor hours per piece is more expensive than paying $1.00 and spending ninety minutes. Rate is not the cost, total time to publishable is the cost. ### What quality gates should a content process have? Two. Brief approval, where someone confirms the angle, the audience and the primary keyword before writing begins, and fact check, where every number, quote and product claim is verified against a source before publish. Style and tone edits happen throughout but do not need to be gates. ### When does publishing more content stop working? When your existing library is decaying faster than new pieces earn traffic, typically somewhere past fifty to eighty published pages. At that point a weekly update cycle on your top twenty pages usually returns more than three extra new posts a month, because refreshed pages already have links and history.