Real estate agents/teams have to put their best foot forward as they are competing against big brokerage to gain clients. Having a strong online presence and a good lead capturing/management system is crucial for getting business and creating lasting brand value.
For pilot, we finalized the local WFRMLS (Utah) real estate market as our target market. In the US there are 1.5 million real estate agents, out of that there are about 10900 in the state of Utah. It serves as a good pilot market for a couple of reasons:
The goal was to build the MVP (Minimum viable product) and get some paying customers to fund further development of the product
Customer Segments:
Target Segment:
We chose Real estate agents & Small teams to focus initially. These 2 segments do not have much of an online presence, so its a big market with unmet needs.
The Problem Space
We conducted surveys and in-person interviews with many real estate agents to understand the key problems they were facing, their expecations and what they would be willing to pay for the service.
Unmet customer needs:
Finding the right product market fit by targetting the correct market, offering the right benefits and getting the pricing correct was key to our success.
Benefits classification:
Must have :
Performance Benefits:
Delighters:
We were unsure of the exact pricing model, but decided that we will test different models when we launch and test the market
Pricing models
The Solution Space
Here are few white boarding sessions
We identified end users for our product
End Users:
We also captured the interal staff users for our product
Clientopoly Internal Users/Staff
MVP Feature Set:
I used balsamiq to create some low fidelity prototypes for the main screens.
We adopted the SCRUM framework for developing the product
We decided that a standard 2 week sprint would be a good starting point for our team. We made a rough estimate that it will take eight 2-week sprints to get all MVP items “Done”. The initial sprint was very difficult. We faced a lot of challenges related to setting up the IDE environment for development, setting up dev, test, production servers, creating a workflow for release, discussing Quality requirements and standards. There were many issues related to misunderstanding about specific sprint backlog item, and we resolved this by increasing communication and we collectively worked on refining the product backlog to provide more details. The sprint retrospectives were really useful to discuss the inefficiencies in process and to refine the “Definition of Done”, so that everyone in the team were on the same page. The team progressively got better at product backlog item effort estimation in each sprint planning session.
Before we launched the product, it was important to understand which metrics were needed to be captured, and logged, so that we can improve the product and determine if we had success.
Acquisition:
Activation:
Engagement:
Revenue: