ERP features explained for Indian builders — what matters, what's enterprise fluff
Most “essential ERP features” articles were written for someone else. They're aimed at factories (MRP, shop-floor control), retailers (POS, e-commerce sync), or Fortune-500 finance teams (multi-entity consolidation, revenue recognition). A builder running 4 sites and 30 people reads the list, feels behind, and either overpays for software they'll never open — or gives up and stays on Excel.
The right question isn't “which ERP has the most features?” It's “which features stop mymoney leaking?”
What actually matters at 1–50 people
Money features first. GST-compliant billing with e-Invoice and e-Way built in. Receivables you can chase. A budget that compares itself to actual spend. A 3-way match on vendor bills. These pay for the software in the first quarter — everything else is convenience.
Then site-truth features.Attendance that's GPS-verified instead of a muster roll. Daily logs and photos with timestamps. Material indents with an approve-issue trail. QC checklists with proof. The pattern: every feature that converts “someone said” into “the record shows.”
Then people features.Statutory payroll (EPF/ESI/PT/TDS) so compliance isn't a monthly panic. Roles, so the site engineer sees work but never rates. A client portal, so “what's the progress?” stops being a phone call. And your team's language — an app your supervisor can read in हिन्दी, தமிழ் or ಕನ್ನಡ gets used; an English-only one gets ignored.
The enterprise fluff — and why it's on every list
MRP and BOM management — for manufacturers. Your BOQ is not a BOM (we wrote a whole post on that confusion). BIM integration — powerful with a BIM department; decoration without one. Multi-entity consolidation — for holding companies. Demand forecasting with ML — for supply chains moving thousands of SKUs daily; a reorder alert on cement does the job on a site. Drag-and-drop BI studios — owners look at six reports; they want those six to be right, not a query builder.
These appear on every list because feature grids are written by the vendors with the longest grids. Ticking 200 boxes is easy if nobody checks whether any single box works end-to-end.
Three questions that cut through any demo
1. “Show me an invoice becoming an e-Invoice, live.”Not a slide — the IRN coming back. Half the market can't do this without a third-party portal.
2. “Where does the site engineer's daily photo go, and can he see the project P&L?”The first tests field usability; the second tests whether permissions are real (he shouldn't).
3. “What happens to my data when I leave?” A confident vendor shows you the export button. A nervous one changes the subject.
The honest bottom line
You need roughly twenty capabilities, done properly, in one place, at a price that doesn't punish you for adding your 6th user. That last part matters more than people expect: per-seat pricing quietly teaches firms to notonboard the site team — and an ERP the site doesn't use is a diary. It's why Rebaar prices per workspace, flat — every engineer, storekeeper and accountant on the record, no seat mathematics.
For the full capability-by-capability checklist (including what we don't build), read the complete construction-ERP checklist — then hold every vendor to it.