AI Discovery Workshop · Session one of three

Which of your AI ideas is worth building first

One workshop with your team. Every candidate use case collected, scored on value, feasibility, data and AWS funding. You leave with a ranked shortlist and a clear first project, not a wishlist.

  • €2,000 per workshop
  • €1,000 per written result
  • Remote or on-site
  • English or German
Where most AI programmes stall

The hardest decision is not which AI tool to buy

It is which problem to solve first. Most teams arrive with twenty plausible ideas, a sponsor who wants visible progress and no shared way to compare them. The pilot then goes to whoever argued loudest, and the result is hard to repeat.

Discovery fixes that. Your team brings the ideas and whatever data you can share. We collect the real candidates, then score each one on four questions: what it is worth, whether it can be built, whether the data is ready, and whether AWS funding applies.

The four questions follow a simple order that I also teach: people first, then business, then technology. A use case that nobody will use does not get better with a better model.

By the end of the session you have a ranked shortlist and one recommendation, agreed by the people who will live with it.
Perspective one

The user

“Who is this for, and what does the day look like afterwards?”

  • Users and personas, named, not assumed
  • The journey as it should be, end to end
  • What people do today and what breaks
  • Which part of it AI is actually allowed to touch

In the room: Product owners, business analysts, designers, service and support

Perspective two

The business

“What is it worth, what is in the way, and who signs?”

  • The value chain the use case sits in
  • Constraints that are real: legal, contractual, political
  • The business case, with the numbers written down
  • What success is measured by, before anyone builds

In the room: Finance, business owners, legal, compliance, leadership

Perspective three

The technology

“Can it be built, run and defended?”

  • Architecture, data access and the layer decision
  • How it is built, reviewed, tested and deployed
  • Security, certification evidence, audit trail
  • What it costs to run and who is on call

In the room: Engineering, platform, data, security, operations

Governance sits at every layer, not at the end. Who may see what, what has to be logged, and what an auditor will ask for are questions for all three perspectives — which is why they are asked in this order rather than after the build.

The decision compass used in Discovery: people, business, technology, and governance at every layer. Each row is one level of how much of the AI stack you run yourself.Source: Linda Mohamed, lecture “Von Managed zu Hybrid: KI-Architekturen”, Hochschule Burgenland, 2026

Written results

What you walk away with

The workshop itself is €2,000. Written results are €1,000 each, so you only pay for the documents you need. The standard Discovery package includes the first two.

1

Scored use-case shortlistIncluded

Every candidate from the session, scored on value, feasibility, data readiness and funding eligibility, with the scoring visible so it survives the next steering meeting.

2

Data and feasibility notesIncluded

For the top three: which data exists, who owns it, what blocks access, and which AWS services would do the work.

3

Funding eligibility checkOptional

Which candidates fit AWS proof-of-concept or migration funding, and what the application needs[7].

4

First-project briefOptional

One page per recommended use case: goal, users, success measure, rough cost range and the next decision. Ready to hand to the Concept workshop.

01A scored shortlist
Use cases ranked on value and effort, with the reasoning written down so it can be argued with.
02An architecture per use case
The layer decision, where the data sits, and what it connects to.
03A cost model per service
What it costs to run at your volumes, not at a demo's volumes.
04A working prototype
On your own data, including the awkward records nobody wants to talk about.
05An MVP roadmap and a decision
Go, stop or narrow, with what would change the answer.
06A funding case
The evidence a cloud funding programme or an internal budget holder asks for.

Where Discovery fits: the scored shortlist is the first of six results across the full series. Concept and Decision add architecture, cost model, prototype, roadmap and funding case.Source: Linda Mohamed, Partner Enablement 2026

Price

Pay for the workshop, add the results you need

Tick the results you want. The total updates as you go. Net prices, plus VAT.

AI Discovery Workshop

Pre-session intake, the live workshop with up to 8 people, and the written results within 5 business days.

Workshop
€2,000 each, 3 to 4 hours, remote or on-site
1
Written results€1,000 per result
€1,000
€1,000
€1,000
€1,000
Your package
€4,000


Delivered within 5 business days after the last session.

Book the Discovery Workshop — €4,000

Secure checkout. Net price, plus VAT. I confirm dates with you before the first session.

Book a free 30-min Idea Call15-min question slot
Standard

Discovery

€4,0001 workshop + 2 results
Book and pay →
Series

Goal, Concept, Decision

€9,0003 workshops + 3 core results
See the full series →
Unsure?

Readiness first

€3,0001 workshop + scorecard
Try the free self-check →
How it runs

Discovery is session one of three

Each session ends with a decision. Sessions run one to four weeks apart, or as one long day if that suits your team better.

Session 1 · this workshop

Goal

Business problems, candidate use cases, scoring. Result: the ranked shortlist.

Session 2

Concept

Architecture per surviving use case, priced per AWS service and tested against real data.

Session 3

Decision

ROI, MVP scope and the funding case. Go, stop or narrow. Stopping early is a good outcome.

Session 1

Goal

The goal, the users and the scored shortlist.

1–4 weeks later

Concept

Architecture and cost for the top candidate.

1–4 weeks later

Decision

Go, stop or narrow, with the evidence behind it.

If it is a go

Funded proof of concept

Built on real data, often with cloud funding behind it.

Or all in one day. The gaps exist so your people can go and check things between sessions. Where that is not needed, the three sessions run back to back.

Pacing of the series. A cheap no after session two beats an expensive yes after six months.Source: Linda Mohamed, Partner Enablement 2026

The agenda

How a first workshop actually runs

The agenda I bring to a Discovery session. Timings shift with the group, the order rarely does.

Block one

Goal definition

What the organisation is trying to change, and what would count as proof. Everyone in the room writes it down separately first — the differences are the useful part.

