KP Unpacked

KP Reddy
  • 0,0 (0)
  • Entrepreneuriat
  • Chaque semaine

KP Unpacked explores the biggest ideas in AEC, AI, and innovation, unpacking the trends, technology, discussions, and strategies shaping the built environment and beyond. 

  1. 29 juin

    Stop Following the Lego Instructions

    What if teaching kids to complete the Millennium Falcon set is exactly what's making them unprepared for the real world? In this episode of KP Unpacked, KP Reddy and Nick unpack why AI reading drawings is a feature, not a company, why reindustrialization in Detroit changed how KP thinks about hard tech, and why the Lego analogy explains everything wrong with how we raise kids today. Original Legos were a mixed box of bricks with no instructions. You built whatever your imagination created. Modern Lego sets are Millennium Falcons with step-by-step instructions. Kids complete the set, lose their mind when a piece is missing, and never learn creativity. Sound familiar? College degree, job market, no pieces, losing their mind. KP takes that analogy into AI: reading drawings is spell check, not a bestseller. Everyone's building tools to "read plans and specs" and the head of pre-con 10 minutes from YC is telling his team these founders have no idea what they're doing every time they leave. The hard part isn't reading the door on a drawing. It's knowing whether you need three hinges, the right finishes, or the shim dimensions based on decades of inference. Then KP shares takeaways from Detroit's Reindustrialized conference: own your building, run your own machine shop, stop outsourcing prototypes to vendors who put you at the back of the line. Antonio Gracias (early Tesla, SpaceX investor) said it best: stop making three SKUs for mass production. Make 15 form factors, release faster, do more interesting things. Key questions answered: Why is AI reading drawings a feature, not a product or company?What's the difference between object detection and inference in construction drawings?Why does every stakeholder look at the same door on a drawing and see something different?What do original Legos teach kids that Millennium Falcon sets don't?Why are college grads losing their minds when pieces are missing?What should we actually be teaching kids instead of following instruction manuals?What happened at the Reindustrialized conference in Detroit?Why should hard tech founders own their buildings and machine shops?Why does outsourcing prototypes to manufacturers put you at the back of the line?What did Antonio Gracias say about nimble manufacturing versus mass production?Why do fewer SKUs and more frequency matter more than cost efficiency?Why is gaining understanding the actual goal of using AI tools?If you're building an AI drawing reading tool and calling it a company, wondering why hard tech funding requires a completely different playbook, or trying to figure out what creativity and imagination actually mean in an AI world, this episode will challenge every assumption about tools, skills, and what we're really solving for. Listen now.

    38 min

  2. 22 juin

    Vibe Coding Works, Vibe Robotics Doesn't

    Can you build a robot the same way you vibe code software? Not even close. In this episode of KP Unpacked, KP Reddy and Nick sit down with Guy German, CEO of Okibo, to unpack why programming motion control got 10x easier but building robots still requires years of field testing. Guy breaks down the three requirements for general-purpose construction robots: physical capability (reach, payload, battery life), tool flexibility (spray guns, rollers, power tools, dust collectors), and intelligence (real-time perception, work plan generation). Humanoids fail all three for construction. Chinese robots require pre-fitted BIM data that doesn't exist in reality. Okibo deploys on messy job sites with no prep, no perfect drawings, just LiDAR and situational awareness. The conversation moves from why construction has the highest suicide rate (cognitive overload plus physical toll) to why workers retire with permanent damage after 30 years (carpal syndrome, can't bend arms from overhead work). Guy shares a story: a veteran worked with Okibo robots for one week during a pilot. When it ended, he begged to keep the robot. His health improved that much. The insight? This isn't about productivity. It's about safety and empathy to the worker. Then they tackle why VCs forgot the venture part of venture capital. If you're showing a hardware prototype and the VC asks about traction, leave the meeting. They've disqualified themselves. Key questions answered: Can you vibe code a robot the same way you vibe code software?What are the three requirements for general-purpose construction robots?Why do humanoids fail all three requirements for construction work?How is the Chinese construction robotics approach different from Okibo's?Why does construction have the highest suicide rate of any industry?What happens to workers' bodies after 30 years of overhead drywall work?Why did a veteran beg to keep the Okibo robot after a one-week pilot?What's Okibo's data advantage from deploying across 3M square feet?Why is skilled labor shortage real (and getting worse)?What should you do if a VC asks for traction on a hardware prototype?Why is the capital stack the biggest impediment to construction robotics?Is physical AI the biggest technology wave of our lifetime?If you're building hardware and getting asked about traction, wondering whether robots can work without perfect BIM models, or trying to understand why safety and worker empathy matter more than productivity metrics, this episode will show you why the physical world is messier than code, and why that's exactly where the opportunity lives. Listen now.

    58 min

  3. 15 juin

    Water Is the Next Constraint After Data Centers

    What if the thing limiting AI growth isn't chips or power, but wastewater treatment capacity? In this episode of KP Unpacked, KP Reddy and Nick unpack why water infrastructure is the next bottleneck. Jacobs has a $22.7B backlog weighted toward water. AECOM intends to double its water business in three years. Stantec's water practice is its single largest vertical. Meta just built a $70M wastewater plant in Idaho. TSMC broke ground on a 15-acre water reclamation facility in Phoenix targeting 90% recycling. The CHIPS Act, EV gigafactories, and hyperscaler water-positive commitments are pulling wastewater treatment capacity onto private campuses at a scale AEC hasn't seen since the petrochemical buildout of the 70s. KP and Nick reveal Shadow's bet in the space: Western Chemicals, which uses duckweed (a plant that doubles in size every 24 hours) grown on wastewater to filter nitrogen and phosphorus while producing ethanol fuel. The insight? Wastewater treatment consumes 2% of global electricity using heavy machinery to do what biology does for free. Then they pivot to why big ideas need big capital (raising $1M for pre-con AI versus $100M for modular wastewater plants), why college grads complaining about no job offers have recency bias ($250K signing bonuses for 22-year-olds was never normal), and why skepticism from engineering firm LPs is actually an anti-signal Shadow should lean into. Key questions answered: Why is water the next infrastructure constraint after data centers and power?What's Shadow's water infrastructure bet, and what is duckweed?How does duckweed double in size every 24 hours and filter wastewater for free?Why does wastewater treatment consume 2% of global electricity?Why are private companies building their own wastewater plants now?Should founders raise $1M seed rounds or $100M for big infrastructure ideas?Is the college grad job crisis real, or just recency bias from the 2010s?Why is skepticism from engineering LP firms an anti-signal for Shadow?What's the difference between alpha (non-consensus bets) and beta (consensus with upside)?How does Founders Fund operate with only 4 partners managing billions?What happened with the Vinod Khosla/Cloudflare co-founder drama?Why do co-founder breakups kill more startups than bad products?If you're wondering where infrastructure investment flows after data centers, trying to understand why wastewater suddenly matters, or deciding whether to raise incrementally or swing for $100M on a big idea, this episode will show you why the next constraint is already visible, and capital is moving faster than you think. Listen now.

    49 min

  4. 8 juin

    Your Edge Case Is Someone Else's Use Case

    What if the detail that seems trivial to you is the constraint keeping the entire project from moving forward? In this episode of KP Unpacked, KP Reddy sits down with Dr. Barry Clark, CTO of Zero RFI, to unpack why construction projects fail on details nobody thought mattered. A structural beam seems simple: read the line on the drawing, spec the size, done. But the client needs the longest span possible without custom manufacturing (adds cost). The superintendent needs to know when the truck leaves to avoid traffic (adds delays). The permitting team worries about wide-load requirements (adds 90 days). The building supplier tracks lead times and availability. Same beam. Five different perspectives. All mission-critical. The edge case you dismiss is someone else's everyday constraint. Barry explains why AI's real unlock isn't automating standardized workflows (McDonald's already perfected that). It's mass customization at scale. Every persona on a project looks at the same drawings and sees different risks. AI can now hold all those perspectives simultaneously and optimize for all of them. The conversation also reveals why companies are having a "Facebook moment" with AI (deployed it everywhere, now realizing they don't understand privacy), the three-tier consulting model emerging (billable hours get worst talent, equity gets best), why programming got easy and that's actually good, and why Zero's training spends two-thirds of its time on mental models instead of AI mechanics. Key questions answered: Why do construction projects fail on edge cases nobody thought were important?What's the structural beam example that shows five different perspectives on the same detail?How does AI enable mass customization instead of McDonald's-style standardization?What's the corporate "Facebook moment" happening with AI deployment right now?Should you go deep on one AI technology or broad across all of them?What are supply chain attacks, and how should executives test their IT teams?What are the three tiers of AI consulting: billable hours, risk fees, or equity?Why did one consulting firm charge $5M but generate $500M in client outcomes?Do employees own their skills files when they leave, or does the company?Why did some software engineers quit when their companies adopted AI coding?What's the difference between LLMs, VLMs, and physics-informed neural networks?Why does Zero's training curriculum focus on thinking frameworks instead of tool mechanics?If you're an engineer dismissing client requests as edge cases, a project manager wondering why small details derail schedules, or trying to understand why AI matters more for customization than standardization, this episode will show you that everyone's edge case is equally critical to project success. Listen now.

    46 min

  5. 1 juin

    Choose Your Team, Not Just Your Tools

    What if the next five years of your career isn't defined by which AI you use, but by who you're working with? In this episode of KP Unpacked, KP Reddy and Nick unpack the quiet revolution happening in management consulting. OpenAI just launched a deployment company and acquired a consulting firm. Anthropic is backing enterprise AI consultancies. PE firms are partnering with AI-enabled consultants and offering equity instead of hourly fees. The result? Three tiers of value capture emerging: billable hours (worst talent), risk-based fees (middle tier), and equity models (where the best people go). If you're still getting paid by the hour to do AI transformation work, you're in the bottom tier. But the deeper insight is about career trajectory. KP argues the next five years aren't defined by how good your Claude skills are. They're defined by who you're sitting next to. Are you in a firm where Opus 4.8 launching makes everyone's Slack light up with memes and excitement? Or are you somewhere people still think AI is a threat? The gap between those two environments is the gap between relevance and obsolescence. The conversation also unpacks skills files as potentially employee-owned IP (not company-owned), why structural engineers still double-check software calculations in Excel despite working for billion-dollar firms, and why Zero's training program spends two-thirds of its time on mental models and thinking frameworks, not AI mechanics. Key questions answered: Why are OpenAI and Anthropic launching consulting practices and partnering with PE firms?What are the three tiers of value capture in AI consulting (billable hours, risk fees, equity)?Where does the best consulting talent go: hourly billing or equity models?Do you own your skills files, or does your company?Should companies make employees sign IP agreements for marketing coordinators building AI workflows?Why do structural engineers still double-check software calculations in Excel?What's Zero's training curriculum focused on: AI tools or thinking frameworks?Why does ambition and optimism matter more than technical AI skill?How should you choose between working at a forward-leaning AI firm versus a traditional one?What happens when Opus 4.8 launches: does your team's Slack light up or stay silent?Why would you sell a $250M/year AI consulting firm when you're banking $50M annually?What's Ramp tracking now: token spend by industry?If you're deciding between firms based on AI adoption, wondering whether your skills files are actually your IP, or trying to figure out whether billable hours still work in an AI-enabled consulting world, this episode will make you realize the technology matters less than the ambition and optimism of the people around you. Listen now.

    52 min

  6. 11 mai

    The Data You Share Is the Advantage You Lose

    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.

    53 min

  7. 4 mai

    Why Robots Spark More Outrage Than Digital AI

    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.

    56 min

  8. 20 avr.

    Token Utilization Is the New Timesheet

    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.

    51 min
Tout afficher (117)

À propos

KP Unpacked explores the biggest ideas in AEC, AI, and innovation, unpacking the trends, technology, discussions, and strategies shaping the built environment and beyond. 

Informations

  • Création
    KP Reddy
  • Années d’activité
    2020 - 2026
  • Épisodes
    117
  • Classification
    Tous publics
  • Copyright
    © 2026 KP Unpacked
  • Site web de l’émission
    KP Unpacked

Vous aimeriez peut‑être aussi