01 · Engagement
30-Day Engagement.
Your team owns it in thirty days
Thirty days, alongside your team, in your environment. Your people build the first piece. By day thirty, they own it — and they can ship the next one without us.
When it fits
You have a team and a clear workflow to put AI in front of.
What you walk away with
- —A working piece, running in your environment.
- —A written direction document — your rules, on paper.
- —A build group that can ship the next thing without us.
30-Day Engagement · timeline
Two parallel tracks, three phases, thirty days.
The build group
One to three people on your side who will own the AI side of the work after we leave. They get the deepest sessions in week one, run the work live in weeks two and three, then teach the rest of the team in week four.
- —Ops lead or the person closest to the workflow.
- —A second person so the engagement does not pause if one is out.
- —Optional third for cross-team coverage.
What is not in scope
Whole-team training from day one. Dev work in your environment without your build group present. Ongoing post-engagement support (that is a Retainer conversation, not a 30-Day extension).
Common questions