The people doing the work today
Whoever currently runs the process by hand. They know what good output looks like better than anyone, which is exactly what makes them the right people to check the automation.
An automation nobody in the business understands is a liability, not an asset. Training is how a workflow we built stops being ours and becomes yours — something your own people can run, check, and change when the work changes.
No AI background needed, and no job titles required. We train the people who already do the work, in the language of the work they do.
Whoever currently runs the process by hand. They know what good output looks like better than anyone, which is exactly what makes them the right people to check the automation.
The person responsible for it once we step back — what to do when something looks wrong, when to pause it, and who to ask.
If you have someone technical — IT, an analyst, a developer — we go further with them, so changes and new workflows do not have to wait for us.
We are not teaching a general AI course. Every session uses the workflow we built for you and the files it actually runs on.
How to start it, what it does at each stage, where its output lands, and what the normal working week looks like once it is in place.
The important one. How to tell a good result from a bad one, how to trace any figure back to the document or cell it came from, and what the common failure looks like so it gets spotted rather than passed on.
Which steps wait for a person and why, what sits outside the workflow's boundaries, and what to do with the cases it deliberately refuses to handle on its own.
Processes move. We show your team what can be safely adjusted in house — a new document layout, an extra field, a changed rule — and what is worth calling us about instead.
Built around your team's actual week rather than a fixed course length.
People use the workflow themselves while we are there to answer questions. Watching a demonstration does not transfer the skill; doing it does.
Whichever suits your team. Most training works perfectly well remotely, and we will say so rather than bill you for travel that adds nothing.
Every exercise uses your own documents and processes, so nothing has to be translated from a worked example afterwards.
A period after the sessions where questions are expected and answered, because the useful ones only surface once the team is running it alone.
We would rather tell you training is unnecessary than sell you sessions your team does not need.
Handover training on a workflow we built is normally scoped as part of the deployment, not sold separately — it is how the work gets finished properly.
Training beyond that, or for a wider group than the people running the workflow, is quoted against what you need. As with everything else, we would rather understand the situation first than publish a package that fits nobody.
The workflows we build run on QMerse. If you have technical people who want to build their own rather than have us do it, QMerse is free to start and has its own documentation and tutorials.
Tell us about your team and the process they run, and we will put together a training plan that fits — or tell you honestly that you do not need one.