Valas
ENSLBGDE
WhatsApp →
Menu
For founders before the first build · pre-seed and seed

Three MVP quotes, €15k to €90k. Nobody has answered whether to build it.

A six-fold spread isn't a market - it's a sign that no one has done the work of finding out what you actually need. Before you pay for an MVP, pay for the answer: go, change, or stop. We get it with a working prototype, real users and real paid traffic - in weeks.

Send us the idea on WhatsApp → What happens in those weeks ↓
Start within a day · A demo you can click every week · Stop any time
You'll recognise this

Every quote says "it depends", and nobody tells you what it depends on. You've spent three weeks arguing about features with people who have never talked to your users.

You're non-technical. Developers want to see money or customers before they take you seriously, and you can't get either without a product.

You've read the "learn from my €40k mistake" posts. Six months, a finished app, zero revenue - because the question "should this exist?" was never asked out loud.

What happens in those weeks

We try to break the idea before you fund it.

01
Name the riskiest assumptionNot the feature list - the one belief that, if wrong, makes everything else irrelevant. Usually it's "people will pay for this", sometimes "we can reach them for less than they're worth".
02
Prototype it in working codeA thing people can click, sign up for and try to pay for - a smaller bet, not a smaller app. Built with the same AI tooling you've heard about, by people who know where it lies.
03
Put it in front of real peopleTen good customer conversations around one painful workflow. We watch what they do, not what they say.
04
Buy real traffic, read real signalsA small paid campaign tells you CTR, cost per sign-up and intent for a few hundred euros - before you've spent fifty thousand finding out the hard way.
05
Decide: go, change, or stopA short memo you can show a co-founder or an investor: what we tested, what we saw, what we'd build, what we'd cut, and what "done" means for the first version.
What you leave with

Evidence you can take to anyone - including a different team.

A working prototype real users have touched. Real signals: conversion, cost per sign-up, what people said and did. Product logic and architecture ready for the build, with a cut list of what not to build first.

Positioning and go-to-market hypotheses already tested against paid traffic. And a decision you can defend: build, change, or stop - with the reasons.

If the answer is "stop", you've lost weeks, not a year. If it's "go", the same people build it - no handover, no re-explaining.

We've done this to our own ideas
Validated with a partner school first
An adaptive-learning product for neurodivergent children started as a prototype tested in a real classroom before anyone talked about scale.
Relaunched on evidence
A consumer nutrition app we took over was re-scoped around what users actually did, then entered the US market - not around the original feature list.
Shut down on evidence
Two of our own prototypes reached the app store and were closed when the signals didn't hold. That's the method working, not failing.
What this is not

Not a workshop. Not a deck. Not a cheap MVP.

Workshops and sprints end with sticky notes and nobody to pick up the work. Ours ends with code, data and the team that will build the product if it should be built.

We don't compete with a €200 AI subscription on price. You're paying for the judgment to know what to test, the engineering to make it real, and someone accountable for the answer.

Payments are tied to milestones you can click. Stop after any of them.

Send us the idea and the quotes you have. We'll tell you what we'd cut first - on the first call.

We’re built for fast communication: no forms, no briefs, no call to book. Just write - a senior on the team replies directly.

Write us on WhatsApp → or Telegram
For more formal inquiries: connect@valas.team

Validate the idea before you pay for MVP development

Most founders search for "how much does an MVP cost" and get the same answer in three different fonts: somewhere between €10k and €90k, "depending on scope". The spread isn't dishonesty. It reflects the fact that each team is pricing a different product, because nobody - including you - has yet decided what the smallest thing worth building is. That decision is the work. We've written up what each MVP price hides and what to bring a developer so they take you seriously.

Product discovery, as practitioners call it, is the process of answering that question with evidence rather than opinion. Done badly, it's a slide deck and a workshop. Done well, it's a working prototype, a dozen honest conversations with the people you intend to charge, and a few hundred euros of paid traffic that tell you whether those people can be reached at a price that makes sense. The output is not a plan - it's a decision: go, change, or stop.

Why a prototype and not a specification

A specification describes what you believe. A prototype tests it. When a real person tries to complete a real task in something that works - even if it works narrowly - you learn things no interview reveals: where they hesitate, what they expected to happen, whether they come back the next day. The prototype forces honesty through reality. It also produces something a specification never can: a conversion number.

Why paid traffic, this early

Because paid traffic exposes a weak proposition faster than anything else. If the people you're targeting won't click a plain ad that states your promise, they're unlikely to install, sign up and pay once the product exists. A small campaign gives you click-through rate, cost per sign-up and the first evidence of intent - the same numbers an investor will ask for, and the numbers that decide whether the business can afford its own customers.

Who this is for

Founders at pre-seed and seed, especially non-technical ones, who have an idea and a budget but no evidence yet. Founders with an existing business testing a new line. Anyone holding several MVP quotes and feeling that the real question hasn't been asked. It is not for teams that have already found traction and need to scale - for them, see installs ≠ users - or for products that were already built and need to be finished properly, which is covered under vibe-coded → production.

Frequently asked

How long does it take?

Weeks, not quarters. We start within a day of agreeing, you see a clickable demo every week, and you can stop at any milestone.

Does the prototype become the product?

Often parts of it do; sometimes none of it should. The point of the prototype is the answer, not the code. If the answer is "go", the same team builds the product on the logic and architecture the test produced.

What if the answer is "stop"?

Then you've spent weeks and a fraction of an MVP budget to avoid a year and all of it. You keep everything we produced - including the evidence of what didn't work, which is worth more than most pitch decks.

Can I take the results to another team?

Yes. Prototype, data, memo and architecture notes are yours. We'd rather you build with us, but we don't earn that by holding anything hostage.

Do you take equity?

No. Equity at this stage is worth nothing; execution is. We invoice, with EU VAT, against milestones.

Also
Already built it with Lovable or Cursor? → Validating inside a company? → All situations →