Wall & Fifth

MVP Development for Founders: What Changes at Each Stage

How the purpose of an MVP changes between pre-seed and seed stage, what to build at each, and what stays constant regardless of funding.

By William · Updated 1 November 2026 · 11 min read

The job of an MVP changes the moment you raise money. Before a raise, you are testing whether anyone wants what you are building. After it, you are building the foundation that your next hire and your next investor will judge you on. These two objectives pull in different directions, and confusing them is one of the most common reasons founders either over-build before they have product-market fit or under-build once they have the budget to do it properly. The broader question of how to evaluate and choose a studio is covered in the guide to choosing an MVP development company in the UK. This guide draws the pre-seed and seed line clearly so you can brief a studio with the right scope at the right moment.

Why the purpose of an MVP shifts after a raise

The term minimum viable product was coined by Frank Robinson in 2001 and later popularised by Steve Blank and Eric Ries. [1] Eric Ries defined it as the version of a new product that allows a team to collect the maximum amount of validated learning about customers with the least effort. [2] That definition is learning-first. The word minimum is doing real work: it tells you to build only what is necessary to find out whether your hypothesis is correct, and nothing more.

At pre-seed, that framing maps directly onto your situation. You have limited capital, an unproven idea and no confirmed market. The most valuable thing you can produce is evidence — does anyone log in, return, and eventually pay? Every feature that is not part of the core loop is noise that costs money and delays the signal.

After a seed raise the calculation shifts. You now have capital, a team growing beyond one or two people, and investors watching how you allocate both. The product needs to carry more weight: it has to work reliably for new users who did not benefit from a founder personally onboarding them, withstand scrutiny from a technical co-founder or senior engineer joining the business, and support the operational patterns of a real company rather than a scrappy experiment. Learning still matters, but the architecture has to survive growth.

This is not an argument for building more at seed stage. It is an argument for building differently — making considered structural decisions that a pre-seed build can reasonably defer.

Pre-seed MVP priorities

Define one core job and protect it ruthlessly

The most important discipline at pre-seed is scope control. Your MVP should do one thing well enough that a user can arrive, complete the core action, and give you a clear signal about whether they would come back. Everything else — billing, admin panels, notifications, multi-user access, reporting — belongs on a deliberate out-of-scope list, not a future sprint.

A useful test: write a single sentence describing the core job your product does for its primary user. If the sentence requires two verbs, your scope probably covers two products. Reduce it until there is one action, one outcome, and one user type. That sentence should govern every scoping conversation you have with a studio.

Speed to feedback, not speed to market

Founders sometimes conflate moving fast with launching fast. They are not the same. Launching a poorly considered product quickly gives you feedback about a poorly considered product, which is not especially useful. What you want is to reach the moment of real user behaviour as quickly as possible — the first session where a user encounters the product without you present to explain it.

That means spending serious time on the work before a line of code is written: the core user flow, the data model, the interface decisions. The design and architecture phase is where most of the structural thinking happens, and compressing it to save time usually costs more than it saves later.

Deliberate deferral: what not to build

At pre-seed, the following are almost always deferrable without meaningful cost to your learning:

  • Admin panels and internal dashboards. Use your database directly, or accept manual operations. An admin panel is for teams managing volume; you do not have volume yet.
  • Complex billing and subscription management. A simple Stripe integration to take payment is sufficient. Dunning logic, plan tiers, proration and invoice management can wait until you understand what your pricing actually needs to be.
  • Email and notification flows. A transactional confirmation email is reasonable. An automated onboarding sequence with branching logic is not a pre-seed decision.
  • Multiple user roles and permissions. Unless your product literally cannot function without two distinct user types — a marketplace is the classic exception — start with one user type and add the second after you have validated the first.
  • Marketing site. A landing page is enough to support launch. A fully built marketing site with CMS, blog and SEO infrastructure is a post-validation concern.

None of these decisions make your product weaker for learning purposes. They make the scope smaller, the timeline shorter and the signal cleaner.

Seed-stage MVP priorities

Investor-ready product quality

