insights

What can you actually build in a 4-week MVP sprint?

2026-06-03

Four weeks sounds short. The first reaction most founders have is "no way you can build my idea that fast."

Sometimes that is true. Most of the time, the idea is bigger than it needs to be. A 4-week MVP is not a smaller version of your eventual product. It is the smallest thing that proves your idea is worth pursuing.

This post shows you three real shapes that fit in four weeks, what is included, what is not, and how to tell whether your idea fits the format.

##What a 4-week MVP is for

Four weeks is the right length when your goal is one of these:

Put a working product in front of real users and watch them use it
Take pre-orders or first paying customers with a real account flow
Demo to investors with something they can click, not a slide
Replace a spreadsheet or a manual process with software your team owns
Validate whether the technical approach holds up before you commit to a v1

It is the wrong length when your goal is "ship the final product." That is not what an MVP is.

##The 4-week shape

Every 4-week MVP has roughly the same skeleton:

Auth. Sign up, log in, password reset. Email or magic link or OAuth, one of the three.
One core workflow. The thing your users come to your app to do. Built end to end. Not stubbed.
A real database. Not LocalStorage, not a spreadsheet. Postgres, D1, or equivalent.
Admin views. You can see and edit your data without a developer.
One paid plan, if you charge. Stripe subscription or one-time. No tiers, no proration.
Email notifications for the key events. Welcome, password reset, transactional.
A deploy to your own accounts. Cloudflare or Vercel, your domain.

Everything in your MVP has to slot into that skeleton. If it does not, it is v2.

##Shape 1: B2B SaaS workflow tool

A team-based product where one person invites their team and they all work on something together.

What ships:

Email sign up, magic link login, password reset
Team workspaces with invites and roles (admin, member)
The core workflow done end to end (e.g. submit-review-approve, create-edit-share, plan-track-report)
Postgres database with admin views
Stripe subscription, one plan, one price
Email notifications for invites and key state changes
A simple dashboard the team lead sees on login
Deploy to your Cloudflare or Vercel account

What does not ship:

Per-seat billing, proration, dunning
SSO, SAML, SCIM
Multiple roles beyond admin/member
An audit log
A reporting suite

Real example shape: a feedback tracker for product teams. Submit feedback, route it to the right person, see the queue, mark it done. One workflow, two roles, one paid plan.

##Shape 2: Two-sided marketplace MVP

A product where two user types interact through your platform.

This one is harder to fit in four weeks because two user types means two onboarding flows, two dashboards, and a coordination problem between them. It is doable if the cut is honest.

What ships:

Two onboarding flows, one per user type
Listings or profiles for the supply side
Search or browse for the demand side
A booking, request, or messaging flow that connects them
Stripe Connect for split payments, one fee structure
Admin tools so you can moderate content and resolve disputes manually
Email notifications for the key handoffs between the two sides

What does not ship:

Reviews and ratings
Multi-currency, multi-region
Automated dispute resolution
Refund and payout flows beyond the basics
Search filters beyond category and location

Real example shape: a marketplace for freelance designers. Designers create profiles, clients browse and book, payment splits between platform and designer, admin can step in if a booking goes wrong.

If your marketplace needs reviews on day one, it is not a 4-week project. That is fine. You move to a six-week Web App Build.

##Shape 3: Internal operations tool

A product that replaces a spreadsheet, a Notion database, or a manual process for an internal team.

This is the easiest shape to ship in four weeks because there is no growth funnel, no payment flow, and only one user type that you already understand.

What ships:

Auth with roles (admin, editor, viewer)
CRUD for the records that matter (clients, projects, orders, whatever your team tracks)
CSV import for the data already in your spreadsheets
CSV export so the data is never trapped
A reporting or summary view for the team lead
Email notifications when key records change
Deploy to your own infrastructure

What does not ship:

Public-facing pages
A mobile app (mobile web works fine for internal use)
Integrations with five other tools (one, maybe two, integration on day one)
A permissions matrix beyond three roles
Custom workflows per user

Real example shape: a project tracker for an agency. Each project has clients, deliverables, deadlines, status, and assigned team members. Admin sees the queue, editors update their projects, viewers see read-only.

##How to tell if your idea fits

Five questions to ask yourself before you commit to four weeks.

1. Can you describe what users do in three sentences? If you cannot, the scope is too big. Cut until you can.

2. Is there exactly one workflow that matters most? If there are three, pick one for the MVP and put the others in v2.

3. Is there one user type that pays you? If two user types pay differently, that is two products.

4. Have you said the words "and also" more than twice while describing the scope? Each "and also" adds a week.

5. Does the idea fit in the 4-week skeleton above? If yes, you are ready. If no, you are scoping a 6-week to 12-week project, which is a Web App Build instead of an MVP Build.

##What four weeks actually feels like

Roughly:

Day 1. Kickoff call. Repo set up in your GitHub. First deploy goes live with a placeholder page.
Week 1. Auth and the database schema. The skeleton of your main workflow. First weekly demo at the end of the week.
Week 2. The core workflow gets built end to end. You start clicking through real flows. Feedback shapes week 3.
Week 3. Payments if in scope, email notifications, admin views, polish. Second-to-last demo.
Week 4. Hardening, last polish pass, launch on your domain, handover of code and accounts.

You see something working every week. By week 4, you are clicking through a real product, not a prototype.

##When to skip the 4-week sprint

Some projects should not be 4-week MVPs. Be honest about which one yours is.

Skip the 4-week MVP if:

You already have product-market fit and need a production v1, not a learning vehicle
You have compliance requirements (SOC 2, HIPAA, GDPR data residency) from day one
Your core workflow depends on hardware, native mobile, or specialised integrations
Two user types both need full apps on launch day
Your domain has so much state and so many edge cases that the skeleton above will not hold

In those cases, a Web App Build starting at $25,000 over six weeks or more is the right tool.

##How ZeCreator does it

We charge $9,500 for an MVP Build, fixed. Four weeks. Weekly working demos. You own the code, deployed to your accounts. If your scope is bigger than the skeleton above, we tell you on the discovery call and quote a Web App Build instead.

If you want to talk through which shape your idea fits, book a 15 minute call. We will tell you what we would cut, what we would build, and what it would cost, in writing, within 48 hours.