Built From Real Construction Experience. Including the Expensive Kind.

I've been in this industry long enough to know what it really costs when you have a bad estimate or project. In real dollars, on real jobs.

The one that sticks with me most was a commercial project, a large mechanical scope, eight figures, a multi-year anchor project. We were a subcontractor and the baseline estimate we were working from was wrong. Not obviously wrong, the project started off good. Wrong in the way that only becomes clear when you're deep into the work and everything is taking longer than it should.

By the time we understood the full picture, it was too late to do much about it. We honoured our commitments and finished the job. And we absorbed a seven-figure loss.

We survived because we were big enough to absorb it. But just barely. A loss like that doesn't just hurt the year it happens, it takes years to recover from. Years of tighter margins, harder decisions, and opportunities you can't pursue because your cashflow isn't there anymore.

That's the thing about construction. The mistakes don't always announce themselves. They accumulate quietly, in hours that don't quite line up, in information that exists somewhere but isn't where you need it, in estimates built on gut feel instead of clean data from the last job.

I've also been through the other side of the market.

When work dried up, we made the decision to cut our crew from 40 people down to 20. We reduced wages across the board, top to bottom, myself included. We gave everyone the choice. Stay at reduced wages or move on with our full support. Some stayed. Some left. All of them deserved better than the situation we were in.

Those decisions don't get easier just because they're necessary. You carry them.

What I kept thinking through both of those periods, the big loss and the slow market, was that we had the information; it just wasn't accessible. Timecards, reports, people's heads, folders nobody could find, and boxes of paper. If we could have seen it clearly, in real time, while the work was still happening, some of those decisions would have been different. Some of those losses would have been smaller. Some of those people might still be on the crew.

That's where SiteFX came from.

Not from wanting to build software. From wanting the information I needed to run better jobs, and realising that the only way to get it was to build the system myself.

I've worked on projects across commercial, industrial, and institutional builds, from mid-size jobs to eight-figure contracts. I've been an estimator, a project manager, a business owner, and everything in between. I know what it looks like when a project is running well and I know what it feels like when one is quietly going sideways.

SiteFX was built to close that gap. To take the field data that already exists on every jobsite and make it visible while there's still time to act on it. Not another report. Not another dashboard. Just a clearer picture of what's actually happening, while the job is still running.

If you've ever absorbed a loss that better information would have prevented, this was built for you.