Two ways to start, with one accountable team.
Start with Workflow Discovery or the 90-Day AI Foundation. Each engagement has a fixed fee, a named deliverable, and decision points where you can stop. Here is what happens after kickoff.
Most clients start with one of two scopes.
Workflow Discovery
The 90-Day AI Foundation
Frame one waiting workflow before you choose an engagement.
A working session identifies the accountable owner, source systems, human decision, and evidence needed to recommend a starting scope. The recommendation can be Workflow Discovery, the 90-Day Foundation, or a decision to wait.
What happens across the 90-day Foundation.
- DISCOVER
WEEKS 1-2 · LEARN THE WORK
We shadow the people who do the job today, map the workflows, inventory knowledge sources, and document key-person risks. Technology choices come after this work.
PLANNED DELIVERABLEWORKFLOW MAP + OPPORTUNITY RANKING- GO/NO-GO · END OF WEEK 2
- Choose whether to fund a proof around the highest-ranked workflow, refine the scope, or stop with the map.
- WHAT YOU RETAIN
- The workflow map, source inventory, and opportunity ranking produced to date.
- VALIDATE
WEEKS 3-4 · PROVE THE VALUE
We build a working proof with your data and questions, then measure retrieval quality against an agreed baseline. If the result does not clear the bar at the week 4 go/no-go gate, we stop and you keep the map.
PLANNED DELIVERABLEPROOF OF VALUE + GO/NO-GO- GO/NO-GO · END OF WEEK 4
- Continue only if the working proof clears the agreed retrieval-quality baseline.
- WHAT YOU RETAIN
- The working proof, evaluation questions, baseline definition, and results produced to date.
- BUILD
WEEKS 5-10 · BUILD THE FOUNDATION
We build the knowledge system first, followed by controlled workflow execution and then the AI employee. The first deployment runs in one channel with human approval for consequential actions.
PLANNED DELIVERABLEPRODUCTION FOUNDATION + FIRST AI EMPLOYEE- GO/NO-GO · END OF WEEK 10
- Approve the first supervised production workflow only when ownership, controls, and human approval boundaries are agreed.
- WHAT YOU RETAIN
- Knowledge-system and workflow-control artifacts, deployment configuration, and documentation produced to date.
- HAND OVER
WEEKS 11-12 · HAND OVER THE KEYS
Your team learns to direct, correct, and audit the system. We deliver playbooks and dashboards, then your IT team takes over or uses managed operations until it is ready.
PLANNED DELIVERABLETRAINING + PLAYBOOKS + OPS DECISION- OPERATING DECISION
- Choose client-operated ownership or managed operations after the training and handover review.
- WHAT YOU RETAIN
- Training playbooks, dashboards, code, pipelines, skills, and operating documentation in your repositories.
WHAT YOU GET
A single accountable team led by the founder. Weekly written status you can forward to your board. Every artifact (code, pipelines, skills, docs) in your repositories from day one, not handed over at the end.
WHAT WE ASK
We ask for a workflow owner for about two hours a week, a decision-maker at the three milestone gates, and scoped, revocable read access to the systems the workflow touches.
Fixed fees and three decision points.
We take a maximum of two Foundation engagements at a time. Currently: TAKING TWO NEW ENGAGEMENTS FOR Q4 2026.
BOOK A WORKING SESSION