The MVP Process


Research and customer development

Before we begin writing a line of code, the entire team along with the founders spend 2 weeks in researching more about the industry, the problem the founder is trying to solve and the most optimal way technology can help in solving the problem.

Some of the major points that are touched upon during this process are:

  • Is there is a real problem that is the founder is solving?
  • Is there a real need for the solution that we are planning to come up with?
  • Is there a possibility to create a product with more value than the current solutions in the market?
  • What is the primary value proposition of the product?
  • Breakdown the features - and at each step asking if it is a “must-have” feature for the MVP


Product Documentation & Wire Framing

Ideally, after we’ve done the market research & customer deepdive we would have found an interesting need that is underserved by the existing players.
In this stage we go into more depth into the solution for the a need, start documenting the product functionality that will create value for the user and begin creating user stories in our internal project management tool, that would also be visible to the clients.

Post that we start creating the wireframes for the core flows and functionality of the product. We start off with the initial wireframes - either through sketches or a wireframing tool . There is going to be a lot of focus on this stage of process, as it is a faster canvas to decide the product flow and ensure the right expectations about the product are set.

Once the wireframes and flow is finalized, we begin work on the UI of the screens. After we have the UI designed, we usually create an interactive prototype of the product, so that we have a clear feel on how the user will experience the product.


Product Development

Post this step, both the founders, and our team would have clear clarity on the exact product features that would go into the MVP launch. Post this it would be over to the development team.

We follow an agile model of delivery with the entire 3 month development schedule broken down into 2-week sprints. The sprints are subdivided into tasks in our internal project management tool. The tasks are managed and updated on a daily basis. The client can take a look at the tool anytime to know the live progress of any of the sptints

There are weekly meetings with the clients and the entire team, where we also discuss the progress on the project, share the latest status of the product - where the clients can also view it. These weekly meetings also give us perspective to see if we are overschedule either due to scope creep or complexity in development, and help take immediate corrective action to ensure we are on-course. There would also be a 2-week testing included in the product development phase before the launch.


Launch, Post Development Support & Scaling

Post launch, there would be a 1-month support period - where we work on any fixes, while the founder simultaneously reaches out to the early adopters to gain feedback on the product, and better understand the receptance of the product among its target customers

The founder simultaneously works on collecting feedback on newer features and enhancements that would be required to roll out the product on a much larger scale. At the end of the 1-month post launch there would be a discussion with the founder on feedback collected, whether the core value proposition has been adopted by the customers, and if there is a need to scale further.