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.

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.

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.