Team01 / 03
Chief executive
Leads the first conversation, the product and the value case.
Leads
- The first conversation
- Product direction
- The value case with senior sponsors
Background
A product-design and front-end background, applied to making complex systems understandable and useful.
Where you meet Leo
- 01Audit
- 02Design
- 03Prove
- 04Deploy
- 05Improve
Locate where exceptions, fragmented information and repeated coordination cost time or margin.
Define what an agent can do, what it needs to know and when a person takes over.
Test one workflow on real cases before giving the system authority to act.
Connect the proven system to your operation and release it in controlled steps.
Learn from live work and improve reliability before expanding the system’s remit.
More of the team
Talk it through
Leo LargilletChief executive
Available this week
Bring a process your team knows should work better. In forty-five minutes, we will listen to how it really runs, identify where AI could help, and be clear about what we would leave with people.
Frequently asked
Our work starts from the people already responsible for the operation. The aim is to remove repetitive search, comparison and drafting, while making their judgment easier to apply and keeping accountable decisions with named human owners.
They help map the real process, choose the difficult cases, test early versions and define where review or refusal is required. An internal group learns to operate and improve the system before handover.
One senior sponsor, access to the people and systems involved, and agreement on the business measure before building begins. Leadership also protects time for operators to participate, because their knowledge is part of the system.
It should be frequent, expensive, evidence-heavy and close to a measure the company already trusts. The two-week diagnostic compares candidate workflows and tests the strongest one on real company data.
That is why it is tested on real exceptions before production. Corrections become part of the evaluation set, and the system is designed to ask for review when evidence is weak rather than appearing certain.
We build in the client environment wherever possible, use the minimum permissions each action needs, and make activity auditable. Data boundaries, retention, human review and prohibited actions are agreed before a production release.
The engagement is designed to reduce that dependency. The client receives the source, prompts, evaluation cases, runbooks and controls, and proves the handover by running the next cycle with its own team.
We establish the current cost and operating baseline together, then review the same measure after each release. If the workflow does not produce a credible financial or operating improvement, we do not expand it.