B5 · Documentation
With AI support, one technical writer is now enough, where five used to be needed.
The project is finished, the work is done, the value has been created – only the documentation is still outstanding. We keep the effort for this low by using AI: the AI writes the draft, an engineer then only reviews the results and refines them where necessary.
You might be familiar with this
Typical starting situations.
Capacity is lacking
Your design engineers want to design, not document, and technical writers are expensive.
Documentation lags behind the project
Manual updates are easily forgotten and cost time. We support automation so the documentation stays current and delivers its value in real time.
Expensive and inconsistent
Extensive documentation causes costs not only at creation but also during later changes and adjustments. Without continuous maintenance, drawings, instructions and other documents can drift apart over the years. At the latest when changes occur or a new version is due, it becomes clear what has been missing – and the effort to gather the necessary information again increases as the project ages.
Requirements specification is missing – or insufficient
Without a clean requirements specification, development can neither be commissioned nor compared seriously. Writing one is a craft in itself. We are happy to take this on for you.
Service
What we deliver
- —Operating, assembly & maintenance instructions
- —Technical documentation & service manuals
- —Training documents
- —Declarations of conformity & technical file according to Machinery Directive, from 20 January 2027 Machinery Regulation
- —Requirements specifications & functional specifications
- —Multiple languages / translation (on request)
- —Product testing with comprehensive test report
We produce documentation during the project itself: the AI writes the first draft from the design data, bills of materials and records that are generated anyway, and an engineer checks it for technical accuracy and completeness. This shifts the effort from writing to checking, so that reliable documentation is ready in days rather than weeks and can be updated with little effort whenever the product changes. Because the description stays so close to the machine, it still serves as an answer years later to questions no one is asking yet. Requirements specifications and functional specifications are produced using the same process.
This example calculation is based on typical market averages; the actual effort depends on the scope and starting point of your documentation.
Would you like to bring order to your documentation?
The more precisely you describe what you need, the more precisely we can tell you what it costs.