Most Indian contractors start here — and it works, until the site count and project size outgrow what a spreadsheet and a chat thread can hold together.
For a single project with a small team, Excel and WhatsApp are hard to beat — zero setup cost, everyone already knows how to use them, and a quick photo update in a group chat is faster than logging into any system. This is not a case against the tools; it is a case about where they stop scaling.
The failure mode is rarely dramatic. It is gradual: a material figure in one person's spreadsheet doesn't match another's, a WhatsApp update about a site issue gets buried under fifty other messages by evening, and by the time someone reconciles material purchased against material used, a month has passed and the wastage number is a guess, not a measurement.
Multiply that across 3-4 concurrent projects, each with its own spreadsheet version and its own WhatsApp group, and the reconciliation lag stops being a minor inconvenience and starts being the reason cost overruns get caught at project close instead of week two.
The core difference is not "digital vs paper" — it is one shared, structured record versus scattered documents that each need manual reconciliation. Material logged on site updates the same BOQ everyone else sees, automatically, the same day — not at whoever's convenience it is to update the master spreadsheet.
| Feature | Rebota | Excel + WhatsApp |
|---|---|---|
| Material vs BOQ reconciliation | ✔ Automatic, same-day | ✘ Manual, usually monthly |
| Multi-project visibility | ✔ Single dashboard | ✘ Separate file per project |
| Site update reliability | ✔ Structured daily log | ✘ Buried in chat history |
| Cost overrun detection | ✔ Real-time alerts | ✘ Found at project close |
| GST/billing tracking | ✔ Built-in | ✘ Separate manual process |
| Setup effort | Moderate — one-time onboarding | ✔ None — already familiar |
| Cost | Paid subscription | ✔ Free |
Contractors running multiple concurrent projects (or a single project large enough that reconciliation lag is already costing real money) who are tired of chasing the latest spreadsheet version or scrolling WhatsApp history to find a site update from two weeks ago.
A contractor running one small project with a tight, co-located team genuinely doesn't need a system change yet — the switching effort (even though onboarding is designed to be fast) isn't worth it until the reconciliation pain is real and recurring.
Excel + WhatsApp wins on cost (free, versus a paid subscription) and on zero setup friction — everyone already knows how to use them. For a single project or a very early-stage contractor, that simplicity is a genuine advantage, not a compromise.
If material value is modest, the team is small and co-located, and reconciliation currently happens without pain, Excel + WhatsApp remains sufficient — the signal to watch for is reconciliation lag stretching from days to weeks, not a fixed project-count threshold.
Start with Excel + WhatsApp. Move when the reconciliation lag — not the tool itself — starts costing more in caught-late overruns than the switching effort would.
The contractors who scale past Excel + WhatsApp successfully don't abandon the habits that worked — they keep the field-friendly, low-friction update culture but move the underlying record to something structured and shared, so a site update updates the same BOQ everyone sees rather than living only in that day's chat thread. The practical signal to watch for is not a fixed size threshold but the reconciliation lag itself: if the time between "material was purchased" and "someone confirms it against the BOQ" is regularly weeks rather than days, the spreadsheet-plus-chat workflow has already started costing more in caught-late overruns than a system of record would.