Wired to Build

Why does construction technology keep landing wrong — even when the tools are better than they've ever been?

Jeff Sample has spent years traveling the industry as a host of the ConTech Crew and, more recently, as head of global industry strategy at Bluebeam. He's been in more contractor offices, job site trailers, and conference rooms than almost anyone in the construction technology space — which gives him a rare view of how technology actually behaves inside real companies and real teams.

In Part 1, Jeff and Nick cover:

• How Jeff's path from IT architect to ski resort technologist to construction tech leader shaped how he reads the industry
• Why people, process, and technology have to happen in that order — and what breaks when they don't
• The shift from evangelist to facilitator: why you can't preach adoption and what actually creates room for change
• What the industry gets wrong about RFIs — and what that reveals about how we handle expertise and risk

Part 2 picks up where this leaves off: culture beyond the company, grassroots adoption versus leadership alignment, and what it means to build an industry that's greater than the sum of its parts.

Support the show!

• Make sure to like, subscribe, and share your thoughts.
• Visit our founding sponsor at www.avicado.com

Most conversations about AI in construction focus on what the tools can do. This one focuses on what it actually takes to use them.

Marcus Turner has been building with AI tools in real construction and knowledge-work contexts for years. He is not predicting the future of AI. He is living in the present tense of it.

In this conversation:

• Why domain knowledge is the multiplier and AI only amplifies what you already understand
• What "context engineering" means and why most people are still using AI like a search engine
• How builders can start experimenting today without feeling like they are already behind
• What a personal AI agent stack looks like when someone actually builds one

The industry is not short on AI opinions. It is short on people who have gotten their hands dirty with it. Marcus is one of them.

Most conversations about construction technology focus on what the tools can do. This one focuses on what they actually do — to the people using them.

Rob Sloyer is VP of Innovation and Strategic Services at KAST Construction, a Florida-based multifamily builder with over two decades building at scale. He's been close to BIM since before most companies knew how to spell it — and he's watched enough hype cycles to know that technology without purpose doesn't just fail to help. It actively makes things worse.

In this conversation:

• Why BIM shifted problems earlier in the process instead of eliminating them
• The three-part test for whether a tool actually belongs in the work
• What AI adoption is getting wrong — and why it's hitting the same walls as every wave before it
• The workforce shortage, rework as a safety multiplier, and why the field pushes back

We never have time to do it right, but we always find time to do it again. This conversation is about changing that.

Last week on site, a quality program manager said something I can’t shake:

“The work isn’t done until it’s documented.”

In this first Field Note, I unpack what that actually means — not as paperwork, but as protection.

When documentation is embedded in the act of building, it changes behavior. It protects craftsmanship. It reduces rework. And it shifts QA/QC from a phase at the end to a design decision at the beginning.

This isn’t about binders.
It’s about building work that’s defensible.

Field Notes are short dispatches from the field — observations from job sites and real conversations across the industry.

If you’re in construction, ask yourself:

Is documentation something you assemble later — or something designed into the way you work?

Wired to Build is supported by Avicado — helping owners and project leaders design smarter systems for capital programs.

Season 3 of Wired to Build begins with a foundational idea:

You can’t improve what you don’t first understand.

In this episode, Nick Caravella is joined by Matthew Byrd, founder of Reality Capture Network, to explore how clarity in the field shapes better decisions across construction, infrastructure, and technology.

Together, they discuss:
– Why understanding reality as it actually exists is the starting point for improvement
– How reality capture has evolved from niche tools to critical infrastructure
– The role of trust, standards, and shared data in technology adoption
– Workforce enablement and why tools should elevate—not replace—people
– What the future of digital twins and connected systems really looks like

Season 3 focuses less on hype and more on the systems, people, and decisions that hold up when the stakes are real.

🎧 If you’re building in complexity and care about getting things right, this episode sets the tone for what’s ahead.

Additional 🔗:

Founding Sponsor: Avicado

Reality Capture Network Conference: RCON2026

🔍 Episode Summary

