Discovery and prioritisation
Where do AI and automation actually make sense?
You know you want to do more with AI, agents, or automation. What is missing is a qualified overview of where the technology genuinely makes sense, and what you should build first.
Does this sound familiar?
There is no shortage of ideas. Someone saw a demo of agents, someone else heard about a robot that saved a colleague a day a week. Leadership asks what you are doing about AI, and the answer is a list of twenty suggestions and no priorities.
At the same time, the ideas are hard to judge. Is the process even suitable for automation? Does it need an agent, a flow, or just a better template? And what does it cost to find out?
Discovery is about finding work that can be done better, not finding somewhere to use AI. The technology is chosen to fit the problem.
Anders on the task
Anders Jensen
Microsoft MVP and UiPath MVP
The goal is not to find somewhere to use AI. The goal is to find work that can be done better. The technology is chosen to fit the problem, never the other way round.
What a discovery programme can include
The outcome is typically a prioritised list of opportunities and a concrete recommendation for what to test first.
The discovery programme itself
- A discovery or ideation workshop with the people who know the processes.
- Walking through specific workflows as they are actually performed today.
- Identifying candidate AI, agent, and automation cases.
- Assessing technical feasibility on your platform, such as Microsoft 365, Power Platform, or UiPath.
- Assessing potential impact and complexity for each opportunity.
- Prioritising the opportunities and recommending which cases to test first.
- Optionally, a prototype or pilot of the first case.
What you take home
We do not deliver a report for the drawer. We deliver a decision you can act on.
See what it includes
- A prioritised list of opportunities with an assessment of impact and complexity.
- A recommendation for the first two or three cases and the technology that fits each one.
- An assessment of what you can build yourselves and where you will need help.
How we have helped others
The examples are anonymised. We do not promise a set number of use cases or a financial return up front.
-
Ideation workshop with domain experts
A day where staff from several departments walked through their own workflows, and the ideas were sorted by whether they needed an agent, an automated flow, or neither.
-
Process review before automating
A step-by-step review of an administrative process before anything was built. Several steps turned out to be removable rather than worth automating.
-
A prioritised list as the basis for decisions
A prioritised list with impact, complexity, and recommended technology per case, which leadership used to choose the first pilot projects.
Price and format
Discovery starts with a short call where you tell us what you want to achieve. From there the usual format is a workshop day at your site, with Anders Jensen or a specialist from our network, and an online follow-up where we go through the priorities together. If the first case is to be built afterwards, we continue on an hour package or a new programme.
Recommended: With Anders Jensen
Workshop program
DKK 53,500 excl. VAT
See all prices, programs, and termsWrite to us
Briefly describe what you want to achieve, or what is causing trouble. You know the price level up front, and we reply within 24 hours.
Message sent.
We reply within 24 hours. A receipt is on its way to your inbox.
Frequently asked questions
How many use cases will you find?
We do not know in advance, and we do not promise a number. Some organisations have three strong cases, others have twenty weak ones. The value is in the prioritisation, not the count.
Do participants need to know anything about AI beforehand?
No. We need the people who know the processes best. We take care of the technology. The best results come when domain experts and technical people are in the same room.
Can you also build what you recommend?
Yes. Discovery can stand alone, but many organisations go straight on to a prototype or pilot of the first case, either with us or with their own developers and us as a sounding board.
What if we already have a list of ideas?
Then we start there. An existing list is a good basis for assessing feasibility, impact, and complexity, and it usually shortens the workshop.
Proudly working with
