CRM Software for Real Estate Developers: Launch Campaign to Site Visit to Booking

CRM software for real estate developers should run presales: capture every launch enquiry from Meta, Google, the website, IVR numbers and channel partners, route it to the right project team within minutes, force a callback date on every live lead, book site visits as appointments, and show cost per qualified lead and site visits by campaign. Unit inventory, payment schedules and demand letters belong in your ERP.

This guide is for sales and presales heads at builders running one to ten projects with in-house telecallers and a channel partner network.

Presales CRM vs post-sales ERP: what CRM software for real estate developers should cover

Search for a CRM for builders and you will find two different products sold under one name. One handles the enquiry until the booking amount is paid. The other handles the unit and the customer after that. It doesn't help that in many developer offices "the CRM team" means the post-sales customer-relations desk.

Presales software is judged on how many paid enquiries become site visits. Post-sales software is judged on collections and paperwork.

The record crosses over at the booking, so decide what the CRM passes across (name, phone, project, unit, channel partner, source). If one vendor offers both halves, ask to see the presales half live on a test lead from your own Meta form. A weak presales setup wastes ad money every day of a launch, long before a demand letter is due.

Project-wise lead routing with branches, teams and source rules

A developer with three projects has three sales problems, not one. The telecaller who knows the Kharadi 2 BHK price sheet by heart should not be pitching plots in Hinjewadi. So route on project first, then share the load inside each project's team.

A routing plan for a hypothetical Pune developer:

Give every campaign, form and IVR number its own source named after the project, and every rule a fallback person, so no lead waits through a launch weekend because one telecaller is on leave.

In atomcrm.ai, each project site can be a branch (location) with its own team. Assignment rules can be limited to a branch or a team, run in priority order, respect a daily cap per person and name a fallback person. A source can also skip the rules and send its leads straight to one person, a team or a branch, and leads that match no rule stay unassigned and visible. See how the lead distribution rules work, and the help docs on teams and locations for the setup screens.

One caution: what each role can see is set as own leads, team or everything, not by branch. If the Kharadi head should see only Kharadi leads, make Kharadi a team as well as a branch.

Direct, channel partner and walk-in leads without ownership fights

Every developer with a CP network has had this argument. A buyer fills your Meta form in March, a channel partner registers the same buyer in April, and the buyer walks into the sales office in May. Who earns the brokerage?

Software cannot settle that. A written policy can, and the CRM's job is to make the facts visible so the policy is easy to apply. A starting template, with numbers you should change:

Channel partner ownership policy (template)

1. A CP registration is valid for 60 days from the date it reaches the CRM.
2. If the buyer is already an active direct lead (a call or WhatsApp
   reply logged in the last 30 days), the lead stays direct.
3. A walk-in registered by a CP within the validity period is a CP lead.
   A walk-in with no record is direct.
4. Disputes go to the presales head, who decides within 2 working
   days using the lead's timeline and logs the decision as a comment.

For this to hold, a registration or walk-in for an existing buyer must land on the existing lead, not create a second one that another person starts calling.

atomcrm.ai records it as a repeat enquiry, matched on the last 10 digits of the phone number or on the email, for leads typed in by staff and leads that arrive through capture. A CSV import skips that check, so clean a partner's spreadsheet first. Give partners a registration form (a Google Form or a form on your site) that posts straight into the CRM, and add custom fields for the CP firm, its RERA registration number and the registration date, shown only when Lead type is Channel partner. The audit trail records every change, including a changed source. Our guide to CRM for real estate channel partners covers the partner's side.

Site visits as appointments: scheduled, confirmed, attended, no-show

The site visit is the step that matters most between enquiry and booking. Treat it as an appointment with states, not a line in a comment box, and you can count how many were booked, how many turned up and what happened to the rest.

A stage set that forces the next step at every point:

The appointment moves through its own states: scheduled when booked, confirmed after the reminder call the day before, then attended, no-show or cancelled. The site office checks the calendar view each morning.

A confirmation template to submit to Meta for approval, so it can go out even when the buyer has not messaged you in the last 24 hours:

Hi {{1}}, your site visit to {{2}} is confirmed for {{3}}.
{{4}} from our sales team will meet you at the sales office.
Location: {{5}}
Reply 1 to confirm or 2 to change the time.

The telecaller sends it from the lead's chat in the WhatsApp inbox, filling in the project, the visit time and the name of the person who will meet the buyer.

Call no-shows the same day, while the buyer still remembers why they booked. Mark the appointment no-show, offer two new slots and book the new visit. If the buyer won't commit, move the lead back to Requirement taken, which demands a callback date, so it cannot sit quietly in Site visit scheduled.

Judging launch campaigns by cost per qualified lead, not cost per lead

Launch campaigns are usually judged on cost per lead because the ad dashboards show it first. It is also the number most likely to mislead you.

A worked example, entirely hypothetical: a Bengaluru developer launching a tower on Sarjapur Road runs three campaigns for a month.

Campaign A looks cheapest on the ad dashboard and costs two and a half times as much per booking as Campaign B.

• Define "qualified" in writing before the launch, for example reachable, budget within range, configuration available, willing to visit within 30 days. Telecallers mark it by moving the stage, not in a comment.
• Review cost per qualified lead weekly and cost per site visit fortnightly. Bookings are too few to judge a campaign in its first weeks.
• Give each campaign its own source or form, or the numbers cannot be split.

