Key facts
| Who it suits | Brokerages and channel partners with 3–40 agents, plus small developers selling their own inventory |
|---|---|
| First Build | Leads, site visits, follow-ups, inventory sheet and commission ledger |
| Typical range | ₹1.7L–₹2.5L with WhatsApp alerts and one export |
| Timeline | 3–4 weeks for a first version |
| Ownership | Code, hosting and data belong to you; no per-seat fees |
How does a broker's day actually run today?
Leads arrive from portals, Instagram forms, hoardings and referrals. They land in a phone, a portal login and a WhatsApp group. Someone copies them to a Google Sheet, usually at night, and some never get copied.
The site visit is where deals are won, and it is also where the record is thinnest. Who took the client, which flat did they see, what did they say about the price? That lives in a voice note or in an agent's memory. When the agent leaves, the history leaves with them.
Then there is money. Brokerage is split between agents, sometimes with a channel partner, often in instalments tied to the builder's payment schedule. The ledger is a sheet that one person understands.
Where do spreadsheets and WhatsApp groups break for brokers?
- Duplicate leads. Two agents call the same buyer, and the buyer notices.
- No follow-up trail. Nobody can see which leads went quiet after the first visit.
- Inventory drift. A unit is shown as available after it was blocked in a group message.
- Agent exit. Contacts and notes sit in personal phones.
- Commission disputes. The split was agreed in chat, and the sheet says something different.
These are tracking problems, not marketing problems. A shared system fixes them without changing how your agents sell.
What would a first Build contain?
A first version is one tool with a few roles: owner, team lead, agent, and an accounts view. The scope we would write for a broker usually has these parts:
- Lead capture from a form and a manual entry screen, with a duplicate check on phone number.
- Assignment rules: round-robin, by project, or picked by the team lead.
- Site-visit log: date, who attended, units shown, client reaction, photos if needed.
- Follow-up reminders per lead, sent to the agent on WhatsApp or email.
- A simple inventory list with status: available, held, sold.
- A commission ledger: deal value, rate, split, amount received, amount owed.
- An owner dashboard: leads by source, visits done, deals closed, stuck leads.
Data import from your existing sheet is part of the scope, because messy contact data is the most common source of delays.
What should a broker not build first?
Do not start with a public listing portal. Competing with the large portals is a marketing problem, and software will not solve it. Do not build a buyer-facing mobile app before agents use an internal tool daily. Skip virtual tours, AI valuation and automated legal documents in version one.
Property registration and RERA compliance are rules your advocate and the authority define. Software can store your documents and reminders, but it does not decide what is compliant. If you want to show RERA details on a page, you enter the numbers yourself and stay responsible for them.
What does it cost, and when does it grow?
| Scope | What it covers | Price | Time |
|---|---|---|---|
| Build: tracker | Leads, visits, reminders, inventory list, owner dashboard | ₹1.7L–₹2.5L | 3–4 weeks |
| Build: with commissions | Adds the commission ledger, partner view and statements | ₹1.5L–3.5L | 3–4 weeks |
| Platform | Several projects, developer inventory, partner portal, accounting export | ₹3.5L–8L | 5–8 weeks, then phases |
Hosting is a small monthly cost paid to the cloud provider. For a general breakdown, read app development cost in India or try the cost estimator.
Should you buy a real estate CRM instead?
If you are a team of three with standard needs, an off-the-shelf CRM is cheaper and fine. Custom starts to make sense when your commission rules are unusual, when you resell the same inventory across partners, or when you are paying per seat for features agents never open. Custom CRM versus Zoho compares the two routes fairly.
The process is on how we build: a written scope and fixed price first, a prototype in week one, then live previews. One person is accountable for the project, with AI agents helping on code and tests.
Frequently asked questions
Can agents use it from their phones?
Yes. It is built to work in a phone browser, which suits agents who are on site most of the day.
Can it pull leads from Meta or portal forms?
Often yes, through the form's export or webhook. Each source is scoped and priced separately.
Can it send WhatsApp reminders?
Yes, through an approved WhatsApp provider. Message charges go to that provider. See the WhatsApp automation guide.
Do you handle RERA or legal paperwork?
No. We build tracking and storage. Compliance decisions stay with you and your advocate.
What if my agents refuse to use it?
Then the scope is wrong. We keep the entry screens short and test the prototype with two of your agents before building.