Stage 03 · Concept

The idea shown, not described

Architecture in plain notation, a cost model per AWS service at pilot and at production volume, and a small sample of your real data run through the service that would do the work.

  • AI Concept Workshop
  • €5,000 incl. 3 results
  • Your AWS account or a sandbox
  • English or German
What this stage is

Three decisions, taken once, written down

Concept answers the questions that get expensive if you guess: which layer of the stack you actually run, which services do the work, and what it costs per month when real volume arrives.

The layer decision is the one that compounds. A managed service is cheaper to start and more constrained later; your own model is the reverse[6]. Getting this wrong is not fatal at Concept and is very hard to undo two rungs up.

Cost is modelled per service in the AWS Pricing Calculator[2] using the published model prices[3], at pilot volume and at the volume the business actually expects. Larger decisions are written as short architecture decision records[9], so the reasoning survives the people.

A cheap no at Concept beats an expensive yes six months later.
What comes out

Three written results

The AI Concept Workshop is €5,000: one workshop with your engineers and the data owner, plus three written results.

1

Architecture per use caseIncluded

Services, data flows, boundaries and who operates what, in notation your team can read without a legend.

2

Cost model per serviceIncluded

Monthly cost per AWS service at pilot and at production volume, built in the pricing calculator rather than estimated.

3

Data test notesIncluded

A small sample of your real data through the chosen service, with what worked, what failed and where the limits are.

4

Production roadmapOptional

What it would take to run this properly: security, operations, scaling.

5

Funding caseOptional

The results written up for an AWS proof-of-concept funding request.

AWS services

The AWS services behind this work.

Plain-language notes on the services I use for this kind of project. Each name links to the official AWS documentation.

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 S3

Object storage for raw files, documents, training data and results.

AWS Pricing Calculator

Builds a cost estimate per service before anything is deployed.

What comes next

Concept is where stopping is cheapest

If the cost model says the economics do not work, or the data test says the documents are too messy, you have learned that for the price of one workshop rather than one project.

If it holds up, the next rung is a cloud demo: the same architecture, built small, running where people can click it.

01

Ideas

Who needs this most?

The idea said out loud, and who it is actually for. Out: a shortlist

Free 30-min call
02

Clarity

Is the idea clear?

Written so anyone in the room can repeat it back without you. Out: one page

03

Concept

Is it technically working?

The idea shown, not described: data, layer and approach chosen. Out: a concept

04

Cloud demo

Does it survive contact?

Something real to click, running in the cloud. Out: a demo you can try

2–24 hours
05

MVP / 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 months
06

Functional 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

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.

  • Whether your use case is ready for Concept
  • Which layer decision you are facing
  • What data you would need to share
  • Whether AWS funding could apply

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