SERVICE
Minimum viable product (MVP) design
I help define, design and build functioning MVPs for controlled testing and early learning. You get a working core experience and a clearer basis for deciding what to develop before investing in a production-ready product.
An MVP needs a focused purpose and an experience that holds together.
I help choose the first audience, define the essential journey and bring the interface and supporting product logic into a working version.
The MVPs I build are intended for controlled testing and early learning. They are not production-ready products. We agree their intended use and limits, then identify what would need further engineering and preparation before a wider launch. I can also design an MVP for your own development team to implement.
WHAT MAKES THE FIRST VERSION VIABLE
Choose one audience and one useful core outcome
Define a first version that delivers meaningful value within a manageable scope. The starting point is the task the product needs to help someone complete. We identify the first users, the circumstances in which they would need it and the outcome that would make the experience worthwhile.
I help turn that focus into an initial scope, with deliberate choices about what to leave for later. Some supporting work can remain manual during an early trial if that is appropriate to the learning goal. The important thing is that the core experience works as a whole. That gives the MVP a clearer purpose than a collection of partially implemented features.
Design the complete first experience
Bring the essential journey, supporting states and visual direction together before the build grows. People need enough context to start, complete the core task and understand the result. Depending on the product, that may involve onboarding, an account, a form, a content flow or an exchange of information between different roles.
I design those interactions alongside the states around them: missing information, an unsuccessful action, an empty screen or a result that needs editing. We establish suitable visual foundations and consider accessibility as part of the experience. The aim is a first version people can meaningfully try, with enough coherence to make their feedback useful.
Build a functioning version within an agreed scope
Turn the design into working behaviour for a focused trial or early product investigation. I can build the MVP's agreed core experience, including suitable data handling, integrations or AI behaviour where the project calls for them.
Decisions about technology follow the purpose of the trial, the capabilities being investigated and the likely next steps.
We keep the implementation scope explicit and identify any simulated or manually supported parts of the experience. I test the agreed journeys and document what the build is intended to support. If your developers are handling implementation, I can instead provide the product design, priorities and interaction guidance needed to move the work into their environment.
Learn from first use and plan what comes next
Use a controlled trial to improve the proposition and understand the work needed for a later production product. Before people try the MVP, we agree what we want to learn and which observations would affect the next decision.
Feedback, task completion and appropriate usage signals can help reveal whether the experience is useful, where it breaks down and what remains unclear.
We then prioritise improvements and identify the requirements for continuing. A wider production launch needs further work on reliability, security, performance and operation appropriate to the product. The MVP gives that conversation something concrete to build on, alongside evidence from the trial and a clearer view of which investment would be justified.
CASE STUDY
Where should we start?
See contact optionsYour message is on its way. I’ll reply to .
It didn’t go through. Copy your message and send it tohello@mareksevcik.com.