AI isn't a fashion. Measurable ROI is.
Two years of production AI systems shipped for European companies. One problem, one system, six weeks — that's the flagship. Larger scopes on request.
Sound familiar?
AI hype, no measurable impact
Leadership asked for an AI strategy. The deck exists. Operations are unchanged. Nobody can name the ROI.
POC graveyard
The pilot ran. The press release went out. It still isn't in production. Are we starting over again?
Internal capacity bottleneck
Senior engineers are booked across three roadmaps. There's no bandwidth to build the AI system, and when there is, the domain knowledge isn't there.
Manual treadmill
Staff spend hours a week on copy-paste work. Everyone knows. Until now, nobody knew what to do about it.
What we do
Three doors. Each with a fixed fee, a written outcome, and a one-sentence promise.
Diagnostic · 1 week
We come in, observe operations, and talk to three people. The output is a written report: where AI fits, where it doesn't, and at what risk. Fixed fee — refunded if the recommendation is "don't use AI."
Pilot → Production · 6 weeks
We embed a single workflow in your existing systems and ship it live. Invoice OCR, parts RAG, scheduler, customer assistant — whichever moves your P&L most. Daily 30-minute standup, week six it's running.
Operator Retainer · monthly
After handover: weekly call, eval and drift monitoring, model and vendor selection, quarterly board read-out. Six-month minimum; cancellable in writing any time.
How we work — six weeks, four phases
Diagnostic · week 1
We come in, observe, and talk to three people. We leave with a written report and a risk map. Sometimes the report says "a Make.com flow solves this" — and that's the recommendation.
Selection · week 2
From the report, together we pick the one workflow that moves the most P&L or carries the lowest risk. Estimated savings, written kill-criterion.
Build · weeks 3–5
We build it, wired into your systems. Daily 30-minute standup, weekly code review. By the end of week five it's running on real data with real people.
Handover · week 6
Documentation in your language. End-user training. Optional six-month retainer. Your team owns it; we stay on call in the background.
Frequently asked questions
What operators ask first on intake calls.
Talk for thirty minutes — you decide if it's interesting.
Send a six-line note about what your company does, or pick a time on the calendar. One reply within 24 hours, telling you whether we can help. Nothing else.