Define what you need to learn
Write down the user problem and the evidence that would justify further investment. Choose the action users must complete to demonstrate value. Remove features that do not support that test. A prototype can answer interface questions, while a working MVP is needed to observe actual use of the service.
Deliver the essentials completely
Include the backend, administration and support needed to operate the chosen journey. Keep appropriate testing, accessibility and security in the scope. Using established services can speed delivery when they fit the requirements. Document what is deliberately excluded and which assumptions would require an additional phase.
Plan the next decision
Collect feedback and measure completion, activation and repeat usage. Reserve time for defects and onboarding improvements after release. Decide whether to continue, change direction or stop based on the evidence. A successful MVP creates learning and a maintainable starting point; it does not guarantee demand or eliminate future development work.