Content Capacity and Scheduling: How Much One Person Can Produce in a Year, and How to Keep the Calendar From Stalling

Bottom line first: For one person doing B2B content, annual output typically lands between 32 and 56 articles — not three a week. A 1,500-word long-form article takes about 12 to 20 hours end to end, with material gathering and technical confirmation accounting for a third.First work backward from hours to capacity, then lay out a 12-week calendar, and discount the plan to 70%–80% of its face value — that’s the only way the schedule survives past week one.

1. Calculate Hours per Article First, Then Work Backward to Annual Capacity

The most common failure path for a solo content creator: commit to “three posts a week,” hit week three unable to write, and by week five the schedule is dead. The right order is the reverse — start by calculating how many hours one article takes.

Take a 1,500-word B2B long-form article with 8 tables:

Stage	Time range	Description	Can it be cut
Topic and keyword confirmation	1 to 1.5 hours	Check for duplicates, pick the primary keyword and supporting long-tail terms, confirm the landing page	Compressible with a topic pool
Material gathering	2 to 4 hours	Product specs, operating records, customer Q&A, competitor materials	Compressible with a material library
Technical information confirmation	0.5 to 1.5 hours	Check specs, terminology, and capability limits with an engineer	Compressible with structured questions
Drafting	6 to 10 hours	Write in two or three sessions, including structure and judgment calls	Hard to compress
Graphics and publishing	1.5 to 2.5 hours	Tables, images, internal links, TDK, pre-launch self-check	Compressible with templates
Proofreading and review	0.5 to 1 hour	Fact-checking, terminology consistency	Cannot be skipped
Total	11.5 to 20.5 hours	Median about 15 hours	The four compressible items total 3 to 6 hours

The hours cluster in two places: material gathering plus technical confirmation at 2.5 to 5.5 hours, and drafting at 6 to 10 hours — together more than 70% of the total. So the key to speed isn’t typing faster — it’s front-loading material gathering and technical confirmation.

Now calculate annual capacity. A working year isn’t 52 weeks: subtract about 2 weeks for annual and public holidays, 4 weeks for trade shows and peak season, and 2 weeks for ad-hoc projects, leaving 44 weeks.

Commitment model	Weekly content hours	Average hours per article	Theoretical article count	Discounted annual capacity	Suited to
Part-time (content is 30% of role)	14 to 16 hours	15 hours	41 to 47 articles	32 to 40 articles	Teams of 1 to 3, with content handled alongside delivery or marketing
Semi-dedicated (60% of role)	22 to 24 hours	15 hours	65 to 70 articles	48 to 56 articles	One person owns content, other roles collaborate
Dedicated (full-time)	30 to 32 hours	15 hours	88 to 94 articles	60 to 70 articles	A dedicated content role with a steady supply of materials

How the numbers work: the part-time track assumes 15 hours a week across 44 weeks, which gives 660 hours; divide by 15 hours per article to get 44 articles, then apply a 75% completion rate. The same logic applies to the half-time track. The full-time track’s bottleneck isn’t hours, it’s source material — one person can produce at most 1.5 to 2 qualified material packs a week, and that sets the ceiling.

So my recommendation: if content is handled part-time by someone in delivery or marketing, set the annual target at around 35 articles, or 0.8 articles a week on average. Three articles a week means 156 articles and roughly 2,340 hours a year — the equivalent of 1.5 full-time content roles, plus a steady supply of source material.

When it doesn’t apply:If content isn’t your main acquisition channel(orders come mainly from repeat customers, marketplace stores, or trade shows), don’t put headcount behind this model. Put the same hours into maintaining product page specs and application notes instead — the return is more direct.

2. Actual output always runs 30% below plan, and writing isn’t the reason

Schedules usually fall apart because they’re built on “pure writing time”: treating all 40 hours a week as available for content, ignoring that the writer also fields inquiries, edits pages, and works trade shows.

