Lead management

Lead management software for real estate teams in India.

Every enquiry from 99acres, MagicBricks, Housing, your own website, your WhatsApp number and your walk-in register lands in one pipeline — deduped by phone number, stamped with its source, assigned to a person, and visibly ageing until someone acts on it. No spreadsheet, no separate portal logins, no lead quietly dying in somebody's WhatsApp.

Get a demo See pricing

A real 20-minute walkthrough with your own projects on screen. No card, no self-serve signup — we set the workspace up with you.

A portal enquiry becomes a lead in the queue — deduped and assigned in seconds.

Capture sources: 6+Capture sources
Dedupe key: PhoneDedupe key
Pipeline views: 3Pipeline views
Leads, still fast: 10KLeads, still fast

How lead management works, start to finish

Four steps, and after the first setup call none of them need a human to remember anything.

01
Capture from everywhere
Portal enquiries, website form submissions, WhatsApp messages, missed calls and manually added walk-ins all arrive in the same queue. Nothing is retyped from a portal dashboard into a sheet.
02
Dedupe on the phone number
The same buyer enquiring on three portals is one lead with three sources, not three leads chased by three brokers. The phone number is the identity, because in India it always is.
03
Assign and age
Routing rules give the lead an owner immediately — by project, locality, language or round-robin. From that second the lead starts ageing, and an untouched lead is impossible to hide.
04
Move it through stages
New, contacted, qualified, site visit, negotiation, token, booked. Drag a card, or advance it from the phone in the car park. Every move is stamped with who and when.

Why lead leakage is the real problem, not lead volume

Ask any Indian brokerage where deals are lost and the honest answer is rarely price. It is the 48 hours after an enquiry arrives. A 99acres lead pings a shared email at 11:40pm. Someone screenshots it into a WhatsApp group. Two brokers call the same buyer the next morning, one of them at 3pm, by which point a competitor has already fixed a site visit for Saturday.

Lead management fixes that with structure rather than effort. The enquiry enters a system that knows it exists, so it cannot be forgotten. It has exactly one owner, so nobody double-calls and nobody assumes someone else has it. And it carries a visible age, so a lead sitting untouched for six hours is a number on a manager dashboard, not a story that comes out in the monthly review.

The measurable outcome teams look for is first-response time. Getting from hours to minutes is not a software feature — it is the difference between the buyer picking up because they just submitted the form and the buyer having already spoken to three others.

One owner per lead, assigned the moment it arrives
Ageing visible per lead, per broker and per source
Duplicate enquiries merge instead of splitting the pipeline
Source retained through the whole lifecycle, so ROI is knowable

Three views of the same pipeline, because three jobs need three shapes

A broker working the day wants a list they can burn through — sorted by what is due, tapped one at a time. A sales head wants a kanban board where the pipeline shape is obvious at a glance and cards can be dragged between stages. And when a team is running several projects at once, a cluster view groups the same pipeline by project, source or owner so a stalled bucket is visually obvious.

All three read from the same data, so nothing is a separate report to maintain. Drag a card on the kanban and the list reorders. Advance a lead on the phone at a site and the desktop board moves under the manager while they are looking at it.

Performance is a deliberate constraint, not an afterthought. A brokerage with ten thousand live leads still gets a first paint under 200ms, and drag-and-drop stays lag-free on a mid-range Android handset. A pipeline that stutters is a pipeline people stop opening.

What gets captured with the lead

A name and a number is not a lead. SaudaFlow records the source and campaign it came from, the project and configuration enquired about, budget and timeline once qualified, the locality preference, the assigned owner, the current stage, every call and WhatsApp exchange attached to that person, site visits with their check-in proof, and the cost sheets shared with them.

That history is why the caller ID banner can tell a broker "3BHK, Lodha Vista, ₹1.85 Cr, site visit fixed Saturday 11am, loan pre-approved" in the two seconds before they answer the phone. The context was never typed into a note — it accumulated as the deal moved.

Custom fields cover whatever your business tracks that ours does not guess: referral source name, channel partner firm, loan bank, NRI status, preferred call window. Fields are per-workspace, so your pipeline does not inherit somebody else's idea of a real estate lead.

Source, sub-source and campaign kept for the life of the lead
Budget, configuration, locality and timeline as structured fields
Calls, WhatsApp threads, site visits and cost sheets attached automatically
Custom fields per workspace, no developer needed

Compliance, residency and who can read your pipeline

Your leads are personal data under the Digital Personal Data Protection Act 2023, and a CRM is where most of that data sits. SaudaFlow stores it encrypted at rest on Mumbai infrastructure — application, database and file storage in the same region — so residency is a fact about the deployment rather than a promise in a PDF.

Access is audited by default. Every staff read of tenant data writes an audit row you can read, and a data-principal rights request (access, correction, erasure) is a workflow inside the product rather than an email to support that gets forgotten. Consent and unsubscribe state travels with the lead, so a buyer who opted out of marketing does not get a campaign message from a keen new joiner.

Works with the rest of SaudaFlow

WhatsApp CRMThe channel most of these leads arrive on, and the one they will answer.Read more Caller ID & call trackingThe lead named and summarised before the phone stops ringing.Read more Automations & workflowsRouting rules, follow-up cadence and stalled-deal escalation.Read more

Frequently asked questions

Does SaudaFlow integrate with 99acres and MagicBricks?

Yes — enquiries from the major Indian portals flow into the pipeline with their source retained. Portals rate-limit at peak hours, particularly weekday evenings, so ingestion backs off and retries rather than dropping enquiries, and duplicates across portals merge on the phone number. Note the reverse direction — pushing your inventory out as portal listings — is not built yet and is on the roadmap.

What happens when the same buyer enquires from three different portals?

They stay one lead. The phone number is the dedupe key, so the second and third enquiries attach as additional sources on the existing lead rather than creating new cards. Your team calls once, and your source report still credits every portal that touched that buyer.

Can I import my existing leads from Excel?

Yes. Upload the sheet, map your columns to SaudaFlow fields, and review the dedupe preview before committing. Rows that clash with an existing phone number are shown as merges rather than silently overwriting anything, and the whole import is reversible in one action if the mapping was wrong.

How many leads can one workspace hold before it slows down?

The pipeline is built and measured against ten thousand live leads with a p95 first paint under 200 milliseconds, and the underlying database is isolated per workspace so a large tenant cannot slow down a small one. In practice, brokerages hit team-process limits long before they hit the software.

See your own leads in the pipeline.

Bring a CSV of last month's enquiries to the call. We will load them, dedupe them, and show you exactly how many were never followed up.