From your need to your automation, step by step
No long-term commitment. At each step, the tool assists you — you're the one who validates.
You book a slot (free)
The slot is booked online, with no prior exchange and no commitment. The point of this first conversation isn't to sell you a project: it's to understand your business and qualify what's worth automating. Sometimes the conclusion is that you shouldn't automate anything yet — and that's a useful answer too.
What we need from you: Come with one or two concrete, recent examples: the last quote you typed out, the last reminder you forgot to send. A real case beats a general description.
We scope the need together
Scoping turns a pain point into a technical scope. We look at where the information comes from, where it has to go, which tools you already use and whether they can be connected. It's also when confidentiality and data hosting questions are raised, because they shape the design rather than being bolted on later.
What we need from you: The thing that makes or breaks a project is almost always data access: can your invoicing software, till system or calendar be connected? If you don't know, we check together.
A clear proposal
The proposal states what will be built, what won't, and at what price. The scope is deliberately narrow: one useful brick, shippable quickly, rather than a full project decided before there's any proof of use. That's what makes it possible to start from a few hundred euros instead of a redesign budget.
What we need from you: Nothing starts without your explicit agreement on that document. Take the time to read it: what isn't in it won't be built at that price.
Build and delivery
The tool is built and then put in your hands on your real business — not on a demo dataset. It's the only way to see what doesn't fit: a forgotten edge case, wording that doesn't sound like you, a step that's still faster by hand. Adjustments are part of delivery.
What we need from you: Actually use it, over several days, including the busy ones. The most useful feedback comes from real use, not from a review.
It grows with you
Once the first brick is in service and its value confirmed, others can be added: a second document, an extra flow, one more tool connected. Each evolution comes with a clear quote before starting, and is decided independently of the previous ones.
What we need from you: Nothing obliges you to continue. If one tool is enough, it's enough — what follows happens because you need it, not because a contract says so.