Engineering services

Training and handover

Train the people who will run the system. They practise making a change, handling a failure and explaining the process to a new colleague.

Potential deliverables

Deliverables and acceptance criteria are agreed in the project scope.

The usual shape

Length
The last 2 weeks of a build, or 2–4 weeks alone
Runs on
With the operators, in Singapore or on a working call
From you
The future owners, present, not only the sponsor

Name the owners first

A sponsor is not an operator. We ask who will notice on Thursday that the drafts got worse, who is allowed to change an instruction, and who tells the queue what to do when the system is pulled.

Teach the operation

We teach the gestures the job actually needs. How to read a failure. How to add an example. How to tighten a permission. How to explain the boundary to a new hire in ten minutes.

Pair on one real change

Before we call it handed over, your team ships a change while we watch. An instruction, an example, a small copy fix, a permission. The point is muscle memory and access that actually works.

Leave materials the next hire can read

The runbook, the job description, the boundary note, and the evaluation set are the materials. They are written in your language, English or Chinese, matching the team that will use them.

Related engineering services

Model integration

Integrate an approved model API into one defined task, with an evaluation the supervisor can review and a runbook the team can keep.

Explore model integration

Agent development and integration

Assign an agent a defined task, such as checking requests or drafting replies. Connect the tools it needs and set which actions someone must approve.

Explore agent development and integration

Tell us what you need to build

Tell us which systems you use, which step takes the most time and what data you can share for testing.

Discuss a project