◀ Home

​

This case study illustrates how I launched an MVP in two days to validate a hypothesis.

​

​

Company Type: Startup

Product: Mental health chatbot

Company size: < 10

Duration of engagement: 1 month

​

This case study demonstrates the following skills:

1. I first understand the goals clearly. I also understand non-goals, which draws a boundary around the goals. In this case, the purpose of the MVP was to validate market demand for an idea, not to build a stable foundation that the startup can build on top of for years to come. What's appropriate for a series-B startup is not appropriate for an early-stage startup, and I'm able to adapt and do what's needed.

2. I'm able to move fast, like launching an MVP in two days.

3. I flag risks up front, like the WhatsApp API not yet being open for general use, before building rather than after.

4. I generate multiple options, like a standalone chatbot and a Telegram bot.

5. If the startup decides to build one option in-house, I'm able to give them initial guidance and then advise when they have problems. I can work in different engagement models depending on what the client prefers.

6. I was able to help the startup conclude in a month that the entire idea of a mental health bot (whether a Telegram or standalone bot) has limited potential. The first goal of a startup is validated learning: learning that something doesn't work quickly and cheaply is a great outcome.

​​

​

This flowchart tells you how I executed this project at a high level, followed by a detailed flowchart:

​