What Does a Documentation Topic Actually Cost to Produce?

Most documentation teams can answer how many topics they produce. Very few can answer what each topic costs.

Not the team salary. Not the tool license. The actual cost of producing one usable documentation topic — from first draft to published output.

Documentation Is a Production System

Factories measure cost per unit. Software teams measure cost per feature. But documentation teams rarely measure cost per topic.

Yet documentation follows the same economics as any production system. Each unit moves through a workflow with identifiable inputs: writing effort, engineering input, review cycles, waiting time, and overhead. Each of those inputs has a cost. And when you add them up per topic, the number is usually higher than anyone expected.

The Cost Drivers That Nobody Tracks

Most managers assume that writing time is the dominant cost. In the teams I have worked with, it rarely is. The real drivers are often invisible because nobody measures them.

Waiting time. Writers wait for engineers to answer questions. They wait for reviewers to respond. They wait for product decisions. This idle time acts like downtime in a factory — the production line stops, but the costs continue. In many organizations, waiting accounts for more than a third of the total time a topic spends in production.

Engineering support. Every topic that requires a subject matter expert consumes engineering capacity. An engineer spending one hour per topic explaining a feature or reviewing a draft may seem reasonable. Multiply that by 30 topics per release and 4 releases per year, and you have consumed 120 engineering hours annually — nearly a full month of engineering time — on documentation support alone.

Rework and review cycles. Documentation that moves through multiple review rounds multiplies the effort. The first draft takes 2.5 hours. The review takes another hour. Revisions take another hour. A second review adds more. By the time a topic is published, the actual effort invested can be double the initial writing time.

A Simple Model

Here is how to estimate cost per topic for your organization. You need five numbers:

• Writing time per topic — the average hours a writer spends producing a topic
• SME time per topic — the average hours of engineering input required
• Waiting time per topic — the average hours of idle time per topic (discounted by 50%, since writers can work on other things while waiting)
• Blended hourly rate — the average cost per hour across the roles involved
• Topics per release and releases per year — to scale up to annual cost

The formula:

Cost per topic = (writing time + SME time + waiting time x 0.5) x hourly rate

With typical numbers (2.5 hours writing, 1 hour SME, 2 hours waiting, $100/hour blended rate), a single topic costs around $450. Multiply by 30 topics and 4 releases, and the annual documentation cost reaches $54,000 — before you count tools, hosting, or localization.

That is just the direct production cost. The engineering time consumed — 120 hours per year in this example — has its own opportunity cost that rarely appears in documentation budgets.

Where the Savings Are

Once you model documentation as a production system, improvement levers become obvious:

Reduce waiting time. This is often the highest-leverage change. Async review workflows, dedicated SME office hours, and better scheduling can cut wait time by 50% or more. In the model above, that saves roughly $6,000 per year.

Reduce SME time. Better preparation before SME sessions, self-service information for writers, and structured interview templates can reduce engineering input by 30%. That saves about $3,600 per year and frees engineering capacity.

Reduce writing time. Templates, content reuse, structured authoring, and style guide automation can reduce writing time by 20% or more. That saves $6,000 per year.

Combined, these three levers can reduce annual documentation cost by roughly 29% — and these are conservative estimates.

Why This Matters Now

Three trends make documentation economics increasingly important:

1. AI is raising expectations. Organizations investing in AI-powered support, chatbots, and knowledge systems are discovering that the quality and structure of their documentation directly affects AI performance. Poor documentation does not just frustrate readers — it breaks AI implementations.

2. Engineering time is expensive. Every hour an engineer spends supporting documentation is an hour not spent building product. As engineering costs rise, the hidden cost of documentation support becomes harder to ignore.

3. Content volume is growing. Products are becoming more complex. Release cycles are shortening. The number of topics that need to be produced or updated per year is increasing. Small inefficiencies in the per-topic cost multiply across larger volumes.

Start Measuring

The first step is to calculate your own numbers. I built a Documentation Cost Calculator that lets you plug in your organization's numbers and see the results — cost per topic, cost per release, annual cost, engineering time consumed, and potential savings.

It takes about two minutes. The results tend to start interesting conversations.

If the numbers surprise you, that usually means there is a significant improvement opportunity. A short diagnostic conversation can help determine where the biggest leverage points are in your specific workflow.

---

I help documentation teams understand and improve the economics of their content production. If you want to discuss what the numbers look like for your organization, book a short call or email me.