I’ve spent the last six years walking job sites, trailers, and finance offices at construction companies — from $40M regional builders to ENR Top 100 generals. The same pattern shows up in almost every one of them: a senior project accountant, every month-end, rebuilding a spreadsheet that reconciles Procore to the GL. By hand. For two days.
The accountants are good at their jobs. The contractors are well-run. The software vendors are sincere. And yet the work is still being done by humans copying numbers between systems, in 2026.
This isn’t an accident. It’s the residue of three structural problems that the construction software industry has been allergic to fixing. They’re worth naming.
The “every job is unique” story
The story goes like this: construction is a project-based business, every project has its own cost structure, every contractor has their own way of categorizing committed costs, and so any integration between project management and the GL has to be customized. The implication: there’s no such thing as a pre-built connector that actually works.
This story is half-true, which is what makes it durable. The cost-code structure really is bespoke. The committed-cost logic really does vary. But — and this is the half that gets ignored — the underlying data model is shockingly consistent across the industry. Procore exposes the same objects to everyone. Sage 300 CRE has the same job-cost categories. The variance is in the mapping, not the structure.
Pre-built doesn’t mean rigid. It means the structural work is done — the schemas, the auth flows, the rate limiting, the conflict rules — and what’s left is the actual variance the contractor cares about: their cost-code tree, their reporting cadence, their commitment workflow.
The middleware that doesn’t understand the work
The other thing contractors get sold is generic iPaaS. The pitch sounds great in the demo: “drag-and-drop integration, no code, works with everything.” And it does — for the first ninety days. Then committed costs show up.
Generic middleware doesn’t know what a committed cost is. It doesn’t know that a change order has a budget impact and a contract impact and a schedule impact, and that they need to flow to three different places with three different rules. It treats every record as a row to be moved, when the actual work is record-with-context-to-be-reconciled.
The result: companies pick a generic iPaaS, get six connections live, then hit a workflow that doesn’t fit the model. They write custom code around it. Six months later, the custom code is the integration; the iPaaS is just a runtime. Twelve months later, that custom code is breaking every Sage update.
The bias toward consulting hours
The third problem is about incentives. Almost every “integration partner” in construction is a services firm. They get paid by the hour. They have, structurally, no reason to make the work go faster.
That’s not a moral indictment — it’s a market structure observation. When the people pricing the work are also doing the work, the work expands to fit the budget. Six-month integration projects become twelve-month integration projects. Configuration becomes customization becomes custom development.
What changes
What we’re betting on, at Aquifer, is that this equilibrium is breaking. Three things are happening at once: the schemas are stable enough to ship pre-built connectors against, contractors are tired of the cycle and allergic to “we’ll build it custom for you,” and the economics of pre-built finally pencil out for a product company in a way they never did for services firms.
The variance should live in the customer’s business, not in the plumbing.
What we tell contractors
When a contractor calls us, the first thing we ask is: show us the spreadsheet. The one your accountant rebuilds every month. We’ve yet to meet a contractor who couldn’t find one inside ten minutes. That spreadsheet is the integration that’s already running in your company. Our job is to replace it.
Construction is one of the largest, most under-digitized sectors in the country. Every dollar of inefficiency in this industry is a real cost — a project that runs over, a building that gets delivered late, a contractor that goes out of business because their committed-cost dashboard lied to them. The real economy is calling. We built Aquifer to answer.