Every development on one dashboard — contractor billing and retention for the build side, plus a real unit-sales layer: availability, bookings and milestone payment tracking.
Managing multiple residential or commercial developments without a shared dashboard means status lives in separate files per project.
Without a system tracking certified vs received amounts, retention held across contractors becomes difficult to reconcile at handover.
Sales spreadsheets showing which units are booked, sold or available drift out of sync with the actual project the moment either side updates independently.
| Business requirement | Rebota capability | Relevance | Status |
|---|---|---|---|
| Portfolio View | Projects (multi-project dashboard) | High | Available |
| Contractor Agreements | Contracts | High | Available |
| Cost Control | Cost Control, BOQ & Estimation | High | Available |
| Unit Inventory & Bookings | Real Estate Units & Bookings (tower/floor/unit, booking, buyer) | High | Available |
| Buyer Payment Tracking | Milestone Payment Schedule, linked to invoices | High | Available |
| Billing & Retention | Client Billing — retention auto-posted to its own ledger account when an RA bill is invoiced | High | Available |
| Reporting | Reports & Dashboards | Medium | Available |
Rebota is used across a wide revenue range, and the honest answer differs by band. This is what it replaces outright, what it replaces with gaps you should plan around, and where you would be better served elsewhere today.
| Annual turnover | Verdict | What that means in practice |
|---|---|---|
| ₹1 – 10 crore | Replaces | Full replacement for a single-project developer: units, bookings, collections, construction cost and the ledger in one place. |
| ₹10 – 100 crore | Replaces | Works well. Unit inventory, customer collections against milestones, contractor bills and project cost control are all live and connected. |
| ₹100 – 500 crore | Replaces with gaps | Usable, with two gaps: RERA quarterly reporting is prepared outside the system, and each SPV is its own company with consolidation done manually. |
| ₹500 crore and above | Not yet | Not yet. Multi-SPV consolidation and integrated scheduling are prerequisites at this size and neither exists. |
What is built and enforced in the product today, by jurisdiction. Anything not listed here is not claimed.
Statutory filing is built for India only.
| Alternative | Stay with it when | Move to Rebota when |
|---|---|---|
| Tally | Books only, with unit bookings tracked separately in a spreadsheet. | You need unit inventory, collections and construction cost to be one connected picture. |
| SAP | You are a listed developer with statutory consolidation across many SPVs. | You are paying enterprise licensing for a handful of projects. |
| Excel and WhatsApp | One small project, sold out, nothing left to track. | Sales and site each hold a different version of what a unit has cost and collected. |
If one of these is core to how you run, Rebota is the wrong choice today and we would rather you knew now than in month three.
| Not built | Who actually needs it |
|---|---|
| RERA quarterly reporting | Every registered developer. Rebota holds the underlying project, cost and collection data, but it does not generate or file the RERA return — that is prepared outside the system. |
| Multi-SPV consolidation | Developers running each project as its own company and needing consolidated group statements. |
| Critical-path scheduling | Developers whose construction programme is managed as a CPM network rather than as activities and progress. |
No sign-up, no email. These run entirely in your browser.
