What real estate developers actually track
Walk into a developer's MIS meeting and the questions are remarkably consistent. None of this is exotic. All of it is operationally critical. And almost none of it lives in a single system.
- Sales velocity by project and configuration. What did we sell this week, by tower and unit type, against the launch plan?
- Collections versus booking value. What is sitting in escrow, what is in the working account, and what is overdue from booked customers?
- Construction spend versus approved budget. How is each project tracking against the BOQ, vendor by vendor, on RA bills submitted versus paid?
- Broker channel ROI and payouts due. Which channels bring leads that actually convert, and what do we owe channel partners this fortnight?
- RERA escrow discipline. Are we within the mandated 70% escrow rule on every active project, every quarter?
Sales sit in a CRM (Sell.do, LeadRat, Salesforce, Zoho, or a custom PHP build). Unit status, civil cost, and vendor bills sit in a construction ERP or a homegrown inventory tool. Financials, GST, and TDS sit in Tally, usually one company per SPV. RERA-side data sits on the state portal. The dashboard worth building holds all of this in one view, sliced by SPV.
Why off-the-shelf BI struggles here
A typical Power BI or Tableau project starts with a question the vendor has never asked you - which database? Real estate rarely has one. You have a Sell.do account for two projects, a custom CRM your earlier IT team wrote for the Pune townships, Tally Prime running per-SPV on the accountant's desktop, and an Excel workbook the project engineer maintains for RA bills.
BI tools handle one source elegantly and three sources with a six-month integration project. They also assume your calculations are universal - revenue, cost, margin. Real estate calculations are not universal. Revenue recognition on a flat is different from revenue recognition on a plot. The proportionate completion method changes which costs flow into project P&L this quarter. RERA calculates project cost differently from how your auditor calculates it. A generic BI dashboard either ignores these nuances or buries them in DAX nobody on your team can read.
The other quiet failure is question velocity. A working developer asks new questions every week - conversion rate from a hoarding versus digital leads, cost overrun on Tower B excluding GST input credit, subcontractor variation in RA bill versus PO. Each one is a ticket to your BI consultant. That is fine for an enterprise. It is exhausting for a 30-person developer team.
The data sources you actually combine
Five sources cover most developers. The consolidation problem is not just connecting these sources, it is matching the same flat across systems. The CRM calls it 'Tower B Unit 1204', Tally calls it 'TWR-B-1204' on the customer ledger, the inventory module uses serial 'B-12-04'. Without a clean SKU map, your project P&L double-counts some bookings and misses others.
| Source | What lives there | Common pain |
|---|---|---|
| CRM | Leads, site visits, bookings, broker attribution, payment schedules | Multiple CRMs across projects, custom builds with no API |
| Construction ERP / inventory | Unit status, BOQ vs actual consumption, vendor bills, RA bills | Item master differs from CRM and Tally naming |
| Tally (per SPV) | GL, GST, TDS, escrow balance, audited cost and revenue | 8 to 15 separate companies on different machines |
| RERA portal | State filings, project registration, pre-filled escrow figures | Quarterly format changes by state authority |
| Excel and shared drives | RA bill trackers, project engineer notes, broker reconciliations | Lives in one head, breaks when that person leaves |
Multi-SPV consolidation in practice
Indian real estate developers structure each project as a separate SPV for tax, RERA, and investor reasons. The owner still wants to see one number alongside the project-level drill-down.
Doing this manually means an MIS analyst exports every Tally company to Excel every Friday, runs a consolidation macro, and emails a deck. The deck is stale by Monday and opaque if the owner asks 'what is in this number'. KolossusAI reads each SPV's Tally in place, plus the CRMs and inventory systems, and answers consolidated questions live with one-click drill-down to the source voucher in the right SPV.
RERA reporting is a data problem first
The quarterly RERA progress report is where most developers' MIS pain becomes visible. The CA needs project-wise booking status, collection summary, escrow movement, and construction expenditure aligned to the format the state authority accepts. Pulling these from a CRM, Tally, an inventory system, and a bank statement spreadsheet is a two-week annual exercise that turns into a four-week panic when the deadline approaches.
- Pre-built question pack. Form 4 inputs per tower per quarter, ready to export in the state-authority format.
- Live escrow utilization view. Per-project draw against the 70% threshold, refreshed from the SPV's Tally bank ledger.
- Booking and collection reconciliation. CRM bookings matched to Tally customer advances, with mismatches flagged for the CA team to investigate.
- Construction expenditure roll-up. RA bills, vendor advances, and capitalised costs aggregated per project from the construction ERP and Tally.
- Drill-down to source for the auditor. Every figure in the RERA pack is one click away from the underlying voucher or CRM record.
The questions developers actually ask weekly
Sales velocity by configuration. Collection ageing by customer. Broker payouts pending. Project margin to date. Escrow utilization. Vendor exposure on unsubmitted RA bills. These are not exotic queries - they are weekly operational decisions. The bottleneck is not analytical sophistication. It is the time it takes to assemble the underlying numbers from five systems.
KolossusAI compresses that assembly from a day-long MIS exercise into a 10-second answer with the drill-down to the underlying CRM record, inventory entry, or Tally voucher visible immediately.
How AI handles this stack
KolossusAI's AI for Indian real estate developers connects to the five source categories above through secure read-only connectors. The system learns your project structure, SPV map, and naming conventions during a 2 to 3 week onboarding, then sits behind a chat interface your team uses in plain English. The owner asks 'show me Tower B P&L' and the AI composes the answer across CRM, inventory, and Tally, honoring your revenue recognition policy, with the source rows one click away.
The trade-off is that you do not get a wall of charts by default. Most developers we work with handle this by pinning 6 to 10 standard views (sales velocity, collection ageing, escrow, project P&L) for the Monday review and using the AI for everything ad-hoc, which is where 80% of the actual decisions get made. See our customers for production deployments at this exact pattern.