Block two

Use cases

The candidates, and the named users behind each one. A use case without a named user does not leave the room.

Block three

Test data

What data exists, who owns it, and which awkward records have to be in any prototype.

Block four

Next steps

The shortlist, scored, and who does what before the next session.

Four blocks in one to three hours: goals, use cases, the data behind them, and the next steps. The right column is what leadership gets out of it.Source: Linda Mohamed, AI Use Cases Workshop deck, 2026

Workshop one

Discovery

Use cases, users and a scored shortlist. The disagreement in the room is the useful part.

Workshop two

Concept

Architecture sketches, effort, data access and the gaps nobody had written down.

Workshop three

Prototype

Built and evaluated on your data. After this the work moves to your engineers or a partner.

Then

First functional version

An MVP with real users on it, built by your team or an implementation partner.

Finally

Market-ready solution

Scaled, operated and owned. The point the ladder was climbing towards.

Where Discovery sits in the series, and where the work moves to your engineers or an implementation partner.Source: Linda Mohamed, AI Use Cases Workshop deck, 2026

Deck slide: typical agenda for a first discovery workshop, with goal definition, use cases, test data and next steps
The agenda slide itself, as it goes out before the session. Four blocks, and the perspective each one is answered from.Source: Linda Mohamed, AI Use Cases Workshop deck, 2026
Deck slide: workshop modules with content, result and perspective columns for the goal, technology and customer sessions
The modules behind the series. Discovery is module one: goals and requirements, and the use cases that come out of them.Source: Linda Mohamed, AI Use Cases Workshop deck, 2026
Use cases

Real patterns, documented in the open.

Examples of the use cases that come up in Discovery sessions. Each opens a write-up on ai-solutions.wiki, the open engineering reference I maintain, with architecture, services and trade-offs.

AWS services

The AWS services behind this work.

Discovery is not tied to one service. These are the ones that most often end up on the shortlist, with a plain note on what each does. The workshop checks which one fits before anyone builds.

Amazon Bedrock

Managed access to foundation models from several providers through one API. You choose the model and write the prompt; AWS runs the model.

Amazon Bedrock Knowledge Bases

Retrieval-augmented generation: your documents are chunked, embedded and stored in a vector store, and the relevant parts go into the prompt.

Amazon Textract

Reads text, forms and tables from scanned documents and returns them as structured data.

Amazon Transcribe

Speech to text with word timings, speaker labels and custom vocabularies.

Amazon SageMaker AI

Managed platform for the whole machine learning lifecycle: notebooks, training jobs, model registry and endpoints.

AWS Pricing Calculator

Builds a cost estimate per service before anything is deployed.

Funding

Check AWS funding before you pay.

Many AI proofs of concept and cloud migrations qualify for AWS funding: credits for the AWS usage and, in some partner programmes, funds for the delivery work. What applies depends on the project, the programme and the AWS account team. I check it in the Idea Call, and the workshop results are written so they can go straight into an application.

Proof of concept

Up to €10,000

For a prototype on AWS with a clear path to production.

Migration

Up to €400,000

For larger cloud moves, planned in phases.

How AWS funding for AI works →

Questions

What people ask before booking.

What does the AI Discovery Workshop cost?

€2,000 for the workshop plus €1,000 per written result. The standard package with the scored shortlist and the data and feasibility notes is €4,000 net. Additional results are optional.

Who should take part?

Up to 8 people: someone who owns the business problem, someone who knows the data, and someone from IT or engineering. Leadership joins for the last hour when the shortlist is agreed.

Do we need data or a clear idea before the workshop?

No. The intake form collects what you have. Sample data helps with the feasibility notes, but the session works without it.

Is the workshop tied to AWS?

The scoring is vendor-neutral. I build on AWS and hybrid platforms such as Red Hat OpenShift AI, and the feasibility notes name concrete services so the next step is buildable.

Can AWS funding pay for it?

Some projects qualify for AWS proof-of-concept funding. It depends on the project and the AWS account team, so I check it in the free Idea Call before you commit.

Remote or on-site?

Both. On-site in Vienna or anywhere in Europe (travel outside Vienna at cost), or fully remote. Sessions run in English or German.

Which AI case comes first for you

FREE DECK

AI Use Cases

Three use cases and one regulation. Each with the five questions that decide it.

  • The anatomy of a ticket
  • A selection matrix to fill in
  • A worksheet

51 pages. Large type, one idea per page, sources on every page. Double opt-in: you confirm by email first. Unsubscribe with one click.

Linda Mohamed, AWS Community Hero, AI and cloud architect in Vienna
Who runs it

Linda Mohamed

AWS Community HeroAWS User Group Vienna organiserLecturer, Hochschule BurgenlandAmazon Bedrock · SageMaker AI · OpenShift AIEN & DE

I design and build AI and cloud systems on AWS and hybrid platforms, and I teach how they work. I have organised the AWS User Group Vienna for more than seven years, co-organise AWS Community Day DACH, teach AI architectures at Hochschule Burgenland, speak at conferences in Europe and the US, and maintain ai-solutions.wiki. Based in Vienna. Remote or on-site, in English or German.

Projects, open source and talks →

Stay in the loop

Architecture notes, straight to your inbox.

New AI architecture write-ups, use cases added to ai-solutions.wiki, workshop dates and AWS community events in Vienna and online. Choose the topic you care about most.

  • Patterns and trade-offs from real AWS projects
  • Workshop and lab dates before they are announced
  • AWS User Group Vienna and Community Day events

Double opt-in: you confirm by email first. Unsubscribe with one click.

Start here

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.

  • Which of your ideas are worth a workshop
  • Who should be in the room
  • Whether AWS funding could apply
  • Which results you actually need

Vienna, Austria · remote across Europe · [email protected]