Turn AI pressure into one system that works.
I’m Yvo de Rooij, an independent AI consultant who builds. I help operations and technology leaders choose the one AI workflow worth doing, build its first useful version with their own team, and keep it running without me.
Replies within one working day · On-site across the Netherlands and Europe, remote elsewhere
- Heathrow
- Rabobank
- Shell
- CZ
- Valcon
- ING
- Zazi
You don’t have an AI problem. You have a decision problem.
Twenty AI ideas. No first move.
The board wants progress, the budget exists, and every meeting adds three more use cases. Nothing has been chosen, so nothing has shipped, and you are the one who has to explain why.
The pilot impressed everyone. Then it stalled.
A demo won the room six months ago. Since then: no owner, no definition of good enough, and a vendor who keeps saying next quarter. You cannot put it in front of operations as it is.
Your people already use AI. Nobody is in charge of it.
ChatGPT is open in every browser tab, with no shared patterns, no approvals, and no way to tell a good answer from a confident one. It works, until the day it doesn't.
Twelve months from now you will either have one system running in operations, or a longer list.
A consultancy programme
A deck, a bench, and a roadmap that hardens before anything ships.
A vendor pilot
Built to prove the vendor’s tool. It rarely proves your workflow.
An internal enthusiast
Fast and unstructured; the system leaves with the person who built it.
…or one person who has shipped it.
Independent. Builds with your team, inside your environment. Leaves when it runs.
How that works
Three clear ways in.
Each starts with a 30-minute call and a one-page proposal. Fixed scope, fixed fee. Pick the one that matches where you are today.
Opportunity Sprint
Choose the one workflow worth doing.
Leadership teams with real budget, real pressure from above, and a long list of AI ideas, but no confident first move.
- Duration
- Two weeks
- Format
- Fixed scope, fixed fee
First Useful Version
Ship the system, not the slide deck.
Teams with one promising workflow, or a stalled pilot, that needs turning into something operations will accept and people will trust.
- Duration
- Six to ten weeks
- Format
- Embedded with your team
Operating Rhythm
Make it stick without me.
Organisations where AI is already in daily use and needs structure: shared patterns, approval rules, and judgment that travels beyond one enthusiast.
- Duration
- Monthly, from three months
- Format
- Advisory retainer
Products with real users. Systems built for clients.
Two AI products I run myself, and a company brain built for Zazi: work that keeps the advice honest, because I know what it costs to ship and what breaks afterwards.
CaseStar
A focused practice room for aspiring consultants: realistic pressure, structured cases, and feedback that arrives while the habit is still fresh.
- 2,000+ users
- Partnerships with top consulting firms
- Live voice coaching loop
Qube
Reads a business's bills, contracts and supplier terms and hands back the lines worth checking, so you can see where you pay more than you should without purchasing expertise. Nothing changes without your approval.
- Spend-cube generation
- Category insight
- Workflow-native AI
Zazi
Zazi, the company founded by Jeanne de Kroon
A company brain for Zazi, the company founded by Jeanne de Kroon: one system that holds how the business runs and automates the operational work around it.
- Company brain
- Operational automation
Operational work that used to be done by hand now runs through one system the team can see and adjust.
What it taught me: a company brain only earns trust when it holds how the business actually runs, not how the org chart says it does.
From first call to handover. No theatre in between.
- 01
A 30-minute conversation
Bring one real situation. I will tell you honestly whether I can help, and what I would do first.
- 02
A one-page proposal
Scope, timeline, fee, and what you will have at the end. No forty-slide deck, no discovery theatre.
- 03
We do the work
Short cycles, visible progress, and decisions made with the people who will own the system.
- 04
You keep it
Documentation, patterns, and enough teaching that your team keeps moving after I leave.
Builder first, advisor second.
I work where executive ambition meets operational reality: fewer slogans, more workflows, clearer interfaces, and honest judgment about where AI belongs, and where it doesn’t. The products I run keep that judgment grounded.
More about me- 01
Start with the workflow
The model is never the strategy. I look for the repeated decisions, hand-offs, approvals and information gaps where AI removes real drag, and ignore the rest.
- 02
Make the system legible
Useful AI has visible inputs, clear stop points, and outputs a team can inspect. Black-box magic does not survive contact with operations.
- 03
Leave ownership behind
The goal is not dependency. Simple interfaces, documented patterns, and enough teaching that your team keeps moving after I have gone.
Notes from the field.
Short essays on agents, evals, prompts, and the operating habits that make AI less fragile: the thinking behind the work.
Bring the messy version. We’ll find the useful system inside it.
Replies within one working day. Or email yvoderooij@gmail.com.