Core idea
Founders often treat an MVP as a compressed company: fewer pages, fewer features, the same ambition. That produces a thin brochure with a login button. A useful MVP is narrower. It proves that one person, in one situation, will go through a workflow because the pain of not doing it is worse.
Why it matters
If the first user is still vague, a polished interface will not tell you anything. You will learn that people can click. You will not learn whether the product should exist. The point of MVP design is evidence: use, payment, or a conversation that would not have happened without the prototype.
Practical breakdown
Name the user in a sentence they would recognize. Not a persona slide. The person who currently hacks this with email, spreadsheets, or a vendor they resent.
Pick the failure point, not the platform. Doorstep.ai was not “better maps.” It was the last 100 meters after GPS stops being useful.
Decide what stays ugly on purpose. Manual ops behind a clean front is allowed. Fake automation that cannot survive a real customer is not.
Choose the artifact that creates the evidence you need: clickable flow, lightweight build, or a staged product. The tool follows the question.
Keep the marketing site honest. If the product is a wedge, do not write category copy for a suite you have not earned.
Example or implication
Dexicon was easy to misread as another coding assistant. The product question was shared context for agents, which is a different job. An MVP that looked like a chat wrapper would have taught the wrong lesson. The design had to make the actual job visible, even if the first surface was small.
What teams should do next
Write the test before the sitemap. If you cannot say what would make you kill or continue the idea, you are not scoping an MVP. You are decorating a guess. How we run that kind of sprint is on Services. Bring the workflow, the user, and the evidence you need to Contact.
Questions
How do I turn my startup idea into an MVP?
Reduce the idea to one user, one painful workflow, and one testable outcome. A good MVP is not a smaller version of the whole company. It is the smallest product surface that proves someone cares enough to use it, pay for it, or keep discussing it. Map the customer situation, define the first wedge, sketch the product flow, and decide what can stay manual behind the scenes.
Should the MVP and the marketing site be the same project?
Only when the site has to demonstrate the product path, not just describe it. If you still need to learn whether anyone will use the workflow, do not spend the sprint polishing homepage sections. Prove the path first, then let the site report what you learned.
