Analysis
MVP launch check
Your prototype works in the demo. We review one user journey and identify what is missing before your next launch.
Before the first test of your prototype
This time, you are not guiding the demo.
Someone opens your prototype for the first time, without prepared data or your explanations. We review the main journey and identify tasks that should be finished before this test starts.
View scope and price See the exampleIn your demo, the first project already exists.
You know which button comes next. A new participant first sees an empty overview. Can they create the first project without your explanation? Check that journey before adding more features.
The MVP launch check is a professional preliminary review of one central user journey. We agree the test start and record relevant findings. A study with recruited participants is not automatically included.
You explain every step while demonstrating.
Record the hints you give verbally. If the interface lacks them, that is a specific location for the preliminary review.
Everything works with your sample data.
A fresh account, empty list or incomplete record shows a different state from the prepared demo.
Turn a demo into a test task.
These details help limit the check to your next start:
Who will try it?
An invited test group or new customers? Supported or independent? Describe the intended use.
What should be achieved at the end?
Describe the task from the person's perspective, such as storing a file and finding it later.
What exists at the start?
An empty account, an import or existing data changes the journey. Define the starting state.
What is already known?
List existing limitations and your preferred date. The work window is agreed before commissioning.
Fictional sample project
One task. One fresh account.
Test card · first run
The task
Create a project, attach a file and find it again after reopening.
The starting state
New account. No projects or sample files. The person has not used the application before.
Findings from the preliminary review
The empty overview offers no starting point.
Create project appears only in a submenu. The starting view needs a recognisable route to the first task.
An unsuitable file disappears without explanation.
The interface needs to explain why the file is rejected and how the person can continue.
The test task ends only when the file is found again. Export can wait; the route to the first project and feedback for a rejected file cannot.
Is the question about the first journey or the technical structure?
The MVP launch check examines your planned test start and one central user journey. If you mainly need to decide whether the architecture can be reused, choose the technology and stack review.
Analysis
Technology and stack review
Do you really need a rebuild? We review an application's structure and explain what to keep or change.
The two reviews can overlap. Agree the question first before combining them for the same project.
The test start determines what must be ready.
In a supported test session, you can explain some limitations beforehand. Independent users need that help in the interface. Describe who will try the prototype and under which conditions.
We relate findings to the described test start: what blocks the task, what can follow later and which technical questions remain? These open points appear in the findings so your team can plan for them before broader use.
MVP launch checkDoes the review fit?
Your prototype is already usable.
You are planning a specific test start and can identify the main journey. Preparation may still have gaps.
An idea alone lacks test material. If a publicly operating prototype is failing, technical repair comes first.
Ask us for adviceDoes this apply to AI or no-code prototypes too?
Yes. We need a usable prototype and a task for the planned test. Identify the tools so we can include their capabilities and limitations in preparation.
Do you organise participants?
The MVP launch check is a professional preliminary review. Recruitment and a user study are not automatically included and need a separate agreement.
Do you need all my code?
We first agree the demo, journey and review boundaries. That determines required materials or limited read access. Tokens and passwords do not belong in the enquiry.
Is the prototype then cleared for public operation?
No. The findings concern the agreed journey and launch context. They do not include penetration testing, legal review or complete operational approval.
Explore the topic.
In the demo, you know every click.
A new account is empty. An entry is missing. The connection drops. These cases show whether someone can continue without your help.
All services for Startups & AI projects