If you Google “CRM for mandate desk,” you’ll find nothing. Zero. Every CRM in India — Sell.Do, LeadSquared, NoBroker, all of them — talks about “builders” and “brokers.” Nobody talks about mandate companies. Because nobody in the CRM industry knows what a mandate desk actually does.
I do. I worked alongside mandate firms for years. I’ve seen how they operate from the inside — the chaos of managing 200 units across 4 towers for a developer who expects daily updates, while coordinating with 15 CPs who all claim the same client visited “their” lead.
This post is for the 3 people in every mandate company who are currently drowning in Excel sheets and WhatsApp groups: the mandate head, the inventory manager, and the person who builds reports for the developer at midnight.
What a mandate desk actually does (for the uninitiated)
A mandate company is hired by a developer to sell their project. Unlike a regular broker who shows clients multiple projects from multiple developers, a mandate firm is dedicated to one developer’s project (sometimes 2-3).
Their job:
- Manage the project’s inventory — which units are available, held, booked, in negotiation
- Coordinate the CP network — 10-30 channel partners bring clients. The mandate desk tracks who brought whom.
- Run the sales floor — their own closers + CP closers, all working the same inventory
- Report to the developer — daily/weekly updates on leads, visits, bookings, revenue, CP performance
- Protect the developer’s interests — prevent duplicate bookings, resolve CP conflicts, manage pricing discipline
A regular broker brings a client, shows a flat, and gets paid. A mandate desk runs the entire sales operation for the project. They’re not selling — they’re managing everyone who is selling.
Why regular CRMs don’t work for mandate desks
Problem 1: They have no concept of “inventory ownership”
A mandate desk doesn’t just track leads. They track units.
Tower A, 12th floor, Flat 1201, 2 BHK, 650 sqft, east facing, ₹78 lakh. That’s not a “product” in the CRM sense. It’s a physical asset that can be:
- Available — open for sale
- Held — CP has blocked it for 24-48 hours for a specific client
- In negotiation — price discussion happening, not yet booked
- Booked — token paid, off the market
- Released — hold expired or client backed out, available again
When CP Rajesh calls and says “block 1201 for my client,” the mandate desk needs to:
- Check if 1201 is actually available (not held by another CP)
- Mark it as held with a timestamp and CP name
- Set a 48-hour auto-release if no token is received
- Notify other CPs that 1201 is no longer available
No regular CRM does this. They track leads. They don’t track physical units with hold/release mechanics.
What we built: A full inventory module — unit-level tracking with status (available/held/booked), tower, floor, facing, area, price. Hold and release with timestamps. Filter by any combination. Import from Excel. See the inventory system →
Problem 2: They can’t track “which CP brought which client”
This is the biggest headache for any mandate desk.
15 CPs are working your project. CP Rajesh brings a client. CP Meera also claims she brought the same client. The client visited twice — once with Rajesh’s closer, once with Meera’s closer. Who gets the commission?
In a regular CRM, a lead has one “source.” That’s it. There’s no concept of:
- Which CP first referred this client (first contact proof)
- Which CP’s closer conducted the site visit (GPS proof)
- Whether the client came through a portal enquiry (CP’s ad spend) or a direct walk-in
- The full timeline: who called first, who visited first, who followed up
Without this, commission disputes are settled by argument, not data. And arguments cost relationships.
I’ve watched mandate desks lose their best CPs because of unresolved commission disputes. The CP says, “If you can’t track my leads properly, I’ll take my clients to the mandate firm next door.” And they do.
What we built: CP tagging on every lead — which channel partner referred them, when, from which source. Full call log timeline with timestamps. GPS site visit proof linked to the CP’s client. When there’s a dispute, you pull up the data. Not opinions. See the proof system →
Problem 3: They don’t understand the mandate-developer reporting relationship
Every Monday morning, the developer asks: “How many leads came in last week? How many visits happened? How many are in negotiation? What’s the expected booking this month?”
A regular CRM can generate a report. But the mandate desk needs to generate a report that excludes their other projects, excludes leads from their own sources that aren’t related to this developer, and only shows activity on this developer’s units.
If you’re managing Developer A’s project and Developer B’s project with the same team, the report for Developer A must show zero leakage of Developer B’s data. One mistake — one wrong lead name appearing in Developer A’s report — and your credibility is destroyed.
What we built: Project-level filtering across every screen — leads, calls, visits, pipeline, reports. Filter by project → everything else disappears. Screenshot it, PDF it, share it. Developer sees only their data. See project-level filtering →
Problem 4: They have no “hold management” system
Here’s a scenario that happens every weekend:
- Saturday 11 AM — CP Rajesh calls: “Hold 1201 for my client, he’s coming for a visit at 3 PM”
- Saturday 12 PM — CP Meera calls: “I want 1201 for my client”
- Mandate desk: “Sorry, it’s held for another CP’s client until tomorrow”
- Saturday 3 PM — Rajesh’s client doesn’t show up
- Sunday 10 AM — Meera calls again: “Is 1201 free now?”
- Nobody remembered to release the hold. Meera’s client books 1202 instead (₹3 lakh less). Or worse — goes to a competitor project.
Hold management is a real-time, high-stakes operation. A held unit is revenue that’s locked up. If the hold isn’t converted within 48 hours, it needs to be released automatically.
No regular CRM has hold timers. No regular CRM tracks “who held what for whom and when.” It’s all done on WhatsApp groups and memory.
What we built: Unit-level hold/release/book status changes. Every status change is timestamped with who changed it. Bulk actions for multi-unit operations. The inventory screen shows the real-time state of every unit in the project.
Problem 5: They need different pipelines for pre-launch vs ready possession
A mandate desk might be selling:
- Tower A — pre-launch (EOI → Token → Allotment timeline)
- Tower B — ready possession (Visit → Negotiate → Book → Register timeline)
- Tower C — commercial (completely different cycle — committee decisions, multiple visits, legal due diligence)
Same project. Same developer. Three different sales processes. A regular CRM gives you one pipeline.
What we built: Unlimited pipelines with custom stages, transition rules, and required fields per pipeline. Tower A gets a pre-launch pipeline. Tower B gets a ready possession pipeline. Each with its own stages and follow-up cadence. See the pipeline system →
Problem 6: They can’t see the “full picture” across CPs
A mandate desk needs to answer questions like:
- Which CP has the highest visit-to-booking conversion?
- Which CP is bringing leads but not converting them? (Should I cut them?)
- Which tower is selling faster? Which floor? Which facing?
- How many units are held right now? By whom? For how long?
- What’s my projected revenue for this month based on current pipeline?
These aren’t standard CRM questions. They’re mandate-specific analytics that require inventory data + lead data + CP data + visit data all connected.
In most CRMs, you’d need to export everything to Excel and spend 3 hours building these views manually. Every week. For every developer.
What we built: Dashboard with pipeline-level stats, booking prospect scoring, project filtering. Site visits filterable by project, CP, and outcome. Call logs traceable by lead and CP source. All the data, connected, in one place.
The mandate desk’s daily workflow
Here’s what a typical day looks like — and how each step maps to what a CRM should do:
| Time | What Happens | What the CRM Should Do |
|---|---|---|
| 9:00 AM | Check overnight portal leads | Auto-captured, deduped, assigned to the right closer based on project + source |
| 9:30 AM | Review today’s site visits | Filter by today + project → see all visits, time slots, assigned closers |
| 10:00 AM | CP calls: “Hold 1403 for my client” | Check inventory → mark held → timestamp + CP name recorded |
| 11:00 AM | Developer asks for weekly numbers | Filter by project + date range → leads, calls, visits, bookings → share in 30 seconds |
| 12:00 PM | Two CPs claim same client | Pull lead timeline → see who called first, who visited first → resolve with data |
| 2:00 PM | Site visits start — 8 clients today | GPS start → mandatory notes → rating → GPS end → visit tag shared in group |
| 5:00 PM | Check: which held units didn’t convert? | Filter inventory by status = Held → check hold duration → release expired ones |
| 6:00 PM | Review Spot alerts | “4 leads with no follow-up”, “2 closers with zero calls today”, “1 stale lead in negotiation for 10 days” |
| 7:00 PM | End of day — send update to developer | Dashboard screenshot: leads received, visits completed, pipeline value, bookings |
Every row in this table is something that happens in Excel and WhatsApp today. Every row should happen inside the CRM instead.
What mandate desks look for (and don’t find) in existing CRMs
| Feature | Regular CRM | What Mandate Desks Need |
|---|---|---|
| Inventory tracking | ❌ Not available | Unit-level with tower, floor, status, hold/release |
| CP tracking | ❌ or basic “referral source” | Full CP entity with lead attribution, visit tracking, conversion rate |
| Multiple pipelines | ⚠️ 1-2 pipelines (paid add-on) | Unlimited — different for each tower/phase/product type |
| Developer reporting | ❌ Generic reports | Project-filtered, developer-specific, exportable in 30 seconds |
| Hold management | ❌ Not a concept | Unit hold/release with timestamp, CP name, auto-expire |
| Commission proof | ❌ “Not our problem” | Timestamped call logs + GPS visits = first contact proof |
| Cross-portal dedup | ⚠️ Within one source only | Across ALL sources automatically |
| Auto call detection | ⚠️ Only from CRM dialer | Any call, any time, from normal phone — auto-logged |
| Weekend visit management | ❌ Basic calendar | Project-wise scheduling, GPS proof, mandatory outcomes, visit tags |
Why this market gap exists
Mandate companies are a uniquely Indian real estate phenomenon. In the US or Europe, developers have in-house sales teams or list on MLS. The concept of a dedicated third-party sales desk managing inventory and coordinating CP networks doesn’t exist elsewhere.
That’s why global CRMs (HubSpot, Salesforce, Zoho) don’t address this. And Indian CRMs (Sell.Do, LeadSquared) built their products for the developer’s perspective — “I’m a builder, help me manage my leads.” The mandate desk perspective — “I’m running the builder’s sales operation, help me manage everything” — was never the starting point.
ClosingFox was built from the mandate/CP side of the table. That’s the difference.
If you’re running a mandate desk, ask yourself
- How many hours per week does your team spend building Excel reports for developers?
- How many commission disputes happened in the last 3 months that couldn’t be resolved with data?
- How many units were held but never converted — and the hold wasn’t released on time?
- Can you tell which CP has the highest visit-to-booking conversion right now? Without opening Excel?
- If a developer calls you right now and asks “how many leads came in this week for Tower B” — how long does it take you to answer?
If the answer to #5 is more than 30 seconds, your CRM isn’t working for you.
Next steps
- Managing multiple projects with one team — project-based routing and filtering
- Pre-launch vs ready possession pipelines — different sales cycles need different pipelines
- Weekend site visit management — handle 30 visits without chaos
- Why CRMs fail channel partners — the CP perspective
- Try ClosingFox free — set it up in 15 minutes, no sales call needed
- Sell.Do vs ClosingFox — Which Fits Mandate Teams?
- 39 Rules — Monitor Mandate Team Execution
—
Running a mandate desk and tired of Excel? WhatsApp me. I’ll walk you through the setup — I’ve been on your side of the table.