Find out where AI would actually pay for itself
Half a day with the people who do the work. You leave with a map of where your data lives, a ranked list of what is worth doing, and a costed first step. Nobody leaves with a slide deck.
HOW LONG
Half a day, on site
WHO ATTENDS
Four to eight of your people
YOU LEAVE WITH
Four written outputs
FEE
Fixed, agreed before we start
The point is to find out what is worth doing before you spend anything building it
Most businesses arrive at AI from one of two directions. Either there is a specific problem that has been irritating people for years, or there is a general sense that something should be happening and no idea where to start. Both are fine, and both begin the same way.
The workshop is not a sales meeting with a whiteboard. It is a working session that produces a document, and the document is yours whether or not you ever work with us again.
Some of what comes out of it will be things we tell you not to bother with. That is part of the value, and it is a great deal cheaper to hear it now.
WHAT HAPPENS ON THE DAY
Four working sessions, one room, no preparation required
Come as you are. Preparing tidy inputs would defeat the purpose, because we need to see the real state of things.
We start with the frustrations rather than the technology. What takes too long, what gets found too late, what depends entirely on one person knowing something. This is the part where the people who do the work talk and the leadership team listens.
We map every system holding something that matters, what condition it is in, what is duplicated, and what nobody can currently get at. Most businesses are surprised by this section, usually in both directions.
A typical session produces ten to twenty candidate opportunities, drawn straight from the frustrations in the first hour. We are deliberately generous at this stage. Ranking comes next, and it is much easier to discard a weak idea than to invent a strong one under pressure.
Each use case is scored on value and urgency, so the sequence becomes a business decision rather than a technical one. We agree which one goes first, and what proving it would involve.
WHAT YOU LEAVE WITH
Four written outputs, back with you inside two weeks
Every system holding something of value, what state it is in, where it duplicates something else, and where the gaps are. Useful well beyond any AI project.
Ten to twenty opportunities, each scored on value and urgency, with a plain explanation of why it sits where it does. Including the ones we would not do.
An honest read on what would need to be true before the top use cases could work, and how much of that is a real obstacle rather than a tidy-up.
A defined, fixed-price scope for proving the highest-ranked opportunity on your own data, with success criteria agreed before anything starts.
WHO SHOULD ATTEND
The people who know where the problems are
-
Someone who can make a decision
Usually the owner, CEO or CFO. The session ends in a choice, and it stalls if nobody in the room can make one.
-
The people doing the work daily
Accounts, operations, buying, whoever lives with the frustrations. This is the most important group in the room and the one most often left out.
-
Whoever knows the systems
Internal IT, an operations manager, or the person everyone asks when a report looks wrong. They do not need to be technical.
-
Not your ERP partner or your IT provider
Bring them in afterwards if it helps. Their presence tends to steer the conversation toward the systems rather than the problems.
What it costs
The Discovery Workshop is a fixed fee, confirmed in writing along with what it covers before anything is scheduled. There is no cost until you agree it, and no hourly billing at any point.
We quote it once we know the size of the business and how many systems are in scope, because a four-system business and a fourteen-system business are not the same day's work.
It is deliberately small relative to what it saves you from spending on the wrong thing.
REQUEST A WORKSHOP
Tell us a little and we will come back within a working day
We will propose a date, suggest who should be in the room, and confirm the fee. Nothing is committed until you say so.
Not sure the workshop is the right first step?
Take a free hour instead. One conversation, no preparation, no obligation, and an honest answer about whether there is anything here worth doing. If there is not, we will say so.
QUESTIONS ABOUT THE WORKSHOP
Before you request one
Nothing. Bring the people who do the work. Preparing tidy inputs would defeat the purpose, because we need to see the real state of things rather than a version assembled for visitors.
No. The workshop stands on its own and ends with four documents you own. Plenty of businesses take the output and act on part of it themselves. If you do want to go further, the next step is proving the top use case on your own data.
Most is, and the ones that assume theirs is worst are usually wrong about which parts. Data condition is a finding of the workshop, not a prerequisite for it. If the honest answer is that something needs fixing before AI is worth attempting, you will hear that clearly.
We would rather not. The value comes from people talking over each other in a room and remembering things they would not have written down. If distance makes on site impossible we will work something out.
Inside two weeks, written up properly. We will not send a photograph of a whiteboard.
Then we will say so, and the document will explain why. That has happened, and it is a considerably better outcome than a project nobody should have started.