An MVP is the simplest version of a product that allows a startup to test an important assumption with real users. It is not necessarily a low-quality product; it is a focused experiment designed to generate useful learning without unnecessary development.
Start by choosing one customer problem and one core outcome. List the features required to deliver that outcome, then separate essential features from improvements that can wait. Explore no-code tools, clickable prototypes, manual service delivery or a small technical build where appropriate.
Before development begins, define what success would look like. It could be users completing a task, customers agreeing to a paid pilot or a measurable reduction in time spent on a process.
Test the MVP with a small, relevant user group. Collect feedback, observe behaviour and identify what should be improved, removed or tested next. Avoid adding features simply because early users request them; check whether those requests support the core use case.