KP Unpacked

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.

What happens when speed to completion collapses from quarters to days, and your planning cycles become obsolete overnight?

In this episode of KP Unpacked, KP Reddy and Nick process life after the Zero RFI launch while unpacking why every startup metric that mattered five years ago just became irrelevant. From PE firms opening San Francisco offices because "you can't remote control this from New York" to one company going from $1M to $61M ARR in six months, the conversation reveals why ARR, CAC, LTV, and 30-60-90 day plans are all anchored to a time domain that no longer exists.

KP argues repeatable process is the fastest path to mediocrity when Claude can generate specialized workflows on demand. Why optimize for quarterly goals when proof-of-concept to revenue can happen in a week? Why build sales pipeline methodology when the only metric that matters is cash trending up or down? Nick counters with the shift happening in venture diligence: Craft Ventures' SaaS formula (meet these metrics, get funded) is dead, Workday's CTO just quit to be an individual contributor at Anthropic, and services businesses are suddenly attractive again because institutional knowledge stays in the AI, not employees' heads.

Key questions answered:

• Why are PE firms rushing to open San Francisco offices after decades in New York?
• How did one company go from $1M to $61M ARR in six months?
• Is the triple-triple, double-double SaaS growth formula dead?
• Why did Workday's CTO quit to be an engineer at Anthropic?
• Should founders still obsess over ARR, or is that metric obsolete?
• Why is repeatable process now the fastest path to mediocrity?
• What happens when proof-of-concept to revenue takes days instead of quarters?
• Are 30-60-90 day plans anchored to a time domain that no longer exists?
• Why are PE firms suddenly excited about services businesses again?
• Should you measure sales pipeline metrics, or just refresh your bank account?
• How does institutional knowledge stay in AI instead of leaving with employees?
• Why is KP anti-process now after writing an entire book about optimization?

If you're still planning in quarters while competitors ship in days, tracking vanity metrics instead of cash, or wondering why your playbook from 2020 feels obsolete in 2026, this episode will force you to ask whether your time domain is calibrated to reality, or anchored to a world that already moved on.

Listen now.

What happens when everyone's AI agents start talking to each other—and you're stuck without any?

In this episode of KP Unpacked, KP Reddy and Nick process the Zero RFI launch aftermath - from 3,500 resumes in 24 hours to a top-tier VC introducing themselves like KP's never heard of them. But the real conversation pivots to what happens when everyone deploys AI agents: cognitive overload, the spy-vs-spy escalation of automation, and why construction's suicide crisis gets worse when information flows faster but judgment disappears.

KP breaks down why engineering firms are drowning in RFIs that should just say "read the damn drawings" (but legal won't allow it), why text messages with no context create work handoffs disguised as communication, and why the people automating everything on X probably don't have real jobs. Nick counters with diligence innovation—using Claude Code for VC code review, building Slack analysis tools to measure founder leadership styles, and whether term sheets should include MCP server access to accounting systems. The through-line? Defense agents, offense agents, and the realization that humans should only handle judgment and exceptions—but the magnitude of those decisions just went exponential.

Key questions answered:

• What was KP's favorite response to the Zero RFI launch announcement?
• Why did a top-tier VC introduce themselves like KP's never heard of them?
• How many resumes did Zero RFI receive in the first 24 hours?
• Should VCs use Claude Code for startup code review during diligence?
• Can you measure founder leadership style by analyzing their Slack history?
• Should term sheets include information rights to connect MCP servers to bank accounts?
• Why are engineering firms drowning in cognitive overload from RFIs?
• What happens when everyone's AI agents start responding to everyone else's agents?
• How do you separate real AI demos on X from complete fabrications?
• Why is construction robotics funding only $1.78B total—and is that enough?
• What's the right business model for robotics: sell machines, lease them, or become a subcontractor?
• Should robotics companies target OEM distribution partners like Milwaukee Tools?

If you're drowning in notifications wondering when AI actually helps, a VC trying to figure out what diligence looks like in 2025, or a founder posting fake demos on X hoping no one notices, this episode will force you to ask whether your agents are creating leverage—or just more work for someone else's agents to handle.

Listen now.

What happens when a VC flips to the founder side and raises $13.8M to fix the biggest broken relationship in construction?

In this episode of KP Unpacked, KP and Nick finally reveal what's been hiding in plain sight across 20+ podcast episodes: Zero RFI, KP's human-first AI-scaffolded platform company purpose-built to modernize the construction industry at scale. After spending two years in conversation with General Catalyst – not shopping decks, just iterating on conviction – KP was handed $13.8M and a mandate to solve the asymmetry of information that leaves owners helpless: architects billing by the hour, contractors burying change orders in in 400-notifications floods, and buildings delivered 80% over budget.

The reveal unpacks everything: why Zero RFI and why now? why Zero RFI isn't SaaS (it's people backed by AI toolboxes), why scaling means buying 50-person firms rather than chasing enterprise sales, and why the owner's rep model is the only position with enough leverage to actually drive industry change. KP breaks down why BIM failed owners 15 years ago, why most construction projects run 80% over budget (McKinsey data, not hyperbole), and why his biggest technical risk is Anthropic releasing features that render what his team just built obsolete. The through-line? Technology has created deflation in virtually every other industry – construction remains the exception, and Zero RFI might finally be the answer.

