Work
A desk, then the people who run it.
Most jobs are a systems build. AI sits inside that desk when it saves a step. Training is how the desk stays yours.
Systems build
A product or portal from the first brief through a working pilot. This is the usual job.
- Problem, operator, and constraints in writing
- A scoped estimate and a change-order rule
- A working slice in the real place
- Handoff notes and a training session
AI inside the desk
Automation only where an operator already loses time. It ships as part of the system, with a person who can override it.
- A step that already exists in the workflow
- Hooks into tools the team already opens
- Guardrails written into the handoff
Training with the handoff
The people who will click it every day sit with us before we leave. Refreshers come later if you ask.
- Operator and admin sessions
- Notes for the failures that already happen on that floor
- Check-ins after launch, when you book them
The four steps
Same path as the home page, with what you get at each step. The number for a slice is in the scope letter.
01 · Discover
A short pass so the problem is shared in writing.
- What the team does today
- Who will operate the desk
- What must stay out of the first slice
02 · Scope
A written proposal for that first slice.
- Estimate and change-order rule
- What “done” looks like
- Who signs before we build
03 · Pilot
The agreed slice, running where your people already stand.
- Build against the signed note
- Checkpoints you can see
- A change order if the slice moves
04 · Handoff
Your operators take the desk.
- It runs in the real environment
- Written notes of what we built
- A training session and a short support window
After the job
Operator refreshers and advisory check-ins are extra work. They are not a fifth phase on every engagement. Write if you need one later.
