Is the first call free?
−
Yes, and with no commitment. It's a real working session, not a sales pitch: you describe the task that eats your time, and we look together at whether it can be automated and on what conditions. You leave with a clear idea of the time you could win back — including if the conclusion is that you shouldn't automate anything yet. No priced proposal is sent before the scope is clear.
No. Whatever your trade, AI takes on the repetitive tasks; you keep the know-how, the client relationship and the final decision. That's a design principle, not a slogan: concretely, no document, message or payment is triggered without your approval. The tool prepares and proposes, you review and you decide. What disappears is the data entry — not the judgement.
I'm not technical — is that a problem?
+
It's the most common situation, and it isn't an obstacle. There's nothing for you to install or configure: your job is to describe what takes up your time, in your own words and with real examples. Turning that into a tool is our job. The rule we hold ourselves to is simple: if a tool needs training to be used day to day, it's badly designed.
How long does a first tool take?
+
It depends entirely on the scope and on how accessible your data is — which is exactly what scoping is for, before you commit to anything. The logic is to ship a useful first version quickly on a narrow scope, rather than making you wait months for a complete tool. You test it in real conditions, we adjust, and the tool only grows if the value is proven.
Builds start from a few hundred euros, because we deliberately start small: one pain point, a precise scope, a low starting price so you can test without risk. There's no imposed package and no five-figure project decided up front. Every later evolution comes with a clear quote before starting — you know what you're paying for before it's built.
What if my needs change?
+
That's expected: the tool is built to evolve, and billing is progressive. An evolution is requested, quoted and decided case by case. You're not buying a frozen setup you'll have to replace in two years, and you're not committed to a volume of changes to use up.
Do I have to replace the tools I already use?
+
The goal is the opposite: connect to what you use rather than add one more piece of software to learn. Most common tools — invoicing, calendar, email, document storage, point of sale — can be connected. When that isn't possible because a tool is closed, we tell you during scoping, before any proposal.
It's a strong priority, especially for client data, financial data or anything covered by professional secrecy. How data is processed and hosted is addressed from the scoping call onwards, because it drives the technical choices — it isn't added once the tool is built. For regulated professions, those constraints are part of the scope discussed before any development.
What happens if the tool doesn't suit me?
+
That's precisely why the scope starts narrow: a first tool is tested in real conditions, on your business, at a deliberately low starting cost. If the result doesn't live up to its promise, we adjust; and if the usage doesn't hold up, you haven't committed a full redesign budget. Nothing obliges you to continue with further evolutions.
Tradespeople, freelancers, professional firms, agencies, retailers and video professionals — and more broadly any business where repetitive tasks eat time that should go elsewhere. The principle is the same everywhere; it's the tools that adapt to the trade. Each trade page details what is most commonly automated in that context.
Do you work with large accounts?
+
Yes: an in-depth initial audit, a pilot on a narrow scope, then a wider rollout if real usage is validated. Automations connect to the tools already in place — ERP, CRM, business systems — with a single point of contact throughout the project. The Enterprise page details this approach.
Who actually builds the tools?
+
A team of AI experts and developers. The AI expert frames the need and picks the models suited to your case — not the flashiest ones; the developer builds the tool, connects it to what you already use and maintains it over time. Initial scoping is done with one or both, depending on the nature of the need.