Wall & Fifth
Start a conversation

Home/MVP Development/Process

The Process

Eight weeks,
with nothing hidden.

A fixed timeline only works if the process behind it is real. Here is exactly how an eight-week MVP build runs, week by week, what happens at each stage, and the small number of moments we need you.

Book a scoping call →

The four phases

How the eight weeks
actually break down.

Weeks 1 to 2 - Scope and design

We pin down what gets built and what does not, map the core user flows, and design the screens. This is where your input matters most, because decisions are cheap to change now and expensive later. You approve the plan before a line of code is written.

Weeks 3 to 6 - Build

Full-stack development: database, authentication, the core features, payments where needed, and deployment. A live preview environment updates continuously, so you watch it take shape rather than waiting for a reveal.

Weeks 7 to 8 - Test and launch

Edge cases, bug fixing, performance, and polish, then deployment to production. The product goes live, on real infrastructure, ready for real users. No development server pretending to be finished.

Handover

The complete Git repository, the live product, accounts and access, and documentation, handed to you. Code, design, and IP fully yours. No lock-in, no fee to keep it running, ready for your team or ours to keep building.

Product image placeholder

Your part in it

What is asked
of you.

Heavy input early

In weeks one and two you help shape scope and flows. This is the cheapest time to decide things, so we front-load it.

A weekly review

One regular checkpoint to look at the live preview, give direction, and keep the build pointed the right way.

Quick answers, not management

Occasional specific questions during the build. You are involved at the right moments, not running the project day to day.

Sign-off before launch

You see and approve the product on the preview environment before it goes live. Nothing is a surprise at the end.

A clean handover

At the end you receive everything, with a walkthrough so you know what you own and how it runs.

What it costs

A fixed process,
at a fixed price.

MVP Build

16,000 GBP

The full eight-week process for one core product. Scope, design, build, launch, and handover, fixed price, code fully yours.

Extensive MVP Build

30,000 GBP

The same process over 8 to 10 weeks for a larger system with admin, integrations, and multiple user types.

Common questions

Before you get in touch.

How long does the process take?

Eight weeks for a standard build: scoping and design weeks one and two, development weeks three to six, testing and launch weeks seven and eight. Complex systems run eight to ten, agreed before we start.

What do you need from me?

Most input early, in scoping and design, where decisions are cheap to change. After that, a weekly review and quick answers to specific questions. You are involved at the right moments, not managing it day to day.

Can I see progress before launch?

Yes. A live preview environment from early in development, updated continuously, so you watch the product take shape. No surprises at launch because you have seen every step.

What happens at handover?

You receive the complete repository, the deployed live product, accounts and access, and documentation. Code, design, and IP fully yours. No lock-in, no ongoing fee to keep it running.

What if scope changes mid-build?

Small refinements within scope are normal and absorbed. A genuine scope change is discussed openly: we agree the effect on timeline and price before doing it, so nothing changes silently or surprises you on an invoice.

Why fixed price?

Because a real, scoped process makes it possible. We know what the eight weeks contain, so we can commit to the number. If it takes longer, that is our risk, not your larger invoice.

See the whole plan before you commit.

Book a scoping call →