Loss item	Typical impact	Can it be reduced?
Waiting on source material	0.5 to 2 business days per instance	Yes: set a fixed weekly technical Q&A slot
Sales interruptions	3 to 6 hours a week	Cap it: set a fixed 2-hour weekly window for rush requests
Review rework	1 to 3 hours per article	Yes: review only facts and terminology, not writing style
Meetings and travel	8 to 16 hours a month	Mostly fixed; can only be scheduled ahead
Last-minute changes at publishing	0.5 to 1 hour per article	Yes: lock TDK and internal links at the draft stage

Add up all five, and actual output is usually 70% to 80% of plan.Scheduling at 75% isn’t conservative — it’s close to reality. Conversely, if you schedule at 100% or even 110%, you’ll start falling behind in week one, and by week three nobody will even look at the schedule.

3. The four bottlenecks and how to speed up each one

Capacity usually gets stuck in just four places, and they tend to stay in the same spots.

Bottleneck	Typical sticking point	How to speed it up	Hours saved
Material gathering	You don’t know who to ask, and the material is scattered across engineers’ computers	Build three material templates (spec tables, FAQs, operating records) and set aside 2 hours a week to fill them in	1 to 2 hours
Technical information confirmation	Waiting 1 to 2 days for answers, with several rounds back and forth	Send a structured list of 8 to 12 questions at once and agree on a 24-hour response time	0.5 to 1 hour
Review	Several people edit in turn, and terminology keeps shifting	Assign one final reviewer who checks only facts and compliance	1 to 2 hours
Graphics and publishing	Graphics get made on the fly, internal links get hunted down on the fly	Template the graphics (same layout, swap the data) and insert internal links at the draft stage	0.5 to 1 hour

Together, the four categories save 3 to 6 hours per article — equivalent to raising annual capacity by 25% to 40%.Of the four bottlenecks, source material collection is the one worth tackling first because it sets both your output ceiling and the quality of each piece. With a full asset library, a finished draft usually drops from 10 hours to around 6.

4. 12-Week Schedule Template

The point of a schedule isn’t to fill every week. It’s to give each content type a rhythm and give review checkpoints a place to sit.

Week	Content type	Deliverable	Review checkpoint
Week 1	Product pages and topic pool	2 product pages plus a keyword mapping table	Keyword mapping table confirmed
Week 2	Long-form (product comparison)	1 post	Schedule review
Week 3	Long-form (buying guide)	1 post	Technical fact check
Week 4	Short posts and product pages	3 FAQ posts plus 1 product page	Internal links complete
Week 5	Long-form (industry applications)	1 post	Do we have 4 weeks of assets in reserve?
Week 6	Customer Case Studies	Full version plus summary version	Client sign-off
Week 7	Short posts and site audit	3 FAQ posts plus a full-site internal link audit	Internal link audit report
Week 8	Long-form (troubleshooting and maintenance)	1 post	Quarterly data review
Week 9	Long-form (certification and compliance)	1 post	Fact and compliance review
Week 10	Case study and product pages	1 case study plus 1 product page	Case study data definitions
Week 11	Long-form (cost and lead times)	1 post	TDK and structured data
Week 12	Review	Quarterly review plus next quarter’s topic pool	Review both output and quality

Over 12 weeks you produce 6 long-form articles, 2 case studies, 6 FAQ posts and 4 product pages, 18 deliverables in total, averaging 1.5 per week. That volume matches the “part-time” tier in the capacity table. If the work falls to someone doing it alongside another role, just drop long-form to 1 article every 3 weeks.

Set your content types and frequency first, then slot them into the weeks. The schedule holds up far better that way.

Content type	Hours per piece	Suggested frequency	Annual output
Long-form (1,200 to 1,800 words)	12 to 20 hours	1 every 2 weeks	24 articles
Customer case study (full version plus summary)	10 to 16 hours	1 per month	12 articles
Q&A short posts (300 to 600 words)	2 to 4 hours	1 to 2 per week	50 to 80 posts
Product pages and spec pages	3 to 6 hours	1 to 2 pages per month	12 to 24 pages
Monthly maintenance and review	6 to 10 hours	Once a month	12 times
Annualized	About 700 to 900 hours	Works out to 16 to 20 hours per week	Someone doing it alongside another role, plus a little outsourcing

