The situation
A capable, growing contractor delivering civil and infrastructure works across Western Australia. Revenue and headcount had scaled steadily. The systems and processes underneath had not.
Estimating sat apart from delivery. Plant and fleet utilisation lived in one place, cost in another, and site reality somewhere else again. Subcontractor engagement, compliance evidence, safety records, daily dockets, variations and progress claims each ran through their own combination of spreadsheets, shared drives, email threads and institutional memory. Nothing was broken, exactly. Everything took longer than it should, and no single view of a job existed without somebody assembling one by hand.
The instinct in that position is usually to go and buy something. That is where most of the money gets wasted.
What InArena was engaged to do
Lead the transformation as a business change with a technology component — not a software project with a change slide at the end. The mandate was independent: no product to sell, no implementation revenue to protect, and no stake in which platform ultimately won.
Phase one
Understand the business as it actually runs
Structured engagement with the owner, executive and the people doing the work — estimators, project managers, supervisors, plant, safety, commercial and finance. Not a survey. Conversations, on site, about what actually happens when a job is won, mobilised, delivered, varied and claimed.
Phase two
End-to-end business process mapping
Mapping the full operating chain — tender and estimating through mobilisation, site delivery, plant and labour allocation, subcontractor and supplier management, compliance and safety evidence, variations, progress claims and cost-to-complete. Every hand-off, duplicate entry, manual reconciliation and control gap made visible and quantified in effort and risk.
Phase three · underway
Consolidation into a single streamlined SaaS platform
Designing the future state and collapsing fragmented workflows into one coherent platform — with the target operating model, data model, integration boundaries and reporting designed alongside it rather than discovered afterwards. Requirements are grounded in mapped process, so platform selection is evidence-led rather than demonstration-led, and adoption is planned as part of the build.
Through the work
Governance that holds the intent
A decision log the owner can revisit, clear decision rights, and a reporting rhythm that surfaces problems while they are still cheap to solve. The measure of success is not that the platform goes live — it is that the business runs differently once it does.
Why it matters
Mid-sized businesses rarely fail at transformation because they picked the wrong software. They fail because nobody mapped how the business actually works before somebody sold them a system that assumed something else. Process first, platform second, and an independent voice in the room for both.