Written so clearly that you are not needed to explain it
One page per use case: the problem, the person, the data, the measure of success and the reason this one is first. If a colleague cannot repeat it back, it is not clear yet.
- AI Discovery Workshop
- €4,000 incl. 2 results
- Remote or on-site
- English or German
Clarity is a written artefact, not a feeling
Everyone leaves a good workshop feeling aligned. Three weeks later, four people remember four different scopes. Clarity is the rung that survives that gap, because the output is a page rather than a mood.
The page is short on purpose. If a use case needs six pages to describe, it is either several use cases or nobody has decided what it is yet.
This is also where scoring happens: value, feasibility, data readiness and whether AWS funding applies[7]. The scores matter less than the fact that they are visible, so the next steering meeting argues with the reasoning rather than re-running it.
One page per surviving candidate
Produced in the AI Discovery Workshop. The workshop is €2,000; written results are €1,000 each and the standard package includes two.
The problem in business languageIncluded
What is slow, expensive or error-prone today, described without naming a single AI service.
The measure of successIncluded
The number that would move, where it is measured today, and what counts as enough to continue.
Data and access realityIncluded
Which data exists, who owns it, and what has to happen before anyone can use it. Usually the part that decides the timeline.
The scored comparisonIncluded
All candidates side by side, with the scoring visible rather than asserted.
Ranked recommendationIncluded
One first project, and written reasons why the others wait.
Clarity is where most programmes quietly stop
It is an unglamorous rung. There is nothing to demo and nothing to screenshot for a board pack, so the pressure is always to skip ahead to something visible.
The cost of skipping shows up two rungs later, when a prototype works perfectly and the business says it answered the wrong question. Rebuilding then costs more than the whole Discovery workshop did.
Ideas
Who needs this most?
The idea said out loud, and who it is actually for. Out: a shortlist
Free 30-min callClarity
Is the idea clear?
Written so anyone in the room can repeat it back without you. Out: one page
Concept
Is it technically working?
The idea shown, not described: data, layer and approach chosen. Out: a concept
Cloud demo
Does it survive contact?
Something real to click, running in the cloud. Out: a demo you can try
2–24 hoursMVP / POC
Do users adopt it?
First public customers on a real user journey, built with your team or a partner. Out: measured use
1–3 monthsFunctional product
Ready to scale?
Market-ready, scaled and operated, with someone on call. Out: a product
3–12 months+Ideas found on the way get parked. They stay in the discussion and out of the build, so the current step keeps its scope and nothing is quietly forgotten.
The full ladder. Every rung answers one question and leaves something people can look at or try. Each stage links to its own page.Source: Linda Mohamed, AI Use Cases Workshop deck, 2026
Where the facts come from.
Prices, service names and limits change. The linked official pages are the reference; figures on this page were checked in September 2026.
- AWS Well-Architected Framework
- AWS Pricing Calculator
- AWS: Amazon Bedrock pricing
- ai-solutions.wiki: From AI proof of concept to production
- ai-solutions.wiki: Total cost of ownership for AI
- ai-solutions.wiki: Build vs buy for AI
- ai-solutions.wiki: AWS funding for proofs of concept
- Regulation (EU) 2024/1689, the EU AI Act
- Documenting architecture decisions (ADR), Michael Nygard
Start with one conversation.
30 minutes to look at your idea, your data and the right starting point. Or book 15 minutes if you only have a question.
- Whether your use case is already clear
- What the one page would need to contain
- Whether Discovery is the right start
- Whether AWS funding could apply
Vienna, Austria · remote across Europe · [email protected]