Case studies have the biggest effect on capacity of any content type, because they need client sign-off and usually take 1 to 2 weeks longer than a long-form article. For how to write them, see /insight/customer-case-study-six-part-structure/.

5. Three Ways to Cut the Cost per Piece

How to do it	What to do	Hours saved	Cost
Templated structure	Long-form always follows the same four sections: problem, judgment, method, boundaries. Headings are preset by content type.	1.5 to 2.5 hours	You have to write the judgment section yourself. A template won’t think for you.
Split one set of assets into several pieces	One 1.5 to 2 hour technical interview yields 2 to 3 pieces	2 to 3 hours	You need an asset library, or in six months you won’t be able to find the original notes
Fill gaps with Q&A short posts	Turn real customer questions into 300 to 600 word posts	Only 2 to 4 hours per piece	Short posts only cover long-tail queries and answer questions. They don’t carry your main keywords.

Of the three, do the second one first.Reusing assets is the only way to turn a one-time cost into a marginal cost, and it pays off the most over time. Templating pays off fast, but it plateaus after two or three months. For which steps suit AI and which must stay with people, see /insight/content-production-ai-human-boundary/.

6. Outsourcing and collaboration: boundaries and acceptance criteria

Stage	Can it be outsourced?	Preconditions	Acceptance Criteria
Material gathering	Yes	Provide a product library and glossary	Zero factual errors; every asset carries its source
Draft writing	Conditional	Glossary plus 3 sample articles plus a fact list	Zero factual errors, no promises, word count within range
Proofreading and formatting	Yes	Provide formatting guidelines	At least 8 tables, 2 to 5 internal links, TDK compliant
Technical fact verification	No	Must be confirmed by an in-house engineer	Every spec traceable to its source
Publishing and internal links	Full outsourcing not recommended	Requires site permissions and a rollback plan	Run one self-check within 24 hours of publishing

There is only one hard boundary:technical fact verification cannot be outsourced. One wrong spec and the customer stops trusting the whole site. That costs far more than the few hours you save. If an outsourced writer fails two batches in a row, replace them; don’t try to fix it with more money, because the hidden cost of repeated rework usually exceeds the cost of a replacement. The division of labor and acceptance table we use in client delivery is at /expert/cuilishu/ 看。

7. Signals that scheduling is stalling, and what to cut first when capacity runs short

Schedules usually collapse after warning signs appear; the problem is no one is watching. Set the four items below as thresholds you can actually judge against.

Signal	Threshold	Action
Repeated delays	Two weeks in a row without publishing on schedule	Stop adding topics; finish the 2 pieces in progress
Assets running out	Asset library holds less than 4 weeks	Pause publishing for a week and restock assets
Slower review	Average review exceeds 3 days per piece	Name a single final approver and fix review time slots
Per-piece overrun	Actual hours exceed estimate by 50%	Reassess topic complexity; cut topics that need lots of new assets

When two or more signals appear, don’t add people. Cut volume first. The order is below.

Order	Content type	Why cut it first	Cost
First cut	Short pieces on non-core topics (industry news, trade show recaps)	Furthest from conversion; stopping costs almost nothing	Social posting frequency drops
Second cut	Follow-ups to long articles (second and third pieces on the same topic)	Low marginal information; the main piece already covers it	Topic coverage thins out
Third cut	Secondary versions of case studies (one-page PDF, multilingual versions)	The main version stays; sales materials shrink	Fewer supporting pieces for trade show pitches
Fourth cut	Q&A short pieces	Affects long-tail and FAQ coverage	Long-tail traffic declines slowly
Do not cut	Product pages and FAQ pages	They carry conversion directly; going dark closes the door	None; must be kept

