Product update: ENRO's WhatsApp connector is nearly here
After weeks of work on privacy and reliability, site WhatsApp groups can feed ENRO directly. Production rollout is planned for next week.
After weeks of work on privacy and reliability, site WhatsApp groups can feed ENRO directly. Production rollout is planned for next week.
Why construction software in India has to understand Hindi, Assamese, Tamil, Bengali and mixed-language site messages.
Questions to ask before any tool reads your site WhatsApp groups, and how we answered them for ENRO.
A worked example of capturing quantity, project, need-by date and owner from one site message.
WhatsApp is where site work is reported. The problem is turning those messages into a record someone can act on.
Reconcile opening stock, receipts, issues and physical counts without hiding unexplained differences.
A partial-delivery example showing what to compare before approving a supplier bill.
Build a dated cash forecast and separate likely receipts from money already in the bank.
Sort unpaid invoices by due date, explain disputed balances and avoid double-counting receipts.
Separate a proposed change from an approved instruction, budget revision and paid cost.
A filled example linking quantities, blockers and named follow-up rather than vague progress claims.
Use consistent quantities and rates to explain a work-package variance.
Compare equivalent quantities, delivery costs and exclusions before choosing a supplier.
Keep ordered, accepted, rejected and still-open quantities separate.
Review measured work, previous certification and deductions without confusing a claim with approval.
A simple example of cash in hand, supported spending and unresolved vouchers.
Give the next person a decision-ready record instead of a forwarded message.
An answer is not fully useful until the affected team knows which information to use.
Record the event and affected work without presenting an untested delay claim as fact.
Define the time basis before interpreting an equipment percentage.
Work backwards from the required-on-site date and give each supply risk an owner.
Use a small import and control totals to find unit, date and duplicate errors.
Test allowed and forbidden actions with separate accounts, not just menu visibility.
Check scope, source records, arithmetic and missing information before acting on an AI answer.
Define a workflow, test exceptions and decide from observed use rather than a feature list.
ERP connects core business work and records in one system. Here is what that means for projects, site teams, procurement, sales and finance.
A bill of quantities, or BOQ, lists measured work items so a team can describe, price and compare a defined scope.
Quantity takeoff is the process of measuring the materials or work quantities represented by project information.
An estimate predicts cost; a BOQ describes measured work items that can support pricing and comparison.
Start with a common scope, then compare price, exclusions, delivery and payment terms on that same basis.
A work package is a manageable part of the project scope with a defined output and responsibility.
A work breakdown structure, or WBS, organizes the project's scope into deliverables and smaller manageable parts.
A baseline programme is the agreed schedule used as a reference for measuring later progress and change.
The critical path is the sequence of linked activities that determines the schedule's completion under its current logic.
Float describes available schedule flexibility within a defined network of activities and constraints.
A lookahead plan turns the near-term programme into work the site team can actually prepare and carry out.
A useful daily progress report states what happened, where it happened, what remains blocked and what needs a decision.
Report progress against a stated measurement basis rather than a person's overall impression.
A milestone marks a significant point or event in the programme.
A delay log records events, their timing, affected work and available evidence so their impact can be reviewed.
An RFI, or request for information, is a formal question used to clarify project information.
A useful RFI is specific enough that the reviewer can identify the issue and give a decision without another round of explanation.
A submittal is project information provided for review under the project's agreed procedures.
Use one identifiable current issue and preserve earlier revisions as superseded records.
An as-built drawing records the constructed condition rather than only the original design intent.
A site instruction communicates a direction through the authority and process defined for the project.
A variation or change order records a change to the agreed work through the applicable contract process.
Keep a pending change register separate from the approved cost position.
A purchase requisition is an internal request for goods or services before an order is issued.
A purchase order should make the intended supply and its commercial terms clear to the supplier and the receiving team.
A goods received note, often called a GRN, records a receipt of goods.
Three-way matching checks a supplier invoice against the purchase order and the recorded receipt.
Record the received portion and leave the balance visibly outstanding.
Record material leaving stores against its destination or purpose, not only against a person's name.
Material reconciliation compares quantities received, issued, returned and remaining to investigate differences.
Make the unit part of every quantity and define conversions before combining records.
A measurement book is a controlled record of measured work that can support checking and payment assessment.
A running account, or RA, bill is an interim claim or assessment for work during a continuing contract.
Retention is money withheld from payments under the contract's terms.
A mobilisation advance is an upfront payment arrangement intended to help a contractor begin work, where the contract provides for it.
An extension of time changes a contractual completion date through the agreement's assessment process.
A snag list records outstanding defects or incomplete items that need attention before or around handover.
A handover checklist connects completed work with its required evidence and outstanding responsibilities.
A risk register records uncertain events that could affect project objectives and how the team plans to respond.
A cost code is a consistent label used to group costs for a defined project activity or category.
Committed cost concerns obligations already made; actual cost concerns cost recognized under the organization's accounting basis.
A cash flow forecast estimates when money will be received and paid over future periods.
Cost to complete estimates the remaining cost needed to finish the defined work.
Start by checking what the comparison measures, then investigate the reason for the difference.
Earned value expresses completed work using the budget assigned to that work.
CPI compares earned value with actual cost; SPI compares earned value with planned value.
Carpet area is a defined area measure under RERA, distinct from broader saleable-area descriptions.
Completion and occupancy approvals serve different purposes, and the documents required depend on the applicable local process.
Use a consistent project and document reference, a clear status and a known owner.
A useful handoff tells the next person what is wrong, what has been checked and exactly what action is needed.
Check the meaning and quality of the data before importing the file.
AI is more useful in a real estate ERP when its answer can be checked against the project’s recorded data.
A supplier bill is easier to review when the finance team can see which project and work it belongs to.
A useful site update tells the next person what changed, what is blocked, and what needs a decision.
Enro uses AI to help real estate teams ask questions about authorized project records and draft selected operational updates.
Enro brings project, site, sales and finance records into one workspace so real estate teams can review work with its project context.
Enro is an AI-assisted ERP option for Indian real estate developers who want projects, site tracking, sales and finance in one workspace.
“What needs attention on this project?”
A project manager asks, “What changed on this project?” The useful answer should point to the site update, task or expense behind it. A confident paragraph is only useful when the team can check where it came from.
A neat project summary can hide an important gap: nobody knows which record it came from.
By Akash Dehingia, founder of Enro
Three early users have tried the Enro demo. Their feedback is useful because it includes what still needs work. These are anonymous summaries, not customer quotes or measured results.
A third early Enro user told us that a shared workspace for real estate teams could be useful in the industry. They said they would tell others about it. We appreciate that interest, but we are treating it as feedback, not as a referral or a customer endorsement.
For one early user, keeping track of project bills was a recurring problem. The information was spread across day-to-day messages and spreadsheets, making invoices harder to follow.
One early Enro user was gathering project updates from WhatsApp chats and Excel sheets, then entering them into their own system. That made it hard to see inventory and finance information together.
Enro’s first demo is now live. We’re building all-in-one, AI-assisted ERP software for Indian real estate developers and their teams.
A developer trying new real estate software already has records to bring across. Those might be buyer enquiries, project details or follow-up dates in a spreadsheet. Asking the team to enter them again adds work before they can even judge the product.
I’m Akash, founder of Enro. We’re building operations software for Indian real estate developers, and one question keeps shaping our research: what would make a site team actually use a new tool every day?
Enro is developing a connected operations workspace for Indian real estate developers and the teams delivering their projects. We have an early demo and are building the first version.
I’m Akash, the founder of Enro. We are building operations software for Indian real estate developers and the teams delivering their projects. Our goal is to connect the information people need to move work forward: site progress, requests, decisions, costs and collections.
A demo can show what software does. A pilot should reveal whether a team wants to keep using it.
A buyer follow-up, a site update and a material request may all belong to the same real estate project. Yet the people handling them can be working from different chats, spreadsheets and software screens.