Skip to content

Your engineers build machines. Not operating manuals.

I set up and maintain an AI-assisted documentation system for you, with the eye of a technical writer. For automation specialists and special-purpose machine builders without their own documentation team.

Become a pilot partner

Sound familiar?

The manual comes last.

The machine is finished and the team has already moved on to the next order. Then someone writes the operating manual on the side, often the design engineer or the project lead.

It is built from the last one.

Every machine is different, but the manual is copied from the previous one and adapted. In the end, nobody knows exactly what still applies to this machine.

The requirements are changing.

From 20 January 2027, the new EU Machinery Regulation applies, including to operating manuals. A good reason to take a fresh look at your own process.

Your people provide the knowledge. The system does the writing.

A fixed process instead of a blank page

The system interviews your engineers in a targeted way, writes a draft from their answers and your documents, and flags what is still open. Your people answer questions and review. Where information is missing, the system does not guess. It asks.

A technical writer stays on board

I set up the system according to your rules and the requirements for operating manuals, and keep it up to date. A technical writer regularly checks that the quality is right. Approval stays with you.

Someone who knows your world

For nine years I looked after documentation for industrial robots at KUKA: robot mechanics, software, accessories and applications. I know how design engineers and software developers think, and what users at the machine need.

I am looking for two or three pilot partners.

I want to test this approach together with companies from the field before offering it more widely. You would be a good fit if …

  • you build machines, systems or robot cells and supply the operating manual yourself,
  • you do not have your own technical documentation team,
  • your documentation is currently written on the side and nobody is happy with that.

What you bring

A real manual that is causing trouble right now, the documents that go with it, and some of your engineers' time for questions and review.

What you get

A solution built for your process rather than off the shelf, direct influence on what it looks like, and a technical writer who is involved from day one.

Lena Soost

About me

I am Lena Soost, a technical writer and technical translator. For nine years I wrote operating manuals for industrial robots at KUKA. Today I combine this experience with AI so that smaller companies get good documentation without building their own documentation team.

Tell me where your documentation gets stuck.

In a first conversation, we listen to your situation and look together at whether a pilot makes sense for both sides. No obligation and no sales pitch.

Arrange an initial call