A small European studio building AI automation systems for businesses with three to twenty-five people. Subscription-shaped engagements: a careful build, then a durable working relationship with one or two operator-champions inside the company.
Not platform installs. Not consultancy decks. Concrete systems that absorb the mechanical layer of the operation, so the operators running it can spend more time on what only they can do.
How an engagement runs
Services
Four service patterns we keep coming back to. Each one is shaped around a real operational problem we've seen multiple times. We don't sell productized packages, generic AI bootcamps, or "transformation" programs.
01
First-contact engagement. We map the operation end-to-end and identify where AI would actually help, and where it wouldn't. Output: a concrete plan with clear scope. No commitment to build with us afterward.
02
The build phase. Specific systems wired into actual workflows: an inbox that routes incoming work to the right person automatically, document drafts generated from your spec sheets, scheduling that handles the back-and-forth without the back-and-forth, internal search that finds the answer in your folders, custom workflows specific to how you actually work. Built to be owned by your team after handover.
03
One or two operators inside your team get trained to own and extend the system day-to-day. Not generic AI training, but specific to the systems we built together. The relationship runs through them.
04
The system evolves as your operation does. A monthly retainer covers small adjustments, technical maintenance, and the occasional new build. We know what your systems do and how to keep them working. The durable working relationship is the point.
How we work
Each engagement runs in four phases. The first is an audit conversation, concrete enough to decide whether we should work together at all. The last is subscription maintenance, the relationship that makes automation actually useful over years, not weeks.
01 · Audit
A 90-minute conversation with whoever runs the operation day-to-day. We map the actual workflows, not the org chart but the lived workflows. Then identify candidates: where AI would compress real work (often: inbox triage, document drafting, internal search, repetitive data entry), where it wouldn't (decisions that need judgment, anything that needs trust), and where a human needs to stay in the loop. Output: a concrete written plan.
02 · Champion
Automation needs a champion inside the company. We work with you to identify the operator(s) who will own the system after handover. Their context shapes the build; their hands run it. No champion, no engagement: that's a structural rule, not a preference.
03 · Build
Four to twelve weeks depending on scope. Each system is shipped in working state, not "ready to be deployed" but actually running, used, and improved through the build phase by the champion. Documentation as we go, not at the end.
04 · Subscription
Monthly subscription for ongoing adjustments, troubleshooting, and new automation needs as they emerge. Honest scope: most months are small adjustments, some are real new builds. Either way, the relationship is what makes automation work over years.
Why we work this way
The deliverable is not "AI installed." The deliverable is more space for the human side of work: the relationships, the judgment, the hiring, the trust-building. The part of the operation that's actually yours.
— from our practice philosophy
About the studio
Subscription-shaped engagements with small businesses, organizations, and non-profits, typically three to twenty-five people. We work across Europe in English, French, and German.
Every engagement pairs us with one or two operators inside the company who become the people actually running the systems day-to-day. The build is collaborative; the systems stay yours.
90 minutes. No fee. We map your operation, name where AI lands cleanly and where it doesn't, and decide together whether to work together. No pressure if it isn't a fit.