In atomcrm.ai, Ads Intelligence syncs Meta ad spend and grades every ad by effective cost per qualified lead against a target you set (winner, scalable, watch, learning or loser), with breakdowns by age, gender, region, placement and time of day. For Google Search, work from the source, UTM tags and gclid stored on each lead, with spend from your Google Ads account. See how the Meta lead ads sync and Ads Intelligence work.

Sending site-visit and booking signals back to Meta and Google Ads

Left alone, Meta and Google optimise toward the event you told them to count, usually a form submission, so they find more people who submit forms. Send back which leads became site visits and bookings, and they can learn from buyers who actually came to the site.

Before switching it on:

• Send the stage that proves a visit happened. Move a lead to Site visit done only after the appointment is marked attended.
• One launch may produce too few bookings for an ad platform to learn much from, so the site visit is often the more useful signal. Send both.
• For Google, only leads carrying a Google click ID (gclid) can be uploaded. That needs auto-tagging on and a landing page that passes the gclid into a hidden form field.
• Test with one lead before a launch weekend and check that the event shows up in Meta Events Manager and in Google Ads.

atomcrm.ai maps the stages you choose to Conversions API events (nothing is mapped by default), sends each event once per lead and hashes customer data. For Google Ads, leads with a gclid are uploaded when they reach the stages you pick, so Smart Bidding learns which clicks became visits and bookings.

How a developer's presales team runs on atomcrm.ai

Take the hypothetical Pune developer again: three projects, eight telecallers, four closing managers who take site visits, a two-person CP desk and a sales head.

1. Branches, teams and roles. One branch per project site, one team per project's presales desk, plus the CP desk. Telecallers see their own leads, project heads their team, the sales head everything.
2. Sources. Log in with Facebook, pick the ad account and page, map each project's lead form to fields, a source, a starting stage and an owner, and backfill up to 90 days of missed leads. Website forms each get their own webhook URL, with UTM tags and gclid stored on the lead.
3. Assignment. The rules from the routing table, plus working hours for distribution and a first-response time limit.
4. Stages and fields. The stage table above, statuses for why a lead is stuck ("Not responding", "Budget issue"), and fields for project, configuration, budget and CP details on Quick Update, the panel a telecaller fills after every call.
5. Calls and WhatsApp. Telecallers install Call Pro on Android phones, so every call is logged on the lead with outcome, duration and recording. The WhatsApp inbox runs on your business number through Meta's WhatsApp Cloud API or Gupshup, each chat linked to its lead.
6. Automations. A lead moving to Site visit scheduled can send a WhatsApp template, and a missed callback can create a task or reassign the lead.
7. Reports. Email the conversion funnel and leads-by-source reports to the directors daily, and read the team leaderboard for calls, connect rate and follow-up adherence.

Telecallers start the day from "Who to call next" and the callback queue, with a reminder 15 minutes before each callback. The real estate industry page shows the full flow from portal lead to site visit.

Where it fits: developers whose presales runs on calls and WhatsApp, who want lead capture, routing, site visits and ad feedback in one place, priced per workspace in rupees with users included and data stored in India.

Where it does not: there is no unit inventory, payment schedule or demand letter module, no native app for iPhone (Call Pro is Android only) and no dialer that rings the next number on its own. Cost per site visit is worked out from a report of site visits by source and your ad spend; Ads Intelligence grades Meta ads by cost per qualified lead. Keep post-sales in your ERP; outbound webhooks on lead events and a REST API can pass booked leads across.

Frequently asked questions

What is the difference between a real estate CRM and a real estate ERP?

A CRM runs presales: capturing enquiries, assigning them, calls, WhatsApp, callbacks and site visits up to the booking. An ERP runs the unit and the money after that: inventory, allotment, payment schedules, demand letters and possession. Some vendors sell both in one suite. Judge each half on its own, and decide which system owns the buyer from the day of booking.

Can one CRM handle leads for several projects?

Yes, if every lead carries its project from the moment it arrives, through a source named after the project or a Project field. Route each project's leads to its own team with a fallback person. Before you buy, check that reports split leads, site visits and bookings by project.

How should a builder handle channel partner leads in a CRM?

Write the ownership policy first: how long a registration stays valid, what happens when the buyer is already a direct lead, and who settles disputes. Then give partners a registration form that posts into the CRM, check that repeat enquiries join the existing lead, and store the partner firm and registration date on each lead.

How much does CRM software for real estate developers cost?

It depends on the pricing model: per user per month, per workspace with users included, or per lead, which can jump in a launch month. atomcrm.ai charges per workspace (Starter includes 3 users, Growth 15, Scale 100) with GST invoices; current rates are on the pricing page. Our real estate CRM price guide has a cost sheet for 3, 10 and 25-person teams.

What to test in a 14-day trial

Run one live project through the trial:

1. Connect its Meta form, backfill recent leads and time how fast a test lead reaches a telecaller.
2. Enter a CP registration for an existing lead and check it lands as a repeat enquiry.
3. Try to move a lead to Site visit scheduled without an appointment.
4. Map Site visit done to a Conversions API event and send one test lead through.

You can start a 14-day trial for ₹5, which sets up a mandate so your chosen plan is debited after the trial, or book a 20-minute demo. Setup can use your own projects, lead sources and stages from day one.