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:
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.