Judgment:Cut from the end furthest from conversion. Product pages and FAQ pages always come last. There’s another boundary here: if the bottleneck is source material, not hours, cutting volume won’t fix it. You need to replenish material before you talk about capacity. Cut everything you’re supposed to cut without replenishing material, and the schedule will collapse the same way next quarter.

FAQ

Is two posts a week realistic?

In most cases, no. Two long-form posts a week is roughly 100 a year, about 1,500 hours — close to a full-time role’s entire working hours, and that doesn’t include topic selection or review. A workable alternative is to change “two posts a week” to “two deliverables a week,” mixing long-form with short Q&As and product pages, and dropping long-form to one every two weeks. Only when content is handled by a dedicated role and the material library has 4+ weeks of reserves does two long-form posts a week become barely sustainable.

Where does the material come from?

Three places. First, customer questions: pull the 20 questions that keep coming up in the past 6 months of inquiries, emails, and chat logs — these make the highest-quality topics. Second, technical and after-sales records, including repair reasons, acceptance disputes, and process changes. Third, sales and trade show talking points — what salespeople say customers care about most is often more accurate than keyword tools. The boundary is that material must have a source, otherwise six months later you can neither verify it nor reuse it.

Can salespeople supply material?

Yes, but give them a template, not a task. Telling salespeople to “write something” usually produces nothing. Instead, have them fill out a form that takes 5 minutes (what the customer asked, what the working conditions were, what solution was used, what the result was) and submit it every Friday. In practice, 10 salespeople can reliably produce 3 to 5 qualified pieces of material a week. The catch is that this form has to be part of their evaluation, otherwise you’ll get submissions for two weeks and then nothing by the third.

How do you review outsourced writers?

Three hard standards plus two soft ones. Hard standards: zero factual errors (parameters traceable to source material), no promise statements (no “guaranteed,” “leading,” “100%”), and word count and structure within the agreed range. Soft standards: terminology consistent with the glossary, paragraph rhythm close to the model text. The process is to randomly pull 2 posts for fact-checking; one error sends the whole batch back. Two failed batches in a row and it’s time to replace the writer. Be careful not to reject based on vague standards like “it just doesn’t read well” — that only creates an endless rework loop.

What if sales interrupts the schedule?

Handle it in two categories. Truly urgent requests (a big client needs materials last minute, trade show collateral) should be accepted, but with time and volume limits — keep a 2-hour slot each week for rush orders. Non-urgent ones become content topics and go into next week’s schedule. The key is to make rush orders costly: every time you accept one, cut a low-priority short post that same week, so total schedule volume stays constant. If rush orders come more than twice a week, the problem isn’t the schedule — it’s the division of labor. You need someone dedicated to handling them.

How much time can AI actually save?

It saves time on the first draft and the polish pass, usually 2 to 4 hours per article, about 15% to 25% of total working time. It can’t save you from three things: deciding what to write about, verifying technical facts, and expressing an opinion. As a rule of thumb, when your source material is ready, drafting time drops from 8 hours to about 5. When it isn’t ready, AI barely helps, because the bottleneck isn’t the writing. Also set aside 0.5 to 1 hour for fact-checking: every factual error in an AI draft has to be checked one by one.

Final thoughts

On output: every plan that fails starts with “let’s set a number first.” The number is an outcome, determined by three variables: hours per article, hours you can actually put in, and your hit rate. Write those three down and the output falls out on its own. No willpower required.

One step is enough to get started: spend a week tracking the actual hours it takes you to write two long articles, use the method in section one to work out your yearly range, then set your target at 70% of it.Aim a little low in year one and you can raise it in year two. That’s far better than aiming high in year one and falling behind from year two on.

One line worth remembering: output isn’t a matter of attitude, it’s a matter of how your hours are structured. Front-loading source collection and technical verification beats writing two extra hours a day. If you want to see what our scheduling sheet and source templates look like, start here:/contact/ Talk to us.