What happens when AEC firms ban Claude because they don't know where their project data goes?

In this episode of KP Unpacked, KP Reddy and Nick unpack the regression happening across construction firms: people disconnecting Claude, companies banning enterprise AI tools, and employees carrying two laptops (work and personal) to keep building with tools their firms won't approve. A 3,000-person AEC firm just banned Claude entirely. The result? Everyone's using personal instances on company time, and the firm loses all institutional knowledge being built in those sessions.

But the deeper conversation is about IP anxiety in project-based industries. In AEC, there is no enterprise, the project is the enterprise. If you're a civil engineer on the Tesla factory and Tesla says "don't share our data with LLMs," how do you even comply when Claude's connected to your email? The answer: firms are hitting pause out of fear, not strategy. Meanwhile, KP delivered his first Zero RFI keynote at Building Transformations, and the feedback was split. Some GCs realized Zero's tools could drive risk to zero, which raises an existential question: if owners don't need insurance against risk anymore, why hire a general contractor?

Key questions answered:

• Why did a 3,000-person AEC firm just ban Claude entirely?
• What happens when employees carry two laptops to keep using AI tools their firms won't approve?
• How do you protect client IP when Claude's connected to your enterprise email?
• Why are AEC firms regressing on AI adoption instead of accelerating?
• What feedback did KP get from his first Zero RFI industry keynote?
• If Zero can drive project risk to zero, why do owners need general contractors?
• What are owner-controlled insurance policies (OCIPs), and why don't more people use them?
• Should firms invest $200/month per employee for enterprise Claude, or keep blocking it?
• Why do some firms still run on-prem Exchange servers instead of migrating to cloud?
• How do law firms handle attorney-client privilege when connecting email to LLMs?
• What's the difference between major muscle tissue (Procore, Autodesk) and connective tissue (Zero's tech stack)?
• Why is Microsoft Copilot "good enough" for 700K Accenture licenses but not for startups?

If you're an AEC firm struggling with data privacy policies while employees build workarounds, wondering whether blocking AI tools protects you or puts you further behind, or trying to understand what happens when risk mitigation becomes automated, this episode will force you to ask whether hitting pause feels safe, or just delays the inevitable.

Listen now.

What is it about watching a machine tape drywall that creates visceral discomfort in ways software automation never did?

In this episode of KP Unpacked, KP Reddy and Nick dissect the emotional response to physical AI versus digital AI. Nick's Okibo robotics video got 300K views and sparked a firestorm: half celebrating reduced construction costs, half horrified that "they're coming for the physical jobs too." The backlash reveals something deeper. People feel guilt about blue-collar displacement in ways they never did about white-collar knowledge work. Why? Because physical labor was supposed to be the fallback when AI took everything else.

KP counters with the mop thought experiment: would you pay your house cleaner more to scrub floors by hand without tools? Of course not. So why do we romanticize construction labor that breaks backs when better tools exist? The conversation moves from a software engineer quitting over AI coding adoption (identity crisis around lost craft) to whether nostalgia will create retro coding communities the way vinyl and Japanese stationery stores preserve analog experiences. Then they pivot to the scarcity flip: intelligence is now abundant and cheap, but transformers have 18-month backlogs. A startup building next-gen transformers would have been laughed out of Shadow Ventures three years ago. Today? Immediate funding.

Key questions answered:

• Why does watching robots do drywall create more outrage than software writing code?
• What happened when Nick posted an Okibo video that got 300K views?
• Would you pay your house cleaner more to scrub floors by hand without a mop?
• Why did a software engineer quit when his company adopted AI coding tools?
• What's the nostalgia equivalent for coding: vinyl, retro Game Boys, or Japanese stationery?
• Why do people feel more guilt about blue-collar job displacement than white-collar?
• What's scarce now: intelligence or physical materials like transformers and turbines?
• Why would a transformer startup get funded today but not three years ago?
• Will graphic designers be forced to monetize art on Substack instead of corporate gigs?
• Is there craftsmanship left in software engineering, or is that identity dead?
• Are we going to be arrested for driving cars in 20 years?
• What happens when physical labor stops being the economic fallback plan?

If you're grappling with why automation feels different when it's visible, wondering whether nostalgia creates business opportunities in a post-scarcity world, or trying to understand why transformer companies suddenly matter more than SaaS startups, this episode will challenge how you think about the emotional response to technology displacing human work.

Listen now.

What if tracking how much AI your team uses tells you more than tracking their hours?

In this episode of KP Unpacked, KP Reddy and Nick reveal a controversial management shift happening at Zero RFI: KP monitors enterprise Claude analytics and reaches out to employees with low token usage, not high spenders. The new performance metric isn't billable hours or output volume. It's curiosity, commitment to learning, and willingness to experiment. Someone burning through credits is building, iterating, testing limits. Someone avoiding the tools is resisting change. And if the CEO isn't in the top third of token usage on their team, they're failing at leadership.

The conversation unpacks Zero RFI's first internal hackathon: seven hours, cross-functional teams pulled out of silos, non-engineers shipping production code by end of day. One team built a preventative maintenance prediction system for a business they knew nothing about. Another deployed a Slack-to-Notion content aggregation engine an hour after presenting. The philosophy? More is better until better is better. Give people space, support, and freedom to build. Then track whether they're actually using it. Nick raises the scar tissue transfer problem: how do senior execs pass decades of decision-making lessons to junior associates without endless meetings? The answer lives in skills files, transcribed Notion calls, and treating Claude as a training partner, not just a task executor.

Key questions answered:

• Should you track employee token usage as the new performance metric?
• What happens when you reach out to low token users instead of high spenders?
• How did Zero RFI's internal hackathon work, and what did people build?
• Why is $30K/month in token spend an easy ROI decision for some CEOs?
• How do you transfer decades of institutional knowledge without one-on-one mentorship?
• What's the difference between using Claude for deliverables vs. training?
• Why are skills files the solution to IP leaving the building when employees quit?
• Should seed-stage CEOs be coding alongside their CTO or delegating?
• Why did PE firms decide San Francisco proximity matters more than New York headquarters?
• How do you codify scar tissue and lessons learned into persistent company memory?
• What should CEOs do if they're in the bottom third of their team's token usage?

If you're managing a team wondering whether to limit AI spend or incentivize experimentation, trying to scale institutional knowledge beyond senior leadership, or questioning what productivity measurement looks like when timesheets become irrelevant, this episode will reframe how you think about performance in an AI-first organization.

Listen now.