From Idea to MVP: PropTech Solution for Real-estate problem in Germany

Client Information & Background

MietMatcher is created and funded by three serial entrepreneurs and visionaries who recognized all the challenges and opportunities on the German rental market and tried to provide an innovative solution for the problem.

Client approached us with the idea on how to solve one of the most demanding issues in the property domain in Germany – fast and easy renting of the apartments without the agent as middle-man in the process.

Client had no technical experience and no idea on which technology to build the MVP.

Challenge

Here we can find the problem with a lot of empty properties that are hard to be accessed or visited because of their attractiveness for the rental agents. Some of them are too far from the current location of the agents, some properties have low commissions and the list goes on.

The challenge on the German rental market is huge. We have a lot of companies that are renting properties which are very depending from the rental agents and their availability.

This is why we need digitalization and simplifying the whole process of scheduling meetings and visiting the properties by the potential new renters.

Approach & Solution

mietMatcher User Journey

The solution is how to avoid the involvement of the agent in the whole process. That’s why we created the mietMatcher app. Rental Companies can offer the current tenant to be their agent for a certain commission. Then the current tenant job is to provide an update small amount of data about the property and to set time slots when he is available for visits.

We delivered the MVP for MietMatcher in 6 steps process:

  • Gathering of Product requirements by using User story mapping
  • We created User flow diagrams and confirmed with the Client
  • Designing non functional Demo in Sketch and presenting in MarvelApp
  • Fixed-Price / Fixed-Time Estimation for MVP Development
  • Development phase with weekly update to the client
  • Delivery of the Product and Final Testing

Step 1: User story mapping

We approached the problem with 1 day workshop where we used the methodology called User Story Mapping to map the ideas of our Client.

On this workshop we defined all the users and their activities needed for the MVP. This is important phase since it is bringing us with our clients in the same level of thinking and understanding the end users and how they will use the product.

Furthermore, it also helped us to split the deliverables in phases and with that to build sequential development, testing and delivery of the MVP project.

Step 2: User Flow definition & State Diagram

After we have all the activities that Users want to have in the Product, the next step is to define the User Flows.

Furthermore, it also helped us to split the deliverables in phases and with that to build sequential development, testing and delivery of the MVP project.

Users flows are important because of 2 reasons:

  • Representation of Logical sequence of user flow
  • Aligning with the Client on the logic for each of the user types in the system

MietMatcher team loved the User Flow Diagrams since they proved that we are completely aligned with their idea of the flow and with all the possible details and edge cases that could happen in the MVP.

After User Flow Diagram, we also defined State Diagram where we took the Data Subject of this project – Property and we divided the Property Data into multiple steps according to the User activities.

The Step Diagram helped us to define each state and according actions that were triggered by the state change. In state machines type of thinking, this is important both for the Product Team and for our Client to spot where and how the communication with the users and with the Backoffice people will be organized.

Step 3: Non-functional Demo with Sketch and Marvel

MietMatcher team loved the User Flow Diagrams since they proved that we are completely aligned with their idea of the flow and with all the possible details and edge cases that could happen in the MVP.

Once we know what user wants, it is time to get something visible.

For that purpose, our UI/UX team created clickable but non functional DEMO with Sketch and Marvel with enough details so our Client can start doing user testing and to present it to potential investors.

Step 4: Fixed-Price / Fixed-Time estimation

Once we know exactly what our clients want to build and it is already visible in the Non functional DEMO or Mockups, we provide final estimation on fixed-price/fixed-time (FP-FT) model. This FP-FT model gives full trust and reduces the risk for our clients for the MVP development.

The estimation is done in number of man/days or man/hours and is supported by Gantt Chart where each Client can see the priority of the modules and features and their timeline of delivery.

Step 5: Development phase with weekly update to the client

As soon we got into development mode, we already had the technical architecture and product specification prepared as part of Step 1-5. That gave our Product Team easier task to organize the sprints and to move complete into Agile Scrum process regardless of the fixed-price and fixed-time business model.

As we were approaching the Delivery state, we were informing our Client with the last miles of our delivery in outlined Gantt Chart.



Step 6: Delivery of the Product and Final Testing

After the complete phase of Development was done, our Client was given access to the final product with complete handover documentation.

In this way, the Client can take the development in-house or can continue developing the next phases with further collaboration plans that we offer.

Conclusion

Building MVP is a transparent multi-step process that enables the Clients to get what they want in a fixed-time and fixed-price way.