An MVP that earns the next milestone. Not a bloated mess.
First client, first investor, or a validated idea. We build only what gets you there: a Discovery for EUR 3,500 that ends in a fixed-price offer, working software you can click every week, and a Werkvertrag that makes the price legally binding. From Tirol, for founders across Austria and the EU.
Three situations we see every month. The common thread: a deadline that matters more than a feature list.
First paying client
You sold the vision, now you need the product before the buyer cools off. We cut scope to the one flow that gets the contract signed and ship it. Everything else waits until revenue says otherwise.
First investor
The deck works, the demo doesn't exist. Investors fund traction, not slideware. We build the version that survives a due-diligence click-through and gives your metrics a place to live.
Validated idea, no tech team
You proved demand with a landing page, a waitlist, or a no-code prototype that is now duct tape. We turn it into production software you own, in your repo, with tests and monitoring from day one.
// 02
What a typical MVP build looks like
Scope decides the calendar. This is the shape, not a promise: every build starts with Discovery and ships working software weekly from the first sprint.
W 0-2
Discovery
Stakeholder interviews, the one metric that defines success, architecture, milestone plan. Ends with a fixed-price offer. EUR 3,500, deducted from the build invoice if you continue.
W 3-4
Walking skeleton
Auth, deployment pipeline, the thinnest end-to-end slice in production. Boring on purpose: this is the part that breaks vibe-coded prototypes later.
W 5-10
Weekly increments
One reviewable increment per week. You click it, we adjust. Features land in priority order so the build can stop at any milestone and still be a product.
W 11+
Harden and launch
QA pass, observability, store or domain launch. Then the honest conversation: what the usage data says you should build second.
// 03
What an MVP costs
No mystery quotes. Discovery is a fixed number, the build is priced against the scope Discovery produces, and the published cost bands tell you what to expect before you ever talk to us.
Discovery + Roadmap
Two to three weeks to the one document that prevents building the wrong thing: architecture, milestones, fixed-price offer.
2 to 3 weeks, fixed
€3,500fixed
Deducted in full from the build invoice if you continue.
Werkvertrag. Signed scope, legally bound to deliver.
An MVP is not a demo. Ours leave the building production-grade, because retrofitting quality costs more than building with it.
Production code in your repository, under your accounts, from day one.
Full IP transfer on payment. No Wavect retained rights, no vendor lock-in.
Tests and CI on every pull request, error tracking and structured logs from the first deploy.
Product judgment included: two founders who tell you when a feature is not worth its invoice.
// 05
When you should not build an MVP yet
You have not talked to a single potential customer. A landing page and ten conversations are cheaper than any MVP. Start with the road to product-market fit.
You want every feature of the five-year vision in version one. That is not an MVP, and we will say so in the first call.
What founders ask before they scope. Front-loaded answers.
Discovery is EUR 3,500 fixed and produces the number for your specific build. As published cost bands: a cross-platform app with login, core flow, and one paid feature typically lands at EUR 25-50k; AI-heavy MVPs run from EUR 5k for prompt integration to EUR 100k+ for multi-step agents. Full bands in how much an AI MVP costs in Austria.
Scope decides. Discovery takes 2 to 3 weeks and ends with a milestone calendar for your build. From the first sprint you see working software weekly, and the plan is sequenced so the build can stop at any milestone and still be a usable product.
Yes, by contract. The build runs as a Werkvertrag: signed scope, legally bound to deliver, the number does not move unless the scope does. If your scope genuinely cannot be locked yet, we say so and start on a weekly retainer instead. The trade-offs are documented in Werkvertrag vs time and material.
Yes, and we start by asking whether AI is the right tool at all. RAG over your documents, agent workflows, and prompt-layer integrations have very different cost and risk profiles. We budget the API spend into the proposal so the OpenAI invoice in month two is not a surprise.
You do. The code lives in your repository under your accounts from day one, and all work product is assigned to you on payment of the invoice. Full IP transfer, no retained rights. We do not even use your project in our portfolio without written permission.
Two options, no obligation: a weekly retainer keeps shipping the roadmap, or we hand over cleanly to your future team with documentation and an onboarding call. Most founders run usage data for a few weeks, then scope iteration two.
Sometimes you should, and we will tell you when. A freelancer wins on a defined ticket, no-code wins on pure validation. We win when the MVP must survive real users, real payments, and a due-diligence review. The honest comparison is in Wavect vs freelance platforms.
Tell us the milestone. We scope the shortest path.
30 minutes, free. You leave with a sharper scope even if you build elsewhere. If an MVP is the wrong move for your stage, we say that too.