Skip to content

How it works

One department. One working assistant.

One department. One body of documents. A working assistant in 6 to 8 weeks. Fixed price. You own it.

Builds start at $45,000 or €40,000.

Start with a ten-day pilot.

We agree the scope, price and what a successful handover looks like before work starts. The build begins once the agreed documents and IT access are in place.

What the build includes

We also agree which knowledge needs to be written down from your experienced people. Your team checks it before it becomes a source for the assistant.

  • Your existing documents

    Procedures, spreadsheets, scanned PDFs, photos and diagrams with handwritten notes. Pages that cannot be read reliably are flagged for review.

  • Answers that show their source

    Your operators can check the document, page or sheet behind an answer.

  • A specialist when the documents run out

    When the documents do not support an answer, the assistant says so and passes the question to a named expert or a specialist queue on your team. Both steps are tested before handover.

  • IT, security and data architecture

    We agree where the documents go, who can access them, how they are indexed and how updates flow in the first week, so the build does not change direction midway.

  • Testing with your operators

    The people doing the work try it on real questions before handover.

  • A handover your people can use

    You receive the project code, setup notes and instructions for updating documents and keeping it running.

What you own

Your knowledge stays yours.

Every assistant has three layers. We build the first two as assets your plant owns.

  • Your knowledge. Procedures, manuals, spreadsheets and the rules your experienced people carry, written down and approved by your team.
  • Your workflows. The questions that matter, who approves the answers, and the acceptance tests that show the assistant is working.
  • The AI model. Chosen to fit your IT and security requirements. Your approved sources, expert rules and tests are handed over with the project.

Software licences, hosting and ongoing support are agreed separately before work starts.

Why not do it yourself

You may already have ChatGPT, Copilot or Gemini.

General AI tools are good at drafting, summarising and answering from a few documents. For one person and one procedure, that may be enough.

A plant assistant has a narrower job. It answers from your approved equipment documents, shows the page behind every answer, and says so when the documents do not cover a question. We handle the work behind that: IT approval, access to the right files, scanned pages and handwritten notes, and acceptance tests on your operators' real questions, so nobody has to wonder whether it invented a torque spec.

If your plant already uses Microsoft Teams, Copilot or Gemini, we can make the assistant available there, agreed with your IT team, so operators ask in the tools they already use.

This is the AI team you can't hire, for the one project you need.

Before we start

A clearly scoped build.

How do we know a build pays back?

We agree the measures before the build: time to answer, escalations, resolution time or adoption. On the first call we put a cost on today's version of each, using your figures, so you can compare it with the fixed price. After handover, the same measures show what changed.

What does the fixed price cover?

We agree the department, source documents, intended users, delivery milestones and acceptance tests before work begins. Additional departments or integrations need a separate scope. Builds are invoiced in your currency at the listed price.

How do we handle access and sensitive information?

We review document access, hosting and security requirements with your team before selecting the implementation. Do not send confidential manuals through a public inquiry form.

What happens at handover?

The proposal specifies ownership, documentation, operating responsibilities and any ongoing support. The assistant helps people find approved information. It does not replace your plant's safety procedures or required checks. Your team should know who maintains the sources and who approves changes.

What comes after the first build?

Once operators trust the answers, the assistant can draft work orders, nonconformance reports and shift handover summaries. A named person on your team approves each one before it reaches your systems. This is scoped and priced separately once the first build is in use.

Can we see it work first?

Arrange a guided operator-assistant demonstration to see source citations and how the assistant handles questions its manual cannot answer.

What does your plant need to know when your best person is out?

Start with one department and the questions that keep coming up. We'll talk through the documents you have and whether a fixed-price build is a good fit.

Book a 30-minute call