how it works

From first call to running systems.

Four steps, about three weeks and a deliverable you keep at every single one. No surprises, no scope creep.

01.

Listen - the audit call

30 min · free

You describe how your team actually works - not the org chart, the reality. We map the repetitive work and what it costs you.

you keep: your automation map - 3 workflows, costed

02.

Design - the smallest system

~1 week

We propose the smallest system that solves the problem, with trade-offs and costs on the table. You decide what gets built.

you keep: the system blueprint & a fixed quote

03.

Build - in weekly iterations

1–2 weeks

Workflows go live one by one, tested on your real data. You see progress every week - never a big reveal at the end.

you keep: systems running in your accounts, from day one

04.

Hand off - it's yours

final week

Training for your team, full documentation, and we stay reachable for questions. No vendor lock-in - leave anytime, it keeps running.

you keep: everything - accounts, docs, autonomy

what you leave with

Your automation mapeven if we never work together

Systems in your accountsnever in ours

Full documentationwritten for humans

A trained teamautonomous from day one

  works everywhereFR / ENfirst reply within 24 h

honest answers

The questions everyone asks.

Every project is different, so there's no flat package, but no "it depends" fog either. The first call is free, and the map you receive after it comes with a complete, transparent quote: every workflow costed, nothing hidden, no hourly meter running. You know the full price before anything gets built and it doesn't move once you've said yes.
About three weeks from the first call to systems in production, one of design, one to two of building, then the hand-off. Complex stacks take longer; you'll know before we start.
That's usually why people call. Step 01 exists precisely to map the mess and "clean up before automating" is sometimes the honest recommendation. You'll get it straight.
No dependency. Accounts in your name, documentation written for humans, a trained team. We stay reachable, but you don't need us to keep running.
One person who knows how the work actually gets done, about an hour of their time per week during the build, and honest answers on step 01. That's it.

  free automation callfixed quoteweekly progress demosfull documentationno vendor lock-in

next step

Thirty minutes, you leave with your automation map either way.