MVP Launch

From idea toProduct.In eight weeks.

One partner who decides, designs and builds. For entrepreneurs who want a product, not a concept.

  • max. 3core features
  • Design + codefrom one pair of hands
  • €25k to €35kfixed price
  • Deutsche Bahn
  • KPMG
  • BMW
  • B/S/H/
  • Porsche
  • Fraunhofer
  • Oddset
  • Asellion
  • Nuveon
  • &Charge
  • Frog Design
  • Design Works
  • Dracoon
  • Yokogawa
  • Neuform
  • SaaS Academy
  • Consorsbank
  • Aptis
  • Bagless
  • werstreamt.es
  • DKB
Hi, I’m Chris
Christian Saur, portraitChristian Saur · Product Designer & AI Builder

I design products.
And I build them.

Fifteen years of product design for Deutsche Bahn, DKB, Porsche and BMW. Today with a team of AI agents that keeps design and development in one pair of hands.

I make the calls. Something real runs early. Then it gets better, round after round:

  1. Think
  2. Design
  3. Build
  4. Use
  5. Adjust
From team to partner

An MVP used to take a whole team.

First you have to find the people. Then everyone hands their work to the next person. Months pass before a single user sees anything.

61Launch · month

Today it takes one partner.

You bring what you know, I design and build, the AI agents bring speed. All at once, in eight weeks together.

8Launch · week
  • Find the team
    Team & strategy
  • Product Manager
    Team & strategy
  • UX Design
    Design
  • UI Design
    Design
  • Frontend
    Development
  • Backend
    Development
  • QA
    Test & harden
  • Growth
    Launch
  • You
    Domain expertise & decisions · Team & strategyFeedback · Test & hardenFeedback · Test & hardenFeedback · Test & hardenYou test itLaunch
  • Me
    Define · Team & strategyDirection · DesignPrototype in code · DevelopmentBuild the product · DevelopmentHarden · Test & hardenLaunch · Launch
  • AI agents
    Exploration, UI variants · DesignFrontend, backend, tests · Development

Team & strategyDesignDevelopmentTest & hardenLaunch

The new model

One partner.
A whole team.

I don’t let an AI throw your app together. I decide with you what truly needs building. Then I build it.

  • Youknow your business.
  • Iknow what a good product needs.
  • AIturns one person into a team.
Stays with me

Everything that takes judgment.

  • What gets built
  • How it feels
  • How it looks
  • How it stands technically
  • What can wait
  • Whether it’s good enough
My agents take on

Everything that can be multiplied.

  • Design variants
  • Design system
  • Frontend
  • Backend
  • Tests
  • Documentation
Both sides

I speak both languages.

With you I talk about customers, workflows and revenue. With the code, about data, interfaces and states. Nothing gets lost in between, because nobody sits in between.

You say: Our customers want an answer faster.
I build: Streamed response, progress visible at once, one endpoint.
You say: The team needs the overview, not every detail.
I build: Condensed view, filter by role, dashboard without setup.
You say: Paying must not be a hurdle.
I build: Stripe Checkout, trial without a card, status via webhook.
You say: Trust comes with the first success.
I build: Onboarding straight to the core value, sample data, success moment measured.
Product philosophy

The question is not what we could build.

The question is what we must build.

Most MVPs don’t fail because too little was built. They fail because too much was built before anyone knew whether it was needed at all.

The 3-feature rule

Three features.
Your MVP gets no more.

Not because more isn’t possible. Because more doesn’t help.

We look for the three things someone would use your product for. Those we build properly. Everything else goes on the list for phase two.

As small as possible. Complete enough to prove whether your idea holds.

14 ideasbecome3 features

  • Dashboard
  • AI assistant (selected)
  • Teams
  • Roles & permissions
  • Notifications
  • Chat
  • Reporting (selected)
  • Export
  • Mobile app
  • Admin (selected)
  • Integrations
  • Onboarding
  • Dark mode
  • Comments
First version
  • 01InputThe user enters the core data.
  • 02ProcessingThe product analyses it.
  • 03ResultThe user acts on the outcome.

Phase 211 ideas, safely parked

Eight weeks, one rhythm

