Episodes
-
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.
-
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.
-
Missing episodes?
-
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.
-
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.
-
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 permissionsHow Dave would automate bid leveling in two weeks using Claude Cowork if corporate let him tinkerWhy pre-con departments are perfect AI targets: small teams, high expertise, Excel-heavy workflowsThe moment Claude told KP to escalate to Barry because he was out of his depth—and what that means for mentoring juniorsIf 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 gapHow organized building data determines which deals asset managers skip during due diligenceThe CapEx vs. OpEx disconnect: design teams optimize construction cost, ignore 20-year maintenance nightmaresWhy facilities teams review drawings after decisions are locked and walls are already placedThe hospital prototype problem: architects don't visit 50 existing hospitals to learn what breaks and what costs too muchWhy grocery store GMs kept selling corporate-spec'd deli coolers on eBay, and corporate couldn't update specs fast enoughHow technology creates deflation everywhere (Blockbuster to Netflix, $20 CDs to Spotify), except constructionWhy RFIs and change orders eat 10-20% of contract value, and AI's first impact will be waste reduction, not bid pricesWhether 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 agilityThe union robotics challenge: layout robots worked in NYC, but full automation requires labor negotiationWhy institutional knowledge walks out the door with employee turnover, and Procore data disappears when subscriptions endThe three-ring binder standard: why we track car maintenance for resale value but not $100M building systemsIf 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 improveThe 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 exclusivityThe 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 ChatGPTThe 2028 economic doomsday scenario: AI succeeds, unemployment hits 10.2%, S&P drops 40%, software companies collapseWhy the rate of AI advancement is too fast for human adaptation, six Claude updates since January 12thHow KP is tracking former AEC firm owners coming off PE non-competes using Claude Cowork 24/7Why IT departments are the biggest barrier to AI adoption in conservative firmsThe "Friday AI Day" thesis: carve out four hours every Friday to tinker instead of leaving earlyWhy KP's 70-year-old brother-in-law (retired physician) wants to learn coding to pre-screen insurance denialsThe opposite of Y Combinator: an incubator in Costa Rica for retired people who want to build AI startupsThought experiment: 60-year-old contractor with hand tools vs. 35-year-old with power tools at identical pricingWhy experience + AI tools is the winning combination and what it means for next-generation knowledge workersThe 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 pointHow Claude Cowork helps ADHD superpowers: holding half-finished tasks while you context-switch and come back laterThe expert generalist thesis: AI tools are making everyone capable of cross-functional work without formal trainingWhy KP tells architects to keep IT out of the room if they want to make progress on AI adoptionThe three A's of knowledge work: Attitude, Aptitude, and Access and why access is the limiting factor in corporate AmericaWhy engineers need to collapse into product roles and learn customer empathy, not just coding mechanicsThe middle ground of AI competency: automating frustrating workflows, not just asking questions Google can answerWhy Claude asked KP if he wanted to pay for data aggregation services or go straight to free public sourcesHow 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 anymoreThe sandbox problem: corporate risk tolerance vs. giving employees freedom to tinker and experimentWhy offshore development teams struggle to build good software, they're not living the customer's lifeHow 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 askingHow Claude became his healthcare coordinator and delivered better emotional support than his momThe blank slate moment after his first exit paying off the house and feeling peace, not accomplishmentLiving in a truck with sleeves of tuna and stolen mayo packets and why going back doesn't scare himThe 2008 crisis, personal guarantees, and why losing everything validated his lack of confidenceWhy "celebrating small wins" is for people not building unicorns assume wins, magnify lossesVibe working: running four Mac Studios with Claude Cowork while doing manual labor he actually wants to doWhy relationship-driven CRM beats software: take engineers to lunch after RFP meetings, not Salesforce data entryThe manager vs. maker schedule and why KP operates at sprint speed with no please-and-thank-yousMorning meditation as leadership: visualizing every founder and team member's context before the workdayWhy one founder said "I can feel when you're praying for me" and what that reveals about leading mission-driven teamsThe 10-year goal isn't three private jets, it's building community where all LPs are former founders who exited and came backIf 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.
-
What happens when execution isn't enough to raise capital?
In this episode of KP Unpacked, KP Reddy and Nick tackle a critical founder mistake: obsessing over traction while forgetting to sell the vision. Inspired by a portfolio company struggling to fundraise despite excellent execution, they unpack why venture capital demands storytelling (not just proof points) and why construction tech founders in particular fall into the "show me" trap when they should be in "tell me" mode.
The conversation spans SaaS market dynamics (why KP canceled Salesforce mid-contract), the psychology of software loyalty (people love Excel, tolerate Salesforce), and why personalization unlocks joy in enterprise tools. Then they pivot to fundraising fundamentals: Elon Musk could pitch on outcomes alone but chooses to tell the Mars story. Why? Because investors back energy, mission, and vision, not spreadsheets.
Key topics covered:
Why KP canceled Salesforce after prepaying for the year and what that signals about SaaS churn in 2026The difference between software people love (Excel, Milwaukee Tools) vs. software they tolerate (Salesforce, SAP)Why usage data won't show up in earnings until 2027 and why the market is pricing in fear, not factsApplication layer thesis: why natural language interfaces will replace system-of-record UX entirelyThe critical founder error: pitching what you've done instead of where you're goingShow me vs. tell me: how to know when investors need vision, not validationWhy Elon Musk still tells the Mars story despite decades of execution proofThe hustler/hacker co-founder dynamic and why two hackers never raise capitalWhy construction tech founders index too hard on substance and struggle with showmanshipHow to separate customer narratives (narrow, fact-based) from investor narratives (expansive, visionary)The modern equivalent of "nice office space": swag stores, media presence, and dinner party bragging rightsIf you're a founder who's executing well but struggling to raise, an investor trying to understand why traction isn't translating to term sheets, or an operator wondering why personalization matters more than features, this episode will reset your fundraising strategy.
Listen now.
-
What if getting cheaper is actually the goal?
In this episode of KP Unpacked, KP Reddy and Nick unpack why AI-driven deflation isn't something to fear, it's the entire point of innovation. From Davos narratives to Elon's predictions to the Grok CEO's commentary, deflation is becoming the dominant framework for understanding AI's economic impact. But construction, housing, healthcare, and education have resisted this trend for decades. Why?
KP walks through live AI experiments: writing 150 job descriptions in 30 minutes, automating recruiting workflows, and why corporate acquisitions like Consigli (AECOM) and Datagrid (Procore) are really about speed-to-market and talent acquisition, not just technology. The breakdown? These deals are cultural change plays disguised as product acquisitions and the real value is in people who are "in it" 24/7, not just using ChatGPT for poems.
Key topics covered:
Why deflation is a core first principle of innovation and why construction has resisted itThe real structure behind the Consigli acquisition: talent, change agents, and customer pull-throughWhy Procore bought Datagrid for speed, not capability. Bulletproofing AI takes timeHow MCP servers are hackable and why proof-of-concept to production still requires curing timeKP's live experiment: 150 job descriptions written and posted in 30 minutes using Claude CoworkWhy CEOs who subordinate AI strategy should resign, you can't delegate thisThe Canvas Robotics acquisition by JLG and what industrialized robotics mean for wall finishing costsWhy 30% of every building ends up in the dumpster and how AI + robotics finally solve itThe talent arbitrage game: why companies can't hire$5M individual contributors but can acquire themSafety improvements in construction: 96 deaths at Hoover Dam vs. today's job sitesIf you're a founder wondering whether your product roadmap is fast enough, an investor trying to understand why acquisitions are spiking, or an operator who thinks "using ChatGPT" counts as AI adoption, this episode will reset your expectations for 2025.
Listen now.
-
This episode is a reality check for anyone who thinks construction is just catching up to tech. It's not. Construction is now leading it.
In this episode of KP Unpacked, KP Reddy and Nick make the case that design and construction have become the single most important constraint on technological progress. Data centers can't get built fast enough. Housing can't scale. Power generation is racing to keep pace. And for the first time in history, construction is facing technology-driven upgrade cycles, not aesthetic ones.
But this isn't just macro. KP walks through live experiments with Claude Cowork and Claude Code: automating LinkedIn grooming, generating $7K in Substack revenue, replacing million-dollar consulting contracts, and sending 1,000 personalized emails in under an hour. The breakthrough? AI agents don't need APIs anymore. They're reading screens and controlling desktop applications, which means on-screen takeoff, Revit, and legacy construction software are suddenly vulnerable.
Key topics covered:
Why on-screen automation could kill 50+ construction tech startups in the next yearHow AI agents control your desktop by watching and clicking, not integrating via APIReal experiments: LinkedIn automation, competitive analysis, email campaigns, vibe modeling in ExcelWhy construction is the bottleneck for AI infrastructure, housing supply, and energy distributionThe shift from trickle-funding to big bets: why seed rounds should be $15–25M for real problemsHow to get surgical about ICP definition using AI-powered researchThe 48-hour email delay hack: protecting your time when automation makes you too efficientWhy sales-oriented, variable-comp businesses are ideal for AI leverage right nowIf you're a founder building in AEC, an investor trying to understand where capital should flow, or an operator wondering whether your software strategy is already obsolete, this episode will reframe how you think about the next five years.
Listen now.
-
This episode is a gut check for founders heading into 2026.
In this episode of KP Unpacked, KP sits down with Nick to unpack a question every builder eventually faces: are you pushing through healthy friction or slamming into an immovable wall? From startup shutdowns to lifestyle businesses to full resets, they explore how to make clearer decisions when time (not money) is the real constraint.
This conversation spans the very practical (how founders are using AI tools daily to replace entire workflows) to the deeply strategic (why AI adoption has become a diligence filter) to the speculative-but-serious (how autonomy, robotics, and AI in the physical world could reshape where and how we live).
If you’re a founder, operator, or investor trying to decide whether to grind, pivot, or quit, this episode will sharpen your judgment.
Key topics covered
The “friction test”: how to tell the difference between productive resistance and a dead endWhy time should be treated as capital and how that reframes shutdown decisionsAI as a new baseline skill: why hours per day in tools like Claude are now table stakesHow non-technical founders are building real products from scratch using AIWhy AI adoption is becoming a red-flag test in founder diligenceReal-world AI in high-stakes environments (including life-or-death decision-making)Eliminating “thought mind work”: how automation reduces stress and extends founder longevityBig bets on the physical future: autonomous vehicles, robotics, VTOLs, space hotels, and living farther from cities without the commute taxIf you’re navigating 2026 planning and wondering whether to double down or walk away this episode is for you.
Listen now.
-
This is our final episode of the year, and we’re ending it with the kind of conversation AEC needs more of.
In this episode of KP Unpacked, KP sits down with Dr. Barry Clark (CTO) to connect the dots from “physical startups” (robots sewing denim) to what comes next: robots + humans coexisting on jobsites, AI-driven motion control, and a coming wave of materials + manufacturing innovation that could reshape how we design and build.
If you’re a founder, operator, or AEC leader wondering what’s real vs. vaporware, this one will sharpen your lens.
If you truly meant “last podcast of 2035,” just swap the year, but “final episode of the year” keeps it accurate either way.Key topics covered
From robotics in apparel to robotics in construction: why “physical startups” are backWhy construction is the hardest automation environment (unstructured, bespoke, constant pivots)AI’s impact on robotics: from brittle logic to learning systems that handle “unknown unknowns”Digital twins + simulation: getting cheaper, more practical, closer to daily useKP’s thesis: a materials renaissance for AEC—and the real bottleneck (commercial scale)What “motion control” actually means (path planning + actuator control)The missing layer: orchestration across people + robots on live jobsitesA hard truth: project tools often become archives, not systems that drive behaviorGuest bio
Dr. Barry Clark is KPR’s CTO with a background in mechanical engineering, optimal control, computer vision, and automation, spanning robotics startups and large-scale automated assembly (including server assembly and software-defined manufacturing). - Show more
