Two days to know what is worth doing.
Before committing to a project, find out what is worth automating in your organisation — and what is not.
The problem with a first project
Committing several thousand euros to a vendor you do not know, on a scope you have not yet seen, requires a trust nothing has earned yet.
The diagnostic answers that by making it small. You are not buying a project: you are buying what you need to decide whether to start one.
What you get
A written document, delivered on an agreed date, that reads in twenty minutes. Not a fifty-page report nobody opens.
It answers three questions: which tasks actually cost you time; which ones are worth automating, ranked by effort against gain; and where to start, in what order, with what effort.
It also contains a section you will not find everywhere: **what is not worth automating** in your organisation, and why.
How it works
We observe your processes as they actually run, we meet the people who live with them, and we look at the tools already in place.
No development at this stage. The point is to understand before proposing — the reverse produces projects that automate confusion instead of resolving it.
You receive the document, we go through it together for an hour, and you decide what happens next. No obligation.
If you decide to continue
The cost of the diagnostic is **deducted in full** from the build, if you commit within three months.
In other words: if the diagnostic leads to a project, it will have cost you nothing. If it leads to « not now », you will still have clarified your processes and you will know why.
What we will not do
We will not tell you AI is the answer when it is not.
Sometimes the right diagnosis is « your process needs clarifying first », or « a well-built spreadsheet will do », or « the software you already own does this, and nobody knows ». You will hear that as plainly as the rest.
It is in our interest as much as yours: a project built on a bad diagnosis fails, and a failed project is never recommended.
Worth knowing
- The diagnostic is quoted after a first conversation: scope depends on the size of your organisation and the number of processes to observe.
- It assumes you can give us access to the people concerned for a few hours. Without that, we would be observing processes in theory only.
- We will not sell a diagnostic if the need is already clear: in that case, go straight to the build rather than pay for a step you do not need.
A task that is weighing you down?
Describe it in two lines. We will tell you frankly whether a diagnostic is warranted — or whether the answer is simpler than that.
Reply within 48 business hours · No commitment · Confidential