On this page
Many successful Indian developers run sales on Excel and WhatsApp. A lead sheet in Google Sheets, a WhatsApp group per project, a price list in a PDF and a collections file maintained by accounts. It works when one project and a small team are involved, and it costs nothing extra.
It starts to break as the business grows. This article looks at what Excel and WhatsApp do well, where they fail, and how to tell when it is time to move to a CRM built for real estate.
01What Excel and WhatsApp do well
- Everyone already knows how to use them. No training needed.
- They are flexible. You can add a column or a group in seconds.
- WhatsApp is where buyers already are. Sharing a floor plan or a location pin is instant.
- The cost is close to zero.
For a single small project with two or three sales people, these strengths can outweigh the problems.
02Where they break
Leads go missing
Leads from Meta, portals and brokers arrive in different places. Someone copies them into a sheet once a day. Leads that arrive at night wait until morning. Leads that nobody claims are never called.
History leaves with the rep
Conversations happen on reps' personal WhatsApp. When a rep leaves, their chats, notes and relationships leave too. The next rep calls the buyer cold.
Inventory gets double-sold
A shared sheet with unit status does not stop two people from marking the same unit. Edits overwrite each other, and nobody knows who changed what.
Collections run late
Demand letters built from Word templates and a payments sheet take days to prepare for a whole tower. Receipts are typed twice, once in the CRM sheet and once in Tally.
Nobody can see the funnel
The promoter asks how many site visits last week turned into bookings, and by which source. Answering takes someone a day of spreadsheet work, so the question stops being asked.
Customer data is exposed
Buyer phone numbers, PAN copies and payment records sit in shared sheets and personal phones. Under the Digital Personal Data Protection Act, 2023, a business that decides how personal data is processed must take reasonable security safeguards to prevent breaches. Spreadsheets forwarded on WhatsApp make that hard to show.
03Signs it is time to switch
- You run more than one project, or more than five people touch leads.
- You spend more than ₹1 lakh a month on Meta or portals.
- You cannot say your median time to first call.
- A unit has been promised to two buyers in the last year.
- Demand letters for a stage take more than two days to send.
- A rep left and took buyer relationships with them.
- You need a day to prepare the quarterly RERA bookings list.
If three or more of these are true, the hidden cost of the current setup is probably larger than the cost of software.
04Side by side
| Need | Excel and WhatsApp | Real-estate CRM |
|---|---|---|
| Capture leads from Meta and portals | Manual download or copy | Automatic, with source and campaign |
| Assign and track first response | By hand, rarely measured | Rules-based, measured |
| Call and visit history | Scattered across phones | On the lead, visible to the team |
| Unit inventory | Shared sheet, no locking | Live status with holds and expiry |
| Cost sheets | Built by hand | Generated from unit and price rules |
| Discount approvals | Phone calls, no record | Request, approve, record |
| Demand letters | Word templates | Generated per stage for all units |
| Collections and ledger | Separate sheet, retyped in Tally | Single ledger with export |
| Reports | Built manually | Live by source, rep and project |
| Access control | Anyone with the link | Role-based, with audit log |
05What to look for in a real-estate CRM
- Mobile first. Sales managers work at sites and on the road. If the app is slow or awkward on a phone, they will not use it.
- Lead integrations. Direct connections to Meta lead ads and the portals you use.
- Local languages. Notes and voice capture in the languages your team speaks with buyers.
- Inventory and stacking plan. Live status, holds and price rules.
- Cost sheets and approvals. Quotes generated from price rules, with discount approval built in.
- Post-sales. Demand letters, receipts, ledger, ageing and accounting export.
- Roles and audit log. Who can see and change what, and a record of changes.
- Clear pricing. Per-user price, what is included, and what is sold as an add-on (WhatsApp messaging, post-sales modules, onboarding). Add-ons can change the total cost a lot.
Ask every vendor for the total annual cost for your team size, with all the modules you need, in writing. Compare that number, not the headline per-user price.
06A 30-day switch plan
| Week | What to do |
|---|---|
| Week 1 | Set up projects, towers and units with price rules. Import open leads from sheets with their source and last contact date. |
| Week 2 | Connect Meta and portal lead sources. Set assignment rules. Train reps on the phone app in short sessions. |
| Week 3 | Move bookings and payment history. Generate a test batch of demand letters and check them against the old file. |
| Week 4 | Switch off the old lead sheet. Run the first weekly review from CRM reports. Fix what people complain about. |
LeadOne AI is built for this switch: the LeadOne AI app for reps with voice notes in English, Hindi and Marathi, a stacking plan, approvals and collections included, at published per-user prices. See pricing.
07Questions to ask in every CRM demo
- Show me a Meta lead arriving and being assigned, end to end, live.
- Show me a sales manager logging a site visit on a phone, in Hindi or Marathi if that is how my team works.
- Show me what happens when two people try to hold the same unit.
- Generate a cost sheet for a unit with floor rise, PLC, GST and stamp duty.
- Raise demand letters for every unit in a tower after a slab is completed.
- Export a month of receipts in a format my accounts team can import into Tally.
- Show me the audit log for a price change and a discount approval.
- Give me the total annual cost for my team, with every module shown in this demo, in writing.
Ask for two reference customers with a similar number of projects and a similar team size, and call them.
