We investigate.
We check the records, map the steps, ask experts to explain decisions and draft the instructions and tests.
Managed process discovery
Ready to build.
We map the work. Your team decides what to build.
We review cases with your team and prepare the map, rules and draft tests. Your process owner approves the decisions. Your developers take them into the build.
Explain what changed
the decision.
Capture the expertise
Find the judgment
behind each step.
Review routine cases and exceptions. Ask what your team checked and why. Resolve conflicting records and rules before choosing what to automate.
Project responsibilities
Agree who does what.
Your team decides.
Show us the work. Correct our interpretation, resolve conflicting rules and approve what the agent should do.
Build, test and pilot.
Build and test the agreed steps. Before a pilot, confirm who approves actions, what results to measure and who maintains the system. Assign someone to review results after launch.
Project deliverables
Give your team a clear brief.
Workflow map
See the steps, people, systems and exceptions. Follow links to the records and flag what is missing.
Expert reasoning
See what the expert checked, why they acted and what would change the decision.
Decision rules
Define when the agent may act, who must approve and when to ask for help.
Development brief
Give developers the data, actions and handoff instructions. Name the decisions still to resolve.
AI tests (evals)
Specify the input, required action and result to check. Have your team review each test before use.
The brief recommends whether to build, narrow the scope or stop. It shows the evidence and decisions still to resolve.
One workflow at a time
Agree the scope
before starting.
Define the question and access.
Choose the workflow, its owner and the people who do the work. Agree the question, records, deliverables, accuracy, schedule and price.
Assign each unanswered question.
Name an owner for each open question. Resolve any rule that changes the next action before developers implement it.
Use the findings in development.
Connect your assistant through MCP or read the data from the command line. Use the supplied Claude and Codex skills to draft tests. Agree access and file formats before starting.
Scope production work separately.
Agree production connections and the automation build separately. Commission one investigation or arrange further reviews as the work changes. Keep named people responsible for operating the workflow.
Start with one workflow
Plan a discovery project.
Bring one workflow and the question your team needs to answer. Agree which records to check, what you will receive and who does the work.
Agree the scope, responsibilities and price before starting.