Key questions answered:

• How did KP raise $13.8M from General Catalyst without shopping pitch decks?
• What does "human-first AI scaffolding" actually mean for an owner's rep?
• Are most construction projects really 80% over budget?
• Why do owners suffer from information asymmetry against their own vendors?
• How does Zero RFI scale—buying companies or SaaS sales?
• How does Zero RFI become distribution for Shadow Ventures portfolio companies?
• Can you actually break the billable hour model in AEC?

If you're an owner tired of 80% budget overruns and zero accountability, a VC wondering what happens when your partner becomes a founder, or a startup trying to crack owner distribution, this episode reveals the playbook for leveraging AI scaffolding to fix construction's most broken relationship.

Listen now.

What if the biggest crisis in construction isn't AI adoption, it's that we hand over $100M assets with no instruction manual?

In this episode of KP Unpacked, KP Reddy sits down with David Niewiadomski, former Turner Construction executive turned Shadow Ventures operator, to answer a haunting question: if your building could talk, what would it say? The answer isn't pretty. "You don't do scheduled maintenance. You didn't check the caulk joints before the warranty expired. You take me for granted." Dave spent 17 years in the contractor trenches, pre-con, estimating, project management, and walked away to solve the data handoff problem that makes every asset transfer feel like buying a car with no owner's manual.

The conversation weaves between tactical AI workflows (how to automate bid leveling in two weeks, why Claude told KP he was "out of his depth" and should call Barry) and systemic industry failures. Why do cars come with organized manuals regardless of manufacturer, but $100M buildings get handed over with incomplete data scattered across expired Procore servers? Why don't architects visit existing hospitals before designing new ones? Why do facilities teams get involved after walls are already placed? And why, when KP's uncle kept every oil change receipt in a three-ring binder to maximize car resale value, don't we track building maintenance the same way?

Key topics covered:

