Foundations
Architecture first
Data model, security and hosting designed before any screens, so the back office and the crew app share one solid base.
Monk Earthworks: an operations hub and a crew app, replacing WorkflowMax.
A civil contractor running budgets, claims and crew on a tool that had stopped fitting the business. Now on software built around how they actually work.
- 13
- crew on the app daily
- iOS + Android
- timesheet app
- Iterating
- block by block
The problem
The system was shaping the business, not the other way round.
WorkflowMax and spreadsheets were carrying budgets, variations, claims and invoicing, with crew time captured on paper and re-keyed. Nobody trusted the numbers until month end, and the people on site had no reason to use the office tools.
What we built
- Web back office: budgets, variations, progress claims and invoicing in one place
- Crew assignment and daily scheduling
- Crew timesheet app on iOS and Android, built for gloves and bad signal, with offline sync
- Reporting that matches how the business already thinks about a job
- Migration off WorkflowMax, with Xero export
Technology
What it runs on.
Next.js
Expo / React Native
Supabase Postgres
Offline sync
Over-the-air updates
Xero export
How we worked
Foundations first, then a prototype in the office, then production in blocks.
Block one
Back office
The thinnest path through claims and variations, reviewed live with the office team for two weeks, then rebuilt around what they did with it.
Block two
Crew app
Timesheets on the phone, trialled with one crew before rolling out to all 13. Now iterating on scheduling.
Where it is now
Live, 13 crew, still improving.
The back office runs the business day to day and the crew app is in use on every site. We run and support it on a monthly agreement and keep iterating in blocks.
Talk to us about a similar buildRunning a business on a tool that has let you down?
Start with a Blueprint: 3 to 5 days, and a plain go or no-go call at the end.