"MVP in a week" sounds like a slogan, but it works when the idea is narrow. The trick is not coding faster. It is deciding, early and ruthlessly, what you will not build.
Before you start: one user, one problem
Write one sentence: "[Type of person] can [do one thing] without [the current pain]." For example: "A PG owner can see who has not paid rent without opening a notebook." If you need the word "and" to describe it, you have two products. Pick one.
The plan, day by day
Day 1: Define and sketch
Write the sentence above. List every feature you can think of, then circle the one flow a user must complete to get value. Sketch two or three screens on paper. Do not open any design tool yet.
Day 2: Cut hard
Sort features into "must", "nice" and "later". Only "must" ships. Login, settings, profiles and notifications usually belong in "later" unless the test depends on them. A good first version often has just two or three screens.
Days 3 to 5: Build the core flow
Build the one flow end to end, even if it looks plain. Use proven parts instead of inventing them: standard sign-in, an existing database service, a ready-made component library. Make it work on a real phone every day, not only at the end.
Day 6: Put it in front of five people
Not friends who will be polite. Real users with the real problem. Watch them use it without helping. Note where they hesitate. Five people reveal most of the big problems.
Day 7: Fix, ship, measure
Fix the one or two things that blocked people, then release it: a web link is fastest, Google Play takes a little longer. Decide in advance what you will measure, such as how many people finish the core flow.
What to leave out
- Custom animations and branding polish
- Admin dashboards (use a spreadsheet or the database screen at first)
- Multiple languages, unless language is the product
- Payments, unless charging is the thing you are testing
- Every "what if a user wants..." edge case
When a week is not enough
If your idea needs several user roles, payments, integrations with other systems, or heavy custom design, expect longer. That is fine. The same method applies, with a longer calendar. What matters is that the first version is small enough that you can learn from it quickly.
After the week
Look at what people actually did, not what they said. If they finish the flow and come back, build the next piece. If they do not, you have spent very little to learn that. Both outcomes are wins compared with building for six months first.
We build lean MVPs for a fixed, low cost. Read about our MVP development service or send us your idea.