Buy, build or consultant: what process docs really cost

The real cost of process documentation isn’t the build — it’s what comes after: maintenance, how fast it goes stale, and the dependency on whoever has to redo it. Across the three routes (consultant, in-house build, engine) those after-costs differ far more than the upfront price.

When someone asks what process documentation costs, they usually mean the first effort: creating it. That’s the smaller part. The price that stays sits in what happens after you create it — who maintains it, how fast it goes stale, and who you depend on to do it again. Three routes lead to finished docs, and they spread those costs in completely different ways.

The three routes, honestly compared

Consultant project: You buy the result and the pace. What you get is a clean snapshot — and a document that starts going stale the day it’s signed off. The dependency is high: for the next version you need the same people again. High one-off effort, little maintenance on your side, fast staleness.
In-house build: You keep control but pay with internal time. Your best process people become doc maintainers, and the moment day-to-day work bites, the docs are the first thing to crumble. Low external cost, high ongoing maintenance, high dependency on individual heads.
Engine: Forge pulls the real as-is state from your existing sources and builds the artifact from it. It isn’t created once — it regrows: when the process changes, the engine builds the next version from the same living context.

What actually drives the cost of process docs?

It’s not the hourly rate that decides, but how these four behave over time:

Time to finished docs: Consulting and in-house build measure in quarters. With an engine the artifact appears in days, not quarters.
Maintenance effort: Consultants don’t maintain at all, in-house maintains badly under load, the engine rebuilds instead of patching.
Staleness: Every static doc freezes a moment. Living context freezes nothing.
Dependency: With consultant and in-house, the next version hangs on people. With the engine, on a run.

You never pay only for the docs created today — you pay for every one that still has to come after.

Forge is an engine, not a tool

The difference isn’t “cheaper than a consultant” or “faster than building it yourself.” It’s a different shape of cost: instead of paying a lot once for a document that goes stale, you keep the ability to regrow the next version on demand. The next audit, the next review, the next process change stops being a new project and becomes just another run of the same engine. The fastest way to see what that looks like on your sources is a demo.