3 min read
How to launch an MVP in six weeks without cutting corners
A week-by-week plan for getting a first version in front of real customers fast, without shipping something you will have to throw away.
Most first products take too long because the team is building for every customer they might one day have. A minimum viable product is the opposite: the smallest version that lets one specific customer get one specific result, so you can learn whether anyone will pay for it.
Six weeks is enough for that if you are strict about scope and you work in small, visible steps. Here is the plan we use.
Week 1: Pick one customer and one job#
Before anything is designed, write down who the product is for and the single job it does for them. Not a list of features, one sentence.
- Who: "Physiotherapy clinics with two to five staff."
- Job: "Let patients book and pay for a session without calling."
- Result they care about: "Fewer missed calls and no-shows."
Then decide how you will know it worked. A good first goal is behavioural, like ten clinics booking a real appointment through it, not a vanity number like page views.
Week 2: Map the flow, then design it#
Sketch the shortest path from "I have this problem" to "it is solved". For a booking product that might be five screens: choose a service, pick a time, enter details, pay, get confirmation.
Design those screens properly, with real copy instead of placeholder text. Words do a lot of the work in an early product: clear labels and honest prices remove more friction than any animation.
Keep the design system small#
You do not need a full design system yet. Pick one typeface, a neutral palette with one accent colour, and a handful of components: buttons, inputs, cards. Consistency matters more than variety at this stage.
Weeks 3 to 5: Build in weekly slices#
Build the flow end to end as early as possible, even if each step is rough, then improve it in passes. A working booking flow with plain styling teaches you more than a beautiful homepage with nothing behind it.
Each week should end with something you can click on a real link:
- Week 3: the core flow works with test data.
- Week 4: real payments, emails and edge cases (cancellations, double bookings).
- Week 5: polish, speed, accessibility and analytics on every key step.
Share that link every week with the people you are building for. Their confusion is the most valuable thing you will collect.
Week 6: Launch to a small, real audience#
Launch quietly to the customers you defined in week one. Watch them use it, by call or screen share if they will let you. Fix what blocks them, not what you think looks unfinished.
A launch is not the end of building. It is the moment your guesses start getting replaced by evidence.
What to leave out (for now)#
| Tempting to add | Why it can wait |
|---|---|
| User roles and permissions | One account type covers the first customers. |
| A native mobile app | A fast, mobile-friendly web app reaches everyone on day one. |
| Complex dashboards | A weekly email or a simple table answers the first questions. |
| Integrations with every tool | Start with the one tool your customers already use most. |
The short version#
Pick one customer and one job, design the shortest path to the result, build it end to end in weekly slices, and launch to real people by week six. Everything else is easier to decide once someone is actually using what you made.
If you are planning a first version and want a second pair of eyes on the scope, book a free strategy call and we will help you find the smallest useful launch.
