What should I automate first, and what should stay human?
One day settles both. Four hours go on the jobs your team still does by hand, and the written decision brief that follows names the first process to automate and the ones that have to stay with a person. It costs €1,500, and the full amount comes off a Product Audit or a Build booked within 30 days of the session.
€1,500
Duration: 1 day
Fully credited toward a Product Audit or a Build booked within 30 days
Who is an AI Clarity Day for, and who is it not for?
Companies where something already runs and a person is holding it together by hand. The order comes in, and someone copies it into a second system. The weekly report gets assembled from four places every Monday. The inbox gets sorted by whoever has time. If you can name the job and the person doing it, there is enough here to work with.
It is not for you if the open question is the product itself. That is a Product Clarity Day: €1,500, one day. It is not an assessment of how AI-ready your company is either. Nobody needs a score. And it is not a way of selling you a Build. Plenty of the processes we look at turn out to be cheaper to fix with a rule and a form than with a model.
What do you get for €1,500?
The decision itself, in writing, and the map of your work that it was built from.
- A written decision brief: which processes to automate, which to leave alone, and in what order
- A map of the work as it runs today, drawn in the session and used as the basis for every decision in the brief
- For the process that goes first: what the system does, what stays with a person, and what it would realistically cost to build
- A recommendation on what to build it with, and the reasoning behind the choice
- The full recording of the four hours
- One named next step, with a date on it
How does an AI Clarity Day actually run?
Three parts, and you sit in only one of them. Half a day of preparation on my side, four structured hours with your team, then half a day of writing.
Before: half a day of preparation
Before we meet I go through how the work runs. Send whatever process descriptions exist, the list of tools you pay for, and a rough count of how often each job comes round; half-written notes are more useful than a tidy document. The people who do the job should be in the room, not only the person who owns it, because the detail that decides this sits with them. I turn up with a first guess at where the system belongs, and the four hours test it.
The day: four structured hours
We work in blocks rather than as an open conversation: how the work runs today, where it stalls, which steps a system could take over, which ones need a person to stay accountable, and what order to do them in. The four hours are recorded.
After: the brief in three working days
The writing takes another half day, and the decision brief is with you within three working days of the session.
What is not included?
Nothing gets automated on the day itself. The work runs exactly as it does now until someone builds the system.
- A working automation. Building it is an Automation Build, from €12,000
- Changes to your existing systems. Nothing gets connected, configured, or switched on during the day
- Ongoing availability after the day. Later questions belong in Product Partner: 2 days a month, €2,000 per month, minimum 3 months
- An audit of a live product that is underperforming. That is a Product Audit: €4,500, 2 weeks
- A score, a maturity rating, or a report on how AI-ready your company is. The day ends with one decision, not a grade
Questions
Then the day has saved you an Automation Build. Some processes are too rare, too varied, or too tied up in judgement for a system to help, and finding that out for €1,500 beats finding it out at €12,000. The brief still sets out the reasoning, and names the one change that would put the process back on the list later.
Usually what did not stick was the choice, not the tool. A tool gets used when it removes a step someone actually does every week, and when nobody has to remember to open it. The day starts from your work rather than from a list of tools, and the brief names the one process where both of those hold.
The full €1,500 comes off the price if you book a Product Audit or a Build within 30 days of the session. Not part of it, all of it. It can be used once, and it applies to a Product Audit or a Build, not to a Product Partner month.
What comes before and after an AI Clarity Day?
Before it, most people arrive with a list of jobs someone is doing by hand and no agreement on which one is worth a system. Some come out of a talk or a workshop, others out of a year of adding tools that nobody opens. Afterwards there are two ways forward: an Automation Build from €12,000 if the answer is to build the system, or your own team taking the brief and running it. Book a Product Audit or a Build within 30 days of the session and the full €1,500 comes off. That credit is applied once.
Let's Build Your Digital Future
Whether you need something built, a system automated, strategic product advice, or a perspective on staying grounded while building at speed: let's talk. I bring 11 years of thinking about what makes digital products work, for the people who use them and for the person building them.