Free expert review. Get UX insights for your SaaS. Book a Free 30-minute review
Free expert review. Get UX insights for your SaaS. Book a Free 30-minute review

How to Build and Validate an MVP in Two Weeks

How we helped InCalendar validate their product idea, get pre-orders, and prepare for fundraising, all before writing a single line of code

Giustino Borzacchiello
Giustino Borzacchiello
Mar 20, 2026
Hourglass with gear representing fast MVP building and validation

Context

“Helping professionals take care of their clients, without worrying about appointments.”: this is the mission of Incalendar, a small Milanese startup that contacted us to follow them in the validation phase of their idea.

They didn’t want to build yet another product that was not useful to its users.

The idea was born from the analysis of the significant problems that professionals face:

An ambitious idea to be validated with a Design Sprint

The concept behind InCalendar is ambitious: an AI-driven chatbot to make and manage appointments, with a built-in chat and reminders to maintain a good relationship with customers and the ability to create a broadcast marketing channel. Integrated into the app for promotions and upsells.

A sprint design is a perfect tool to validate innovative product ideas where there is high market risk.

Working closely with the two founders, we started by framing the idea using the Lean Canvas to create the first business hypothesis to be validated.

Later, given the breadth of the solution, we chose the creation of appointments, which is the fundamental part of the app, as the first part to validate.

We were interested in understanding professionals’ reactions in front of such an innovative approach compared to the usual paper plan, so we decided to approach the validation with guerrilla user testing sessions.

The idea was simple: let potential customers experience a realistic experience of using the app at the lowest possible cost.

The tools decided for these user testing sessions were

A landing page for SaaS: benefits, not features.

The landing page of a SaaS product must be considered integral to the product experience: the promises made on this page must then be kept by the application.

We then brainstormed the various messages on the landing page. At the same time, part of our team took care of the wireframing and the design proposal.

Once the brainstorming was done, through dot-voting, we chose the messages that looked most promising.

And we then integrated them into the final landing page, which also incorporated branding and logo created ad hoc to make it as realistic as possible.

An advanced interactive prototype

The second tool for our user testing sessions was a realistic interactive prototype.

It was crucial to the experiment’s success that the experience is as immersive as possible to seem real.

Together with the founders, we defined the boundaries of testing. We created the first navigable prototype that could be installed on a smartphone to look like a real app.

The interviews

Having prepared the landing page and the prototype, we accompanied the founders for the first interviews. We had previously designed a script to follow.

The interview was divided into two parts: the first involved navigating the landing page to retrieve the message that was being transmitted.

This allowed us to iterate on the page copy and focus on some benefits of the app rather than others.

The second part of the interview instead was completing a task (the only one possible on the prototype): adding an appointment for the following Tuesday.

All accepted the conversational interface, but the excellent work was confirmed by the purchase / pre-order request of two out of 10 respondents and the attempt of 90% of the interviewees to go outside the perimeter of the prototype and experiment with other features of the app.

Towards fundraising

To support the team of founders, we have collected all the results of the interviews and analyzes them in an interactive report that can be easily consulted and summarized all the fundamental messages in a pitch deck that the team will then use to raise funds necessary for the development of the already validated product.

Frequently Asked Questions

How long does a Design Sprint take?
A standard Design Sprint runs five days, but some teams compress it into three or four. The key is having dedicated time with the right people in the room, not stretching it across weeks of part-time work.
Do I need a working product to validate my idea?
No. A high-fidelity prototype built in a design tool can feel real enough to test with users. The goal is to simulate the core experience, not build the actual technology behind it.
How many users should I test with?
Research shows that 5 users reveal about 85% of usability problems. For broader validation like InCalendar's, 8-10 users give you enough signal to spot patterns and make confident decisions.
What if my validation results are mixed?
Mixed results are still valuable. They tell you which parts of your concept work and which need rethinking. The worst outcome isn't a mixed signal, it's building for months without any signal at all.
How much does MVP validation cost compared to building the full product?
A Design Sprint with prototyping and user testing typically costs $5K-$15K. Compare that to months of development that can easily run $50K-$200K. Validation is a fraction of the cost and prevents you from building something nobody wants.
Can I run a Design Sprint without a design agency?
Yes, if you have someone on your team with facilitation experience and access to a prototyping tool. The structured process is what matters. An agency brings speed and experience, but the framework itself is open and well-documented.

Similar posts