At seed stage, your product will be used — and judged — by people who did not choose to use it out of enthusiasm. They are users acquired through marketing, referred through partners, or simply handed a link by someone who told them it was good. The tolerance for rough edges drops sharply, and the tolerance for confusion drops to near zero.

Investor-ready does not mean polished in the cosmetic sense. It means that the product behaves predictably, recovers gracefully from errors, and does not require a founder to explain how it works. Onboarding in particular deserves real investment at seed stage: the first few minutes of a new user's experience will determine whether the product appears to work or appear broken, regardless of what the software actually does underneath.

Architecture that survives the next hire

The most common technical cost of a rushed pre-seed build is an architecture that a second developer cannot work in. When that second developer joins — and at seed stage, it is a common early pattern — they will form a rapid judgement about the codebase. If it is structurally unclear, inconsistently typed, or missing the conventions a senior engineer expects, the first month of their time disappears into understanding rather than building.

Seed-stage builds should use a well-documented, hireable stack, enforce consistent conventions, and separate concerns cleanly enough that a new engineer can work in one area of the product without having to understand all of it. For most web products this means a typed framework such as Next.js with TypeScript, a structured database schema with clear naming, and API routes that correspond to the actual domain objects rather than improvised endpoints.

For a more detailed view of how the right technical foundation affects what you can build later, the guide on what to confirm before your build starts covers the technical decisions that are cheap to make upfront and expensive to fix afterwards.

Multi-user access and permissions

By seed stage, most products need to support more than one user type. A SaaS product needs team accounts. A marketplace needs buyer and seller flows. A platform serving professional services firms needs admin access for the firm and limited access for their clients. These are not features to add after launch — they affect the data model, the routing logic, the session handling and the UI simultaneously.

The right moment to design multi-user access is at the architecture stage, before the database is built. Adding it afterwards means restructuring tables, rewriting session logic and revisiting every screen that shows or hides data based on role. It is one of the most reliable sources of expensive rework in early-stage products.

Hypothetical example: two founders, same idea, different stage

The following is a hypothetical example to illustrate how scope changes between stages.

Two founders approach a studio with the same idea: a platform that connects independent consultants with small businesses for short project engagements. Founder A is pre-seed, testing whether consultants will list themselves and whether businesses will reach out. Founder B has just closed a seed round and needs to launch commercially within ninety days.

Founder A's MVP covers: consultant profiles, a business-facing search and filter, and a contact request form that sends an email. No billing, no messaging, no ratings, no admin panel. The whole thing takes six weeks to build and produces a clear signal within the first month of launch.

Founder B's build covers everything in Founder A's scope, plus: two distinct account types with separate dashboards, a Stripe-based escrow payment flow, an in-product messaging thread, email notifications for key events, and an admin panel for managing disputes and flagged accounts. This takes ten to twelve weeks and costs significantly more — but Founder B is launching to paying customers with investors watching, so the investment is justified by the commercial reality.

Same idea. Very different products. The difference is not ambition — it is stage-appropriate scope.

What stays constant regardless of stage

Two things should not change between pre-seed and seed, and should not change regardless of budget or timeline pressure.

Real code, owned outright

A no-code or low-code build can appear attractive at pre-seed given the pressure to conserve runway. In practice, this is an approach worth scrutinising carefully. The moment your product needs custom logic — conditional workflows, complex permissions, non-standard integrations — you reach the limits of the platform. The rebuild that follows tends to arrive at the worst possible moment: when you are trying to scale, not when you have the breathing room to do it properly. Treating no-code as a permanent foundation, rather than a time-bounded experiment, is a structural risk worth weighing against the short-term saving.

Production code on a hireable stack, owned outright by the client, is the baseline that separates a product with a future from one that needs replacing. Wall & Fifth builds on Next.js, React, TypeScript and PostgreSQL for web products, and React Native for mobile — mainstream choices that any competent developer can work with from day one.

No lock-in of any kind

Code ownership extends beyond the repository. Your hosting accounts, your domain, your database, your third-party service accounts — all of these should be in your name from the start. A studio that retains hosting or platform access as part of the engagement is not a partner; it is a dependency. When you want to switch direction, bring on a technical co-founder, or raise a Series A with a new CTO doing due diligence, the last thing you need is a conversation about access with a previous supplier.