Decide clearly.
Use it early.
Actually launch.

Design and development run side by side. You have the product in your hands long before it is finished.

Week 1 to 8

  1. 01 · DefineWeek 1

    We find the product inside your idea.

    Who it is for, which problem it solves, which three features count. And what we deliberately leave out.

  2. 02 · DesignWeek 1 to 2

    As much design as we need to decide.

    The key paths, the central screens, the visual language. Then we start building.

  3. 03 · Try it outWeek 2 to 4

    You use it instead of imagining it.

    Something real runs early. What feels awkward goes. What is missing gets added.

    FigmaCodeProductFeedback

  4. 04 · Build it outWeek 4 to 7

    The prototype becomes a product.

    Sign-up, payment, database, error cases, tests. Everything real users need.

  5. 05 · LaunchWeek 6 to 8

    We bring it to people.

    Landing page, message, measurement and a first path to your customers.

The outcome

You don’t end up with a concept.
You end up with a product.

No Figma file, no prototype someone still has to build. Instead:

  • An MVP running in production
  • Up to three core features
  • A clear design direction
  • A landing page that is live
  • A path to sign-up
  • Measurement from day one
  • A plan for your first users
  • A roadmap for phase two

Something you can show, sell and keep building on.

The proof

I built Elyvite exactly this way.

An AI platform that makes expert knowledge and scientific research accessible. From the initial concept to the payment flow: designed, built, and launched.

See the Elyvite case study
  • searchable knowledge passages
  • structured expert profiles
  • specialized research assistants
A search result showing how much the body of research agrees on a question
Research with a consensus view
The processing pipeline that ingests, checks and prepares studies
The pipeline behind it
Prepared research updates for professionals in healthcare
Knowledge for health professionals
What I ownedProduct decisionsUX / UIAI orchestrationFrontendBackendPaymentsOperations
  • PeriodSeptember 2025 to today
  • StatusOpen beta since June 2026
  • TeamJust me, plus an AI agent team I built for it

Before that: fifteen years of products with a lot at stake.

Rail, banking, automotive, industry. Systems with thousands of users, where a pretty interface is not enough. That judgement is what I bring. What is new is that today I carry it all the way to launch myself.

This fits if

you want something real.

  • You have a product idea, or a problem that needs solving.
  • You know your business and your customers.
  • You can narrow it down to what matters.
  • You want someone who pushes back, not someone who just executes.
This doesn’t fit if

you need something else.

  • You have a full team and only need another pair of hands.
  • You want fifty features built exactly as specified.
  • You are facing a large migration or an enterprise transformation.
  • You don’t want to cut anything from the first version.
The package

MVP Launch

About eight weeks.Up to three core features.A product that runs.

  • Product strategy
  • UX and design
  • Development with AI agents
  • A prototype you can use
  • The finished build
  • Landing page
  • Launch setup
  • A path to your first users
Typical investment

Fixed price, fixed scope, both agreed after the first conversation. No timesheets, no surprises, no design phase without end.

One goal. One price. One date.

After the launch

From here on, evidence counts. Not opinions.

We see what people do with the product, where they get stuck and what they love. That is what decides the next step. If you like, I stay on board.

Frequent questions

Good questions.
Short answers.

  • So is this AI-generated software?
    No. The AI makes me faster. What gets built, how it looks and whether it is good: that is my call.
  • Do you still work with Figma?
    Yes, wherever it helps us think. Just not for every single screen before a line of code exists.
  • Why only three features?
    Because the first version should answer one question: does anyone want this? That needs the right things, not all of them.
  • Are eight weeks guaranteed?
    Eight weeks is the format. Whether it fits your idea is what we settle in the first conversation, before we commit.
  • Who owns the product?
    You do. Code, design, everything.
  • What if we think of something new along the way?
    Then we trade it against something already in scope. Or it waits for phase two.
Got an idea?

Then let’s find out whether there is a product in it.

Thirty minutes, no concept and no presentation. Tell me about your idea and the problem behind it. We’ll see the rest together.

Message me on LinkedIn(opens in a new tab)

A short message on LinkedIn is enough · no pitch deck needed