In part 2 of this month's episode, host Nick Caravella and Kyle Majchrowski dive into the theme of curiosity—a foundational topic from Kyle’s book Powerful Conversations.

Together they explore how curiosity shapes leadership, project delivery, and personal growth. What begins as a question—“what does curiosity really mean?”—unfolds into a workshop-style dialogue on learning, vulnerability, and slowing down under pressure.

This episode brings the Wired to Build story arc full circle: understanding how to create systems that empower people to think differently, lead authentically, and stay curious even in high-stakes environments.

👤 Guest Bio

Kyle Majchrowski is a leadership coach, author, and founder of Ripple Intent, a nonprofit dedicated to improving communication and collaboration in the built-environment industry.

After decades spanning subcontractor, GC, and owner roles—including work with Banner Health—Kyle now helps teams master the art of powerful, people-first conversations.

• Curiosity is the courage to ask what if—to explore possibilities without demanding immediate answers.

• Environments that reward speed and certainty often suppress curiosity; leaders must create space for “slow-down moments.”

• Asking questions from a place of not knowing builds trust and psychological safety across teams.

• Fear of failure and imposter syndrome can shut down curiosity—especially when cultures punish mistakes.

• Curiosity in leadership is as much about permission-giving as it is about inquiry: inviting others to think, test, and learn.

• Slowing down can accelerate progress; taking time to reflect often leads to better, faster decisions later.

🔗 Resources

• ⁠Get the book, Powerful Conversations

• Join the Ripple Intent Community

• ⁠Sign up for the Avicado Toast Newsletter

🔍 Episode Summary

In this episode, host Nick Caravella welcomes Kyle Majchrowski, author of Power Full Conversations: How to Talk About What Matters Most in Work and Life.

Kyle’s journey from subcontractor to owner-side leader shaped his belief that connection—not compliance—drives project success. Together, Nick and Kyle explore how empowering people to shape their own systems creates stronger teams and healthier capital programs.

From “don’t forget about us—the people” to gratitude, trust, and curiosity, this conversation is a reminder that the most powerful tools in construction are still human.

👤 Guest Bio

Kyle Majchrowski is a leadership coach, author, and founder of Ripple Intent, a nonprofit fostering meaningful dialogue across the built-environment industry.
With decades of experience spanning subcontractor, GC, and owner roles—including work with Banner Health—Kyle helps teams strengthen connection and navigate high-stakes conversations with empathy and intention.

• Empowering project teams to define how they work builds engagement and accountability beyond any “best practice.”

• Meetings should have meaning—define why and how before you calendar when.

• Gratitude builds culture when it recognizes behavior + impact, not just manners.

• Trust begins with self-awareness; understand your wiring before expecting alignment.

• Get the 📖 Powerful Conversations

• Join the Ripple Intent Community

• Sign up for the Avicado Toast Newsletter

🔑 Episode Summary:

Welcome back to Wired to Build, a data-driven, technology-focused podcast digging into how building owners and operators use technology to manage the full lifecycle of their projects.

In Part 2 of our conversation with ⁠Jamie Lynn Cooke⁠, we move beyond AI hype and dig into what responsible implementation actually looks like. We unpack the differences between procedural software and probabilistic AI, break down high-risk use cases, and explore how to balance autonomy and oversight in capital project environments.

From Air Canada's now-famous chatbot lawsuit to jobsite automation risks, this episode is a must-listen for anyone serious about integrating AI while protecting people, brand, and bottom line.

If Part 1 was the why, this is the how.

🧠 Key Takeaways:

• AI ≠ Traditional Code: AI doesn't repeat exact outcomes. Understanding the difference between procedural and probabilistic systems is essential.

• Governance is Risk Strategy: Good governance isn't red tape—it's how you decide where you're willing to fail.

• Real-World Risk Examples: Air Canada’s chatbot cost them in court. The lesson? If your logo is on it, you own it.

• Human-in-the-Loop vs Human-on-the-Loop: Knowing the right level of oversight is key to safe AI augmentation.

• Not All Productivity Is Equal: Gains that cause rework or liability later aren’t productivity wins.

