Construction Intelligence for Heavy Civil
Every project should make the next project smarter.
MESA connects the assumptions behind an estimate to what actually happens in the field — so a heavy civil contractor's next bid is informed by what really happened last time, not a stripped-down average or a memory that's already fading.
The Core Loop
The Problem
The issue isn't too much data. It's that knowledge loses its connections.
An estimate's assumptions become disconnected from the execution that tests them. A completed project's actual performance becomes disconnected from the next estimate that could use it. Each disconnection is a point where the organization relearns something it already knew.
Assumptions don't survive award
Production rates, crew plans, and cost logic built into the bid rarely travel with the project once it's won — the field team works from a number, not the reasoning behind it.
Variance gets recorded, not explained
Daily reports capture what happened. They rarely connect back to why it differed from what was assumed — so the variance sits in the record without becoming useful.
Historical data loses its context
A unit price without its project's conditions — location, soil, crew, timing — is a number you either distrust or misapply. Neither builds real institutional knowledge.
In Practice
One project. One documented variance. A traceable answer.
County Road 14 & Meridian Pike Roundabout — a single-lane roundabout replacing a signalized intersection, with storm drainage, water main relocation, and full concrete/paving scope — is the flagship project in this interactive showcase, with a 57-line-item bid schedule behind it.
The variance was a cost story, not a quantity story — and every number above traces to the field condition that explains it, not the other way around. Open this project in the demo workspace →
What MESA Contains
Three connected areas, not a generic platform.
MESA is scoped narrowly and deliberately — the connective layer between an estimate and the field record that tests it, not a replacement for every system a contractor already runs.
Explicit, inspectable assumptions
Bid items, quantities, and the crew, equipment, material, and production logic behind every unit price — visible before and after award, not filed away at bid time.
See it on an active bid →Structured against the same bid items
RFIs, change events, quantity tracking, and daily reports — organized so the field's actual story can be measured against the estimate that preceded it.
See it on an active project →Estimate vs. actual, with evidence attached
Every variance shown carries a path back to the RFI or change event that explains it — never a number presented without its reason.
See it on a closed project →Where MESA Fits
The mechanics aren't new. The traceability is.
HCSS, B2W, and Procore already move field data back into the next estimate — that loop isn't new, and MESA doesn't pretend otherwise. What's still mostly manual across those tools is the last step: noticing the pattern and carrying it into the next bid with its reasoning intact. That's the gap MESA is built to close.
Public market information as of 2026, not MESA product data.
In other words: the data already gets captured. MESA's bet is that making the pattern-matching and its justification visible — not just storing the numbers — is what actually changes the next bid.
Operating Principles
What keeps MESA honest.
Try It Yourself
Step through the exact loop, on four real-shaped projects.
The demo workspace isn't a mockup of one screen — it's a fictional but fully-connected portfolio: two active projects, two projects out to bid, and one closed job whose actuals are already shaping the next estimate. Walk the same Estimate → Field Record → Project Intelligence path MESA's users walk.
Launch Interactive Demo →Built for the Field
Not just the office.
Every screen so far has been the estimator's or the PM's view. The same record — the same project, the same day — is just as much a five-minute mobile entry from the crew lead standing at the excavation. That's what closes the loop: the field data behind County Road 14's RFI-201 didn't arrive from a spreadsheet, it arrived from a phone.
What MESA Is Not
Scoped on purpose.
MESA is not trying to replace the systems a contractor already runs — it's the connective layer those systems are currently missing.