Project costs visible before month-end, in Spanish
A construction firm in Mexico
Per-project costs lived in one person's Excel, purchases in WhatsApp threads. Now budgets, purchase orders and committed-vs-spent are live per project — and the whole system runs in Spanish, because that's the language the crew works in.
The system runs entirely in Spanish — screens, notifications, exports. Built that way from day one, not translated after.
01
What was broken
Each project's costs were tracked in Excel by one person in the office, updated when invoices arrived. Site managers requested purchases over WhatsApp; approvals were a thumbs-up emoji or a phone call, and the paper trail was a screenshot.
Nobody could see committed money — orders placed but not yet invoiced — so a project could look healthy for weeks while it quietly overran. The real position arrived at month-end, as archaeology.
02
What got built
- 01Project cost control: budgets by phase and concept, with committed vs. spent live per project
- 02Purchase orders raised from a phone on site, routed through a real approval chain
- 03A supplier catalog with agreed prices, so orders start from the negotiated number
- 04Every screen, notification and export in Spanish — the working language of the office and the sites
03
What changed
Site managers request purchases from the site, and the office sees the commitment the day it happens — not the month it's invoiced. Approvals leave a trail that isn't a screenshot.
Month-end closed the gap between what the spreadsheet said and what the projects had actually spent. The conversation moved from reconstructing the past to steering the next purchase.
Related demo
A fictionalized version of this kind of system is in the demo library — see Grupo Sillar, a Spanish-first construction demo.
Open the Grupo Sillar demo page →Recognize your Monday in any of this?
Tell us what's breaking — six questions on the studio page — or start with a call.