Your team takes over. We leave.

The engagement is designed to end

A staffing business that never reaches a system is the failure mode.

Train is contracted on every build. Correspondence leaves a correspondence office that can run the register. Operations agents leave the team that owns the process owning the agent.

We leave the engagement. We do not pretend the account vanished. The next workflow is a new decision, not a standing army.

Three tracks, one page

Not three landers. Not an open catalogue of courses.

Executive

The board and the signers understand the system they own. What it does. What it must not do. Where the trail lives. Who is accountable on Monday.

Technical

Your engineers and operators run it. The instance, the logs, the runbooks, the models, the write-back to the system of record. Their environment, not a lab.

Train-the-trainer

Your team teaches the next cohort. The next clerk, the next shift, the next quarter. They should not need us for that.

On the system that was built

Train is not sold as a standalone academy. It is the last rung of a build — or a named enablement package on a system the institution already owns, if that system is the one we built.

Curriculum follows the instance: this register, this workflow, this trail. Not a slide deck about “AI for leaders.”

Operate is not Train

Until your team is certified, we can run the system for a time-boxed window. That window lives on How we work. It is not a managed-services SKU. It exists so Train can happen. A forever retainer dressed as a handover is the thing this page exists to prevent.

What a contracts officer can start with

• Train named as the exit on the build SOW — executive, technical, train-the-trainer as tracks, not options.
• Acceptance: named operators can run the instance without us in the room.
• Runbooks, weights, prompts, logs handed over. The instance is theirs.

If there is no system yet, start with a board briefing, not with a course.