The Status Trap: Why Construction’s Best Innovation Roles Don’t Look Like Innovation Roles
The construction industry has an innovation problem, but it’s not the one people talk about at conferences.
This article is written by Victor Muchiri who runs strategic initiatives at BuildVision. Prior to this, he spent time at Barton Malow on strategy and business transformation and started his career in the field with a degree in construction management from The Ohio State University and worked in the field for companies like Turner Construction. He writes one of my favorite newsletters, The Next Build about construction technology, construction strategy, and industry consolidation which I highly recommend subscribing to.
I’m so tired of hearing that contractors are resistant to change. The core issue is that the industry has built an entire class of roles designed to look like progress without producing it. And the people who actually drive technology adoption, the ones doing the unglamorous, operationally messy work of making software stick inside a real business, are often invisible.
It’s a structural issue. And this is the status trap.
Over the past decade, large general contractors created innovation roles with titles like Director of Innovation, VP of Construction Transformation, Head of Construction Technology. These are high status roles. They come with conference speaking slots, executive visibility, travel budgets, and the social currency of being “the future of the company.”
However most of these roles share a structural flaw: they sit outside of operations.
The innovation team evaluates tools. They run pilots. They write internal memos about what’s possible. But they rarely own a P&L, manage a project, or have the authority to mandate that a $200M hospital project team changes how it works.
I’m not criticizing the people in those roles. These are our friends and colleagues. Many of them are sharp, motivated, and frustrated by the exact dynamic I’m describing. The structural problem is that when you separate innovation from operations, you repeatedly run into the brick wall where technology adoption stalls at the pilot stage. The innovation team can find great tools. But making a tool work inside a real project requires operational authority, operational credibility, and the willingness to grind through the messy middle of deployment. Many of these folks weren’t structurally set up to succeed. The game is rigged.
The innovation function began as a modernization effort. It was built to help first adapt, compete and improve how work actually gets delivered.
But how many innovation teams have delivered on this promise?
Instead, external signalling gained strategic value, evolving into a platform for business development and talent attraction. In some cases, the appearance of progress started to matter more than the progress itself.
The conference circuit, the panel invitations, the title, these became the markers of success rather than operational impact. People started optimizing for the rewards of innovation work before doing the actual innovation work. High-status, low-success.
Meanwhile, the people who actually drive adoption are often invisible. The project manager who stays late to configure the software. The estimator who rebuilds a template to match the new workflow. The superintendent who agrees to test a daily log tool even though the old way was working fine. Low-status, high-impact. Low-status, high-value.
This is the inversion the industry needs to recognize: low-status does not mean low-value. In most cases, the opposite is true.
Low-status work is low-status because it’s hard to measure and easy to ignore. Nobody tracks the hours the estimator spent reconfiguring a template. Nobody puts “successfully changed how the team does daily logs” on their annual review. But the conference keynote that gets a LinkedIn post with 200 likes is a major dopamine hit. The incentive structure of the industry actively rewards visibility over impact, and that’s why the inversion persists. People aren’t irrational for chasing status. The system is paying them to.
What’s Actually Changed
For 15 years, contech companies built products for the median general contractor.
They looked at workflows common across the industry, document management, RFIs, submittals, daily logs, and built standardized tools that could be sold to any GC with minimal customization. This made sense as a business model. It scaled. But it created a ceiling on ROI.
Software that worked well enough for everybody and worked great for nobody.
The features that made a DPR different from a Big-D, Shawmut, McCarthy, or a Hoar, the specific sequencing decisions, the approval hierarchies, the procurement patterns, none of that was captured in the tool.
AI changes this equation.
Instead of buying a standardized product built for the median contractor, GCs now have the option (and obligation) to co-develop software with a vendor’s technical team. The vendor brings the AI capability, the data infrastructure, and the engineering resources. The GC brings their data warehouse and operational knowledge: how their buyout process actually works, why their scheduling logic differs from the textbook version, and what their superintendents actually need on a daily basis.
This is the FDE model (forward-deployed engineers) that’s becoming standard across enterprise AI.
OpenAI just launched an entire platform, Frontier, built around this idea: pairing deployed engineers with enterprise customers to build context-specific AI agents. And Palantir just released their Foundry platform for construction allowing enterprises to encode their decision making into software.
The approach is valuable as the underlying technology is moving faster than vertical products can adapt. Enterprises get platform leverage, with more customization and scalability.
This pattern is standardizing in construction, and it means the companies that engage with it seriously will have tools their competitors literally cannot buy off the shelf. Don’t be surprised if your Procore bill goes up this year by the way.
But here’s the catch. The FDE model only works if there’s someone on the contractor side who’s actually willing to be low-status in the short term. Someone willing to be curious and nerdy and who’s willing to ask hard questions to deeply understand operations. Someone who is technically curious enough to learn how AI works, and is willing to grind through the co-development process.
Winners are Low-Status
Think about what the co-development model looks like in practice. A solution provider provides an FDE that wants to build an agent that automates subcontractor bid leveling. They have the AI capability. What they don’t have is your knowledge:
How your company actually evaluates bids
Which scopes you typically self-perform, how your preconstruction team handles scope gaps
Why your senior estimator always adjusts unit costs on concrete by 8% in the Southeast
That context is locked inside your operations and with your staff. Without someone who can extract it, translate it, and pressure-test the AI’s output against real project conditions, the agent is just a cool demo.
The person who does this doesn’t need a Director of Innovation title. They need operational credibility, a tolerance for ambiguity, and the patience to sit in between “this is how our business works” and “this is what the technology can do.”
I suspect the most successful companies through 2026+ are the ones that identify and empower this kind of person. Someone who came up through operations. Someone who knows why the company does things the way it does because they lived it on a project. And someone curious enough about AI to understand what’s now possible, even if they can’t write code (which is no longer a requirement with AI, by the way).
It’s a different profile than the one most GCs hired for five years ago.
The new archetype is a bridge between the vendor’s FDE team and the company’s operations. They co-develop workflows, they test agents against real project data and they push back when the technology doesn’t match reality. It’s a high-friction, low-visibility role. It won’t come with a speaking slot at an ENR FutureTech conference. It probably won’t have “innovation” in the title.
But it will be the role that determines whether your company captures value from AI or just talks about chatbots for another five years.
A Note for 2026
2025 was the year of trying stuff. Everyone got a pass for experimentation. That pass is expiring.
If you’re an innovation executive at a GC, the focus should be on whether your organization has the right people in the right seats to make AI work. Look for the project engineer who keeps asking about your data infrastructure. The estimator who taught themselves Python to automate bid tabs. The PM who piloted three tools last year and has strong opinions about which one actually saved time. These are the people who will make the co-development model work, because they can translate between how the company operates and what the technology can do.
If you’re still treating AI as a conference topic, your firm will fall woefully behind. Companies that pair technically curious operators with vendor engineering teams, and give them the room to grind, will build something their competitors can’t copy because their specific operational knowledge is baked into their software.
It’s the greatest opportunity in construction technology in years and the people who chase status before results will get stuck. Be willing to be low-status for a while. It will follow the results. It always does.
This article is written by Victor Muchiri who runs strategic initiatives at BuildVision, where he leads GTM strategy for a construction network focused on MEP equipment procurement and financing. Before BuildVision, he spent time at Barton Malow on the strategy and business transformation teams and has experience on the lending strategy team at Upstart, a fintech lending platform. He started his career in the field with a degree in construction management from The Ohio State University and worked in the field for companies like Turner Construction. He writes about construction technology, construction strategy, and industry consolidation on his Substack, The Next Build.
 | A guest post by
|