The accumulation
Construction and M&E businesses tend to arrive at the same place by different routes. Nobody designed it; it built up one reasonable decision at a time:
- An estimating process held together by spreadsheets and an ageing desktop tool
- A component catalogue that nobody owns
- Project tracking in one system and job information in another, so a simple question about a live job means opening both
- No consistent way for staff to move between any of it
Each one on its own is survivable. Together they mean the business depends on a handful of people who know which spreadsheet is current.
Why buying something often does not fit
For most of what a contractor runs (accounts, payroll, email) buy the product. The market has solved those, and we will say so.
Estimating is different. How you price mechanical and electrical work is the thing that makes you competitive, and generic estimating software flattens it into the method everyone else uses. That is the strongest case there is for building: the process is the product. It is also why replacing the spreadsheet is usually the first step rather than the last, because the spreadsheet is where the method is currently written down.
The difficulty is cost. Building an estimating tool, a project system, a catalogue and an operations hub one at a time, each from scratch, would be unaffordable for most groups. So we don't build them that way.
Platform first, applications on top
The foundations go in once, and every application after that inherits them:
- A shared component library, so every application looks and behaves the same and staff are not relearning screens
- Single sign-on, so moving from the estimate to the project to the operations hub does not feel like crossing a boundary
- Shared product analytics, so you can see which tools are actually used and which are being worked around
On top of that sit the applications the business needs. For contractors that has meant M&E estimating with the group's own method encoded in it, tender analysis that uses AI to get an estimator through a document set that used to take days, project management built for how construction projects actually run, an owned component catalogue behind an API, and a staff operations hub for the day-to-day. The AI in tender analysis assists the estimator rather than replacing them.
Where engineers are out on site, the office-side systems can be joined by a mobile app for job sheets that keeps working without a signal. The field service page covers that part.
The evidence
For a construction and M&E group, we built eight applications on one platform, including estimating, AI-assisted tender analysis, a web rewrite of a legacy estimating workflow, project management, a component catalogue, a staff operations hub and a marketing automation platform, all on the shared foundations above. It is live and in daily use across the group. Seven of the eight were built between May and August 2026.
The number that matters is not the eight. It is that the eighth application cost a fraction of the first, because authentication, the interface library, the deployment pipeline and the conventions were already settled by then. That is what makes a suite affordable for a business that is not a software company.
Price and ownership
Fixed price, off a scope agreed in writing. Engagements start from £4,000; most first builds of a real business system land between £8,000 and £15,000. A suite of that size is phased, and each phase earns its keep on its own — the estimating tool is useful before the project system exists.
The code, the hosting and the accounts are set up in your name as the work goes. Your estimating method is your competitive advantage, and it should not end up living in a supplier's repository.
Who does the work
One senior engineer scopes it, builds it and deploys it. For a contractor that means explaining how you price a job once, to the person who will write it. It also means we are not the right fit if the programme needs a team of five from day one — and we would rather say that before a contract than after one.
If your estimating lives in spreadsheets, or following one job means opening three systems, tell us about it.