MVP Development

MVPs shipped in 4-8 weeks for €15K-€40K. We are aggressive about what to cut so the thing actually launches and gets feedback from real users, not from a deck.

What MVP Delivers

• We Are Loud About What to Cut: Most "MVPs" we are asked to rescue are not minimum and not viable: they are 14-page Notion specs that took six months and never met a user. Our entire process is built around the opposite: what is the smallest thing we can put in front of ten real prospects in week one, and then iterate from their faces, not from internal opinions.
• Fixed Scope, Fixed Price, No Surprises: After a one-day discovery we send a written brief with exactly what is in and what is out, plus a fixed price between €15,000 and €40,000. Mid-project change requests get a one-line cost, not a renegotiation of the whole contract.
• Real Users in Front of It from Week One: On Friday of week one you have a clickable thing on a real domain. Even if half is mocked, you walk it through five prospects on Monday and bring back faces, not survey responses. That weekly cycle is the whole engine.
• Founder Inside the Build, Not Just Reviewing It: You join a daily 15-minute call, you see the staging URL change every afternoon, you comment in Linear by name, not via a project manager. The proximity to the build is what saves the bad call before it ships, not after.
• Built on Tech That Will Not Strand You: Next.js, Postgres, Stripe, Vercel or AWS: exactly the stack any junior-to-senior engineer can pick up. No Bubble, no Webflow with hacky logic, no untranspiled Rust. We optimise for "the next dev can clone the repo and ship a fix in an afternoon".
• A Clear Decision Point at the End: Week 8 we sit down with usage data, conversion data and qualitative interview notes. The output is a written recommendation: double down, pivot, or kill. No "lets keep going" by default: the framework forces a real call.

How We Build Your MVP

1. Risky-Belief Workshop: Half-day session. We force-rank everything you believe about the customer, price and channel. The single belief that, if false, kills the business: that is what the MVP tests.
2. Wireframe in Two Days: Low-fi screens in Figma covering the three or four flows that matter. We deliberately do not visual-design until the flow holds up against a real prospect interview.
3. Skeleton App on a Real Domain: End of week one: signup, primary action, payment if relevant, all on yourdomain.com with TLS. Crude. Stable. Demoable.
4. Weekly Demo, Cut, Build: Friday demo with you and three prospects on the call. Saturday you receive a one-page note: what we keep, what we cut, what we add. Monday we build that. Repeat.
5. Public Launch & Handover: We help you push the launch, then run a 60-minute handover: full repo walkthrough, how to deploy, how to read the metrics, what is fragile and why. You are operational without us by day one of v2.

High-performance stack used by global leaders

React/Next.js/Angular on the frontend and Java 21 + Spring Boot + PostgreSQL 14 on the backend: the same stack that BBVA, ING, and Netflix use for their security and performance.

MVP: FAQ

How much does an MVP cost?

Our fixed-scope MVPs land between €15,000 and €40,000. The bottom of that range is a single-purpose web app with one paid feature; the top is a richer flow with auth, payments, dashboards and a small admin tool. Anything above €40,000 is no longer an MVP in our book: it is a v1 and we price it differently.

How long does it really take?

Four weeks for the genuinely small ideas, eight weeks for the typical case. The few projects that drift past eight weeks always do so because someone added a "small" feature that was not small. That is exactly what our weekly demo + written cut-list is designed to prevent.

What counts as an MVP for you?

A product that lets a real user complete the core action and pay (or sign up to pay), nothing more. Admin tooling, role hierarchies, internationalisation, mobile native, granular notifications: all v2 by default. If a feature does not test a risky belief, it does not ship in the MVP.

Which stack do you build MVPs on?

Next.js + Postgres + Stripe + Vercel is the boring default. We deliberately avoid no-code: nothing kills momentum like hitting a Bubble ceiling at month three. The stack is chosen so that any future hire can clone the repo and be productive on day one.

When should we pivot or kill?

After eight weeks, if fewer than 5% of qualified prospects pay (or commit a verbal LOI for B2B), the data is screaming and we recommend a hard pivot or kill. We have killed our own ideas under the same rule. Sunk cost is not a reason to keep going: momentum without traction is the most expensive trap in startups.

What happens after launch?

Three options. One: full handover, you take the keys and we are gone (most of our clients). Two: a maintenance retainer of 10-25 hours per month for bug fixes and small improvements. Three: we stay as a fractional product team for v2. Whatever you pick, the code, infra and credentials are 100% yours from day one.

Can we do this with our own designer or developer in the loop?

Yes, and the projects where the founder embeds an in-house dev tend to be the cleanest. We pair, we do code review, we share the Linear board. Knowledge transfer is a feature, not a side effect: by week eight your team can move forward without us if they want to.

Do you work with clients globally?

Yes. We work fully remote with clients across Spain, Europe, the US and LATAM. Time zones, video calls and live demos at every milestone.