• Cautious Optimism > Blind Adoption: Move fast with purpose, not without a plan.

🗣️ Shareable Quotes:

“AI doesn’t fail like humans—it fails confidently. That’s the danger.” – Jamie Lynn Cooke

“Governance isn’t red tape. It’s how you decide where you’re willing to fail.” – Nick Caravella

“If your logo is on the AI, you’re liable for what it says.” – Jamie Lynn Cooke

“Cautious optimism doesn’t mean moving slowly—it means moving with discipline.” – Nick Caravella

“You can’t sue an algorithm—but you can sue the company behind it.” – Jamie Lynn Cooke

🔗Links to reference for more:

• Jamie Lynn Cooke's publisher page: ⁠⁠https://www.amazon.com/stores/author/B0054HB0I0⁠⁠
• Jamie Lynn Cooke's new book, AI Firing Freeze: ⁠⁠https://aifiringfreeze.com/⁠⁠
• The Marketing Artificial Intelligence Institute: ⁠⁠https://www.marketingaiinstitute.com/⁠⁠.

🔑 Episode Summary:

Welcome to Wired to Build, a data-driven, technology-focused podcast digging into how owners and operators use technology to manage the full lifecycle of their projects. In this guest introduction episode, host Nick Caravella sits down with Jamie Lynn Cooke—an author, consultant, and educator who's helped organizations transform big ideas into operational reality.

We explore Jamie Lynn Cooke’s evolution from software tester to change agent, uncovering her early interest in usability, systems thinking, and business process optimization. Jamie Lynn Cooke reveals how her journey led her to apply Agile beyond software and into enterprise-wide strategy. With a clear-eyed view of today’s AI hype cycle, Jamie Lynn Cooke warns against "cartoon dollar signs" and makes the case for governance, not chaos, in the age of automation.

This episode lays the foundation for the next one, where we dig deeper into AI governance and how to navigate the risks of rapid adoption.

👤 Guest Bio:

Jamie Lynn Cooke is an author, consultant, and educator focused on operationalizing innovation. She brings Agile methodology out of its software silo and into enterprise strategy, helping organizations improve productivity without sacrificing quality. Her latest work tackles the realities of AI transformation, focusing on responsible adoption and the human implications of automation.

🧠 Key Takeaways:

• Productivity ≠ Hours Worked: Jamie Lynn Cooke redefines productivity by how much value is delivered—not how many hours are logged.

• Agile Isn’t Just for Software: Agile can—and should—be applied across business functions, from marketing to operations.

• Beware of Cartoon Dollar Signs: Organizations often rush into AI with unrealistic cost-saving dreams and unclear directives.

• Entry-Level Isn’t Optional: Eliminating entry-level jobs in favor of AI jeopardizes the future talent pipeline.

• • Governance Empowers, Not Restricts: True AI governance creates frameworks and guardrails that allow teams to innovate safely.

  
  

  Links to reference for more:

  • Jamie Lynn Cooke's publisher page: https://www.amazon.com/stores/author/B0054HB0I0
  • Jamie Lynn Cooke's new book, AI Firing Freeze: https://aifiringfreeze.com/
  • The Marketing Artificial Intelligence Institute: https://www.marketingaiinstitute.com/.

Welcome to Wired to Build, a data-driven, technology-focused podcast digging into how owners and operators use tech to manage the full life cycle of their projects.

In this episode, we’re joined by Itzik Malka, CEO and co-founder of 4M Analytics, who is building the first centralized subsurface utility database—a Google Maps for what’s underground.

We explore:

• Why utility data today is unstructured and unreliable

• How AI and image science can map utilities without digging

• Use cases from DOTs, engineering firms, and infrastructure owners

• The future of digital twins, permitting, and predictive analytics

If you've ever seen spray paint on a sidewalk and wondered what’s below—you’ll want to listen.

🔗 Learn more at 4manalytics.com
📥 Subscribe and sign up for the Avicado Toast newsletter
🎯 Share with a friend who’s Wired to Build