• Why IT departments are the #1 barrier to AI adoption, not capability, cost, or interest, just permissions
• How Dave would automate bid leveling in two weeks using Claude Cowork if corporate let him tinker
• Why pre-con departments are perfect AI targets: small teams, high expertise, Excel-heavy workflows
• The moment Claude told KP to escalate to Barry because he was out of his depth—and what that means for mentoring juniors
• If your building could talk: "40% of my caulk joints are cracking and my exterior warranty just expired"
• Why cars have consistent owner's manuals but $100M buildings don't, the automotive vs. construction data gap
• How organized building data determines which deals asset managers skip during due diligence
• The CapEx vs. OpEx disconnect: design teams optimize construction cost, ignore 20-year maintenance nightmares
• Why facilities teams review drawings after decisions are locked and walls are already placed
• The hospital prototype problem: architects don't visit 50 existing hospitals to learn what breaks and what costs too much
• Why grocery store GMs kept selling corporate-spec'd deli coolers on eBay, and corporate couldn't update specs fast enough
• How technology creates deflation everywhere (Blockbuster to Netflix, $20 CDs to Spotify), except construction
• Why RFIs and change orders eat 10-20% of contract value, and AI's first impact will be waste reduction, not bid prices
• Whether contractors will pass 30-40% AI cost savings to owners (answer: no, they'll pocket it until competition forces pricing down)
• Why mid-sized GCs will adopt AI faster than Turner, fewer people, less federal red tape, more agility
• The union robotics challenge: layout robots worked in NYC, but full automation requires labor negotiation
• Why institutional knowledge walks out the door with employee turnover, and Procore data disappears when subscriptions end
• The three-ring binder standard: why we track car maintenance for resale value but not $100M building systems

If you're an owner frustrated by incomplete building handoffs, a contractor wondering where AI automation starts, or a facilities manager tired of inheriting broken systems with zero documentation, this episode will make you realize the problem isn't innovation, it's that we never solved basic organization.

Listen now.

If contractors get 50% more efficient with AI, who captures the margin improvement?

In this episode of KP Unpacked, KP Reddy and Nick tackle a question that went viral in construction circles: with all these AI companies raising capital to serve contractors, will owners and developers actually see lower costs? Or will GCs pocket the efficiency gains and maintain pricing power? The conversation spirals into economic theory, prisoner's dilemma dynamics, and why the WebMD playbook might predict construction's AI future.

But the deeper thread is about what happens when an entire conservative industry, one built on stability, 401Ks, and predictable careers, gets blindsided by deflationary technology moving too fast to adapt. KP shares observations from an M&A conference where 200 AEC executives think AI is "ChatGPT helping me pack for trips," while tracking former firm owners coming off PE non-competes who could launch AI-native competitors overnight. Nick introduces a viral economic report painting a bleak 2028 scenario where AI delivers on all its promises but unemployment hits 10.2% and the S&P drops 40%.

Key topics covered:

• Why construction AI companies target contractors, not owners, and who captures the ROI when margins improve
• The prisoner's dilemma: will a mid-market GC defect and pass savings to clients to win volume?
• How one multifamily GC is guaranteeing outcomes by controlling supply chains and offering territory exclusivity
• The WebMD precedent: doctors used it first, then consumers took control, will owners do the same with AI?
• Why 200 M&A conference executives had no idea what's happening in AI beyond trip-planning with ChatGPT
• The 2028 economic doomsday scenario: AI succeeds, unemployment hits 10.2%, S&P drops 40%, software companies collapse
• Why the rate of AI advancement is too fast for human adaptation, six Claude updates since January 12th
• How KP is tracking former AEC firm owners coming off PE non-competes using Claude Cowork 24/7
• Why IT departments are the biggest barrier to AI adoption in conservative firms
• The "Friday AI Day" thesis: carve out four hours every Friday to tinker instead of leaving early
• Why KP's 70-year-old brother-in-law (retired physician) wants to learn coding to pre-screen insurance denials
• The opposite of Y Combinator: an incubator in Costa Rica for retired people who want to build AI startups
• Thought experiment: 60-year-old contractor with hand tools vs. 35-year-old with power tools at identical pricing
• Why experience + AI tools is the winning combination and what it means for next-generation knowledge workers
• The impossible prediction: what jobs will exist for kids born in 2020?

If you're a contractor wondering whether to pass AI savings to clients, an owner trying to figure out when pricing pressure arrives, or a knowledge worker in a conservative industry watching the future unfold too fast, this episode will challenge every assumption about who wins when technology moves faster than adaptation cycles allow.

Listen now.

Why are corporate knowledge workers structurally prohibited from learning the most important skill of the decade?

In this episode of KP Unpacked, KP Reddy sits down with Nona Black, Head of People, to unpack why hiring 36 people feels harder than running 36 Mac minis with Claude Cowork and why that's both a joke and a serious question. From Delta Airlines innovation leadership to startup chaos, Nona brings the corporate perspective on what happens when IT departments become the biggest barrier to workforce evolution.

The conversation spans the tactical (how Claude holds your ADHD thoughts while you context-switch), the structural (why engineers need to collapse into product roles and talk to customers), and the philosophical (should we expect new hires to show up AI-fluent, or is that unfair?). KP argues that medium-level AI competency means you've automated something frustrating in your workflow not just asked ChatGPT about the weather. Nona counters that most people in corporate America don't have access, incentive, or permission to build that skill, which creates a massive disadvantage for anyone not in a startup environment.

Key topics covered:

• Why managing people is harder than managing AI agents and why that's both true and not the point
• How Claude Cowork helps ADHD superpowers: holding half-finished tasks while you context-switch and come back later
• The expert generalist thesis: AI tools are making everyone capable of cross-functional work without formal training
• Why KP tells architects to keep IT out of the room if they want to make progress on AI adoption
• The three A's of knowledge work: Attitude, Aptitude, and Access and why access is the limiting factor in corporate America
• Why engineers need to collapse into product roles and learn customer empathy, not just coding mechanics
• The middle ground of AI competency: automating frustrating workflows, not just asking questions Google can answer
• Why Claude asked KP if he wanted to pay for data aggregation services or go straight to free public sources
• How to evaluate AI fluency in hiring: have they built an agent, automated a task, or just used ChatGPT for trip planning?
• Why solo entrepreneurship is more appealing now than ever, you don't need 17 people to fill 17 roles anymore
• The sandbox problem: corporate risk tolerance vs. giving employees freedom to tinker and experiment
• Why offshore development teams struggle to build good software, they're not living the customer's life
• How Claude gives real-time feedback on KP's fiction writing: "This chapter doesn't make sense, are you coming back to this?"

If you're a knowledge worker wondering whether to stay in corporate or jump to a startup, a leader trying to figure out how to hire for AI fluency, or an IT department blocking progress in the name of risk management, this episode will challenge how you think about access, aptitude, and the future of work.

Listen now.

What matters after decades of building, losing, and rebuilding?

In this episode of KP Unpacked, KP Reddy turns 55, and Nick uses the milestone for a lightning round conversation exploring career highs, crushing losses, and the philosophy that's shaped three decades of entrepreneurship. From living in a truck eating 19-cent tuna to running a VC fund, KP reflects on the moments that actually stuck and why they weren't the trophy wins.

The conversation moves between tactical and existential. KP explains how Claude Cowork is now his nurse practitioner (drafting insurance appeals, scheduling appointments, analyzing x-rays), why he runs four Mac Studios doing different jobs while he unpacks office furniture, and why the future of CRM is taking people to lunch instead of data entry. But the deeper thread is about identity: why his worst fear (going back to zero) doesn't actually scare him, why his family has more confidence in him than he has in himself, and why the 2008 financial crisis validated the self-doubt that still drives him today.

Key topics covered:

• Why KP spent his 55th birthday at the DMV after his assistant cleared his calendar without asking
• How Claude became his healthcare coordinator and delivered better emotional support than his mom
• The blank slate moment after his first exit paying off the house and feeling peace, not accomplishment
• Living in a truck with sleeves of tuna and stolen mayo packets and why going back doesn't scare him
• The 2008 crisis, personal guarantees, and why losing everything validated his lack of confidence
• Why "celebrating small wins" is for people not building unicorns assume wins, magnify losses
• Vibe working: running four Mac Studios with Claude Cowork while doing manual labor he actually wants to do
• Why relationship-driven CRM beats software: take engineers to lunch after RFP meetings, not Salesforce data entry
• The manager vs. maker schedule and why KP operates at sprint speed with no please-and-thank-yous
• Morning meditation as leadership: visualizing every founder and team member's context before the workday
• Why one founder said "I can feel when you're praying for me" and what that reveals about leading mission-driven teams
• The 10-year goal isn't three private jets, it's building community where all LPs are former founders who exited and came back

If you're navigating what success looks like after the wins, trying to lead without micromanaging while operating at full speed, or wondering whether your worst-case scenario is actually that bad, this episode will reframe how you think about ambition, fear, and what matters most.

Listen now.