Project ERP with Client Progress App for a Singapore Construction Contractor

A mid-sized Singapore construction contractor — residential renovation, light commercial fit-out, A&A works. Annual turnover in the low eight figures, around 20 active projects at any given time. The operational pattern was the one we see across most SMEs in this space: the founder still touched every project, and the business couldn't grow past the founder's attention span.

The specific friction points:

• Quotation took too long. Each quote was a bespoke spreadsheet, assembled from past quotes by copy-paste. Estimators spent more time formatting than estimating.
• Approvals lived in WhatsApp. Variation orders, additional works, and material substitutions were approved in chats. When disputes arose six months later, the audit trail was a screenshot search.
• Clients called daily for updates. Homeowners and small business clients wanted to know where their project was. The PM spent two hours a day on phone updates that conveyed information already known to the site team.
• Cash visibility was lagging. Progress claims went out late because the documentation lived across folders. Payment delays compounded.

We designed a two-part system: an internal ERP for the operations team, and a client-facing mobile app for project visibility.

The ERP — operations spine

• Quotation builder with a maintained item library, costing logic, and PDF generation. New quotes pulled from past quotes structurally, not by copy-paste.
• Project workspace per job, holding the quotation, contract, variation orders, material schedules, site photos, and progress claims in one place.
• Variation order workflow with structured approval — client signs in the mobile app or signs on paper that the PM scans in. The audit trail is automatic.
• Progress claim generation tied to project milestones. The system assembles the claim document from project records and routes it for review.
• Management dashboard for the founder: active projects, outstanding claims, cash collected this month, projects at risk.

The client mobile app — visibility layer

• Each project has a private project page accessible to the client by invitation.
• Site team uploads daily photos and short updates from their phone. Updates appear in the client app within minutes.
• Milestone progress shown as a visual timeline.
• Variation orders pushed to the client for in-app review and signature.
• Progress claims and payment status visible to the client.

The thesis: most client phone calls aren't asking for information that isn't already known on site. They're asking because they have no other way to see it. Give them the view, and the calls stop.

After deployment, the operational shifts the team reported were the ones we'd designed for. Quotation turnaround compressed materially. The variation-order paper trail became airtight, which paid for itself the first time it was needed in a payment dispute. Client update calls dropped substantially as homeowners began checking the app instead of phoning. The founder got back several hours a week — not eliminated entirely, but enough that the business could take on more projects without adding headcount.

The deeper outcome was less measurable but more important. The team stopped working around the software and started working in it. Knowledge that had lived in the founder's head — pricing logic, approval norms, claim timing — got encoded into the system. The business became transferable.

Construction in Singapore is full of operationally sound businesses that can't scale past their founders because the operational logic isn't written down anywhere a system can run. The off-the-shelf options are either too generic (Xero plus folders) or too rigid (full construction ERPs designed for main contractors). A custom system built around the actual size and shape of the business — with a client-facing layer that handles the relationship overhead — is the gap.