MVP / Business system

The first version of your SaaS or business system, priced up front.

I build two kinds of product: SaaS from scratch, and websites with a system built in, such as a CRM, client portal, bookings or orders. You get a working version you can put in front of real users and measure.

  • 3 phases
    two weeks each, to version 1
  • One point of contact
    no PM layer between us
  • Priced up front
    scope and cost of every phase in writing
Who this is for

Who this offer is for

This works best with one kind of client: someone who already knows what they need to validate and wants the first version built without it turning into a six-month project.

TYPE A

Founder in the validation stage

You have an idea and you want the market to answer quickly. A full product isn't the point; a working version you can put in front of users and measure is.

TYPE B

Creator with an audience

You already have people listening, whether that's a newsletter, LinkedIn or a community, and you want to turn an offer into a simple SaaS. Burning 6 months before finding out whether anyone pays isn't an option.

TYPE C

A business running on spreadsheets

Orders, clients or bookings live in email and Excel. I build a website with a system inside it that takes the process over and gives your team those hours back.

Scope

What's included in the base MVP scope

The base scope is 3 two-week phases, from €5,700 net. Anything beyond it becomes a later phase with its own price, which is why version 1 lands on time.

  1. 01

    2 core business features

    The ones the product can't work without. Everything else waits for phase two.

  2. 02

    User login (auth)

    Email + password or social login (Google), with password recovery and basic onboarding.

  3. 03

    1 key integration

    Stripe for payments, the OpenAI or Anthropic API, Google Calendar, your CRM. We pick whichever one carries the most weight.

  4. 04

    Simple dashboard / user panel

    Where a user sees their status and what they've done. Not a reporting suite.

  5. 05

    Deployment on your target domain

    A real production environment: hosting, SSL, database backups and monitoring on the basics.

  6. 06

    Basic onboarding / starting flow

    The first user path, getting them to the "aha moment" in under 2 minutes.

Scope boundaries

What doesn't fit into the base scope

All of this is left out on purpose, because that's how the first version fits the time and the budget. Any of it can happen in phase two at its own price.

  • More than 2–4 core user flows
  • Multiple roles and advanced permissions (e.g. team accounts, role-based access)
  • An extensive admin panel (advanced reports, segmentation, operational tools)
  • A marketplace with a full two-sided workflow
  • A native mobile app (iOS / Android)
  • A custom AI/ML model trained on your data

Anything outside the base scope becomes phase two or a separate order, quoted on its own.

Process

How it works in practice

First contact to a working version 1 runs about 7 to 8 weeks. The build itself is 3 two-week phases; the rest goes on the brief, discovery and launch.

  1. 01

    Brief + short call

    3–5 days

    You describe the idea and the goal in the brief, then we take 15 to 20 minutes on a call to check the project fits this model and that we want the same thing. If it does, we go to discovery.

  2. 02

    Discovery + scope

    3–5 days

    60 to 90 minutes cutting the idea down to 2 core features and one integration. You leave with the scope written down, split into phases, with a price and a date. Nobody says "we'll figure it out as we go".

  3. 03

    Build

    3 × 2 weeks

    Every phase ends with a sign-off on a working part of the product. You get staging access in week one and feedback goes in weekly batches. You pay for phases you have signed off, not for hours.

  4. 04

    Launch + iteration

    1 week

    Production deploy, a short handover, and every access and repo transferred to you. From there we plan the next phase with its own scope and price, or your own team takes it over completely.

Comparison

Why this is different from a classic software house

Some projects belong at a software house and some belong here. Worth knowing which is which before you commit a budget.

Classic software house
My model
3–6 months to a working version
6 weeks to version 1
Sales rep, PM, designer, then a developer
One person accountable: me
Scope grows, so does the price
Fixed base scope, extras priced separately
Building in "just in case"
Only what actually tests the business hypothesis
Estimates instead of commitments
Fixed price and timeline after discovery
Work

What I've already built

I build my own products alongside client work, which is where I test the decisions before recommending them to you.

[ STOCK PLACEHOLDER ]
Client MVPs · SOON
Soon

Client MVPs

The first projects under this offer are in progress. A case study lands here as soon as one of them is live.

FAQ

Frequently asked questions.

The base scope is 3 two-week phases, from €5,700 net. The exact number comes out of discovery, once the scope and the phase split are written down.
A working version 1 with the base features, live on your domain. It's ready for users and feedback. It is not ready to scale, and that's deliberate.
Yes, in further phases, each with its scope and price agreed before it starts. Your own team can also take the whole thing over, since the code is yours either way.
Next.js with Postgres, hosted on Vercel or Railway. For AI features I integrate OpenAI or Anthropic models directly. The stack follows the project, never the reverse.
Yes. Once the final payment clears, the code, the database, the docs and every access token are transferred to you. Nothing is held back to keep you tied in.
Then it takes more phases. The first three give you a working version 1 and later ones add features. You know the price of every phase before it starts.
That's where most people start, and it's what discovery is for. Bring the idea and a clear sense of the problem behind it; we narrow the rest down on the call.
Yes, where the project genuinely calls for one. A standard NDA covering non-public information usually does the job. Strictly confidential work runs under full white-label terms, priced separately.
No. You pay a fixed price for a written scope, split into phases. After any phase you have signed off, you can stop and keep everything you paid for.
Brief

Fill in the brief, I'll reply within 24h.

Four short steps. The more specific you are, the more useful my answer gets. Every brief lands in my inbox, not in a sequence.

Step 1 / 4 · Project type

What do you plan to build?

Pick whichever is closest to your situation; details come in the next step.

Have a product or system in mind? Let's count the phases.

The brief takes 5 minutes. You get back either a proposed scope with a price, or a straight answer that this isn't a project for me.

Cookie settings

You decide which cookies I use. Necessary ones are always active because the site does not work without them. The rest is up to you, and you can change your mind at any time. Details in the privacy policy.

Necessary Always active

Required for the site to work: security, network handling, accessibility and remembering your cookie choice. The site does not work properly without them.

Preferences

Remember your settings (like language or region) to adapt the site to you on future visits.

Analytics

Collect anonymous statistics (which pages you visit and how you use the site) so I can improve it.

Marketing

Allow more relevant ads and measuring their performance, also on other sites.