How Wall & Fifth scopes differently by stage

The scoping conversation at Wall & Fifth begins with one question before any feature discussion: what does this build need to prove or deliver, and by when? The answer determines whether the right engagement is a fixed-price MVP build, a more extensive build with multiple user types and integrations scoped individually, or a Product & Technology Partnership for founders who need ongoing product development after initial launch.

Pre-seed founders typically need the tightest scope and the clearest handover: real code, core flow working, deployed to production, everything owned. Seed-stage founders typically need the same foundation with more surfaces — admin tooling, permissions, payments, onboarding — and a team they can stay with rather than hand off to.

Both are valid. The studio's job is to identify which one you actually need, not to default to the larger scope because it produces a higher invoice.

Three questions to answer before briefing a studio

Before you send a brief to any studio, answer these questions with your co-founder or alone. They will sharpen the conversation considerably.

  1. What is the one thing this product needs to do in version one? Write it as a single sentence. If it requires more than one verb, reduce it.
  2. What is the specific assumption you are testing? Not a goal, not a vision — a hypothesis that this build will either validate or invalidate. If you cannot state the assumption, you cannot evaluate the result.
  3. What happens after launch? Are you looking for traction evidence to raise, or are you already funded and building toward a commercial launch? The answer changes the scope, the architecture and the right kind of partner.

The answers will also tell you whether you are at a pre-seed or seed stage in terms of product maturity, independent of how much capital you have raised.

Frequently asked questions

Can a pre-seed MVP be used in a seed-round pitch?

Yes, and a well-built pre-seed MVP is often the most persuasive thing in a seed deck. Investors are not looking for a complete product — they are looking for evidence that you can ship, that users engage, and that the core hypothesis holds. A focused MVP that has real users and a clear retention signal is more compelling than a feature-rich product with no evidence of use. The key is that it needs to be real software, not a prototype or a demo environment, because serious investors will ask to see it in action.

Should I add payments to my pre-seed MVP?

Only if payment itself is the thing being tested. If your hypothesis is about whether users will engage with the product, you do not need a payment flow to validate it. If your hypothesis is specifically about willingness to pay — and for many founders that is the right thing to test — then a minimal Stripe integration to take a single payment is reasonable. A full subscription billing system with tiers, trials and dunning logic is not a pre-seed decision.

How do I know if my architecture is good enough for seed stage?

The clearest signal is whether a competent developer who was not involved in the build can understand and extend it within a day or two of looking at it. If the answer is no — because conventions are inconsistent, the data model is unclear, or the codebase lacks documentation — you have technical debt that will cost you at the point of hiring. A brief code review from an independent senior developer before your hire arrives is a worthwhile investment.

My MVP was built by a freelancer and needs reworking. Should I rebuild or extend?

The honest answer depends on the codebase, not the cost. A rebuild is warranted when the data model is structurally wrong, the stack is proprietary or unhireable, or the code is too inconsistent to extend safely. Extension is appropriate when the foundations are sound but the product simply needs more surfaces. The worst outcome is extending a broken foundation because rebuilding feels expensive — that approach compounds the problem at every subsequent feature. If you are unsure, a technical review before committing to either direction will save significant time and money.

Does Wall & Fifth work with pre-seed founders as well as funded ones?

Yes. Wall & Fifth builds fixed-price MVPs for founders who need a real product quickly without open-ended billing risk, whether or not they have raised external capital. The scope is agreed before work starts, the timeline is eight weeks, and the codebase transfers to you completely at handover. Founders who have raised and need more capability — multiple user types, integrations, an admin layer — are typically scoped individually before a fixed price is agreed.

Back to MVP Development Company UK: How to Choose, What to Pay, and What to Avoid

Sources

  1. Minimum viable product - Wikipedia
  2. What is a Minimum Viable Product (MVP)? | Agile Alliance

Work with Wall & Fifth

Have something to build? Let’s talk it through.

Start a conversationSee our work