The team roles, approved tools, installed workflow, access policy, and real operating examples.
02
Prepares
A role-specific curriculum, playbook, job aids, exercises, and handover record.
03
Does
Live instruction and supervised work on the company workflow.
04
Escalates
Unsafe access, unclear authority, missing owners, and requests beyond the approved environment.
Accepted finish
Each role can use the approved tools and workflow safely, with job aids, recorded instruction, and a named path for questions and exceptions.
Starting unit
One accepted workflow
Existing stack
Keep the tools that work
Human control
Consequential work waits
After launch
Operate or hand over
What this build changes.
Generic prompt workshops create enthusiasm without operating rules. The team still needs to know which sources to use, what may be changed, what requires approval, and how to recover when the system is wrong.
The system follows the operating job.
01Role-specific tool training
02Safe operating rules
03Approval and authority playbooks
04Installed-system owner training
05Workflow job aids
06Recorded team sessions
07Admin handover
Concrete paths, not a bag of features.
Each example begins with a trigger, crosses named records, assigns approval, and ends in a state people can verify.
Common workflow
Installed system owner handover
Trigger
The Production Install approaches acceptance.
Crosses
Admin surface, documentation, incident path, source updates, and review queues.
System role
Turns the operating rules into a role-specific handover and practice session.
Human gate
The accountable owner confirms access, recovery, and decision responsibilities.
Finished when
The owner can run, inspect, and escalate the workflow using the agreed materials.
Common workflow
Codex or Claude Code on a real workflow
Trigger
A team member needs to extend an approved internal tool or process.
Crosses
Repository, instructions, tests, review, and deployment policy.
System role
Teaches the user to inspect context, make a bounded change, verify it, and prepare it for review.
Human gate
Repository and deployment permissions stay with the company.
Finished when
The change passes the agreed checks or returns with a clear blocker.
Direct delivery
Packaged workflow operation
Trigger
A team installs a documented workflow on its own machine.
Crosses
Package, scripts, environment, provider API, and rendered output.
System role
Provides the installation contract, failure messages, resumable steps, and artifact checks.
Human gate
The client controls credentials and accepts the final output.
Finished when
The package runs in the target environment or reports the exact missing dependency.
Useful because the limits are explicit.
Reads
The team roles, approved tools, installed workflow, access policy, and real operating examples.
Prepares
A role-specific curriculum, playbook, job aids, exercises, and handover record.
Does
Live instruction and supervised work on the company workflow.
Escalates
Unsafe access, unclear authority, missing owners, and requests beyond the approved environment.
Connected to the stack. Governed at the action.
Training materials, recordings, access, and post-session support are defined in the written scope. Training can sit inside an install or be scoped around an existing approved workflow.
Common surfaces
Codex
Claude Code
Approved AI tools
Company repositories
Installed Outproduce systems
Recorded sessions and job aids
Control rules
No generic prompt workshop sold as adoption
Training on approved accounts and data only
Role-specific permissions
Human review of consequential changes
Recorded ownership and support path
Commercial path
Fit first. Definition before production.
The free Fit Review decides whether the workflow is ready to map. It does not promise a design, price, or launch date.
01
Fit Review
We review the workflow, owner, records, tools, and obvious blockers.
02
Operating Map
A paid engagement defines the boundary, acceptance test, exclusions, authority, timeline, and fixed Production Install price.
03
Production Install
We build against real records, verify each connection, test exceptions, and launch the accepted workflow.
04
Operate or hand over
Managed operation or documented handover follows the responsibility written into the agreement.
Relevant proof
Direct client delivery, identity withheld, acceptance pending
Installable Animation Workflows
The delivery shows how technical workflows can be packaged for another team to install, inspect, and run with explicit environment and verification rules.
No. Training is tied to approved tools, real company workflows, installed systems, and the authority rules people need to follow.
Do you train non-technical operators?+
Yes when the workflow and tools are appropriate. The curriculum is based on the role, the job, and the approved operating boundary, not on a generic engineering syllabus.
Can training be part of an installation?+
Yes. Owner and team handover are normal parts of a Production Install. A broader adoption program is separately scoped when more roles or workflows are involved.
Start here
Show us the workflow.
Tell us what starts it, who owns the result, which tools carry it, and where it stalls. We will tell you whether it is ready to map.