Enterprise AI spend on LLM APIs hit $8 billion in just the first half of 2025 — double all of 2024. Most of that spend is going to the same general-purpose models, and Iddo Gino thinks companies are building on a foundation that won't hold.

Iddo founded his first company at 17, scaled it to unicorn status by 24, and spent nearly a decade in the API integration space. His position is straightforward: trillion-parameter models optimized to do everything are expensive, slow, and ill-suited for the narrow, repeatable tasks that make up the majority of production AI workloads. The companies gaining ground are decomposing their systems into specialized models — each trained for one specific task, orders of magnitude smaller, and meaningfully more accurate than any general-purpose model in that lane. He also gets specific about why most fine-tuning efforts quietly fail, why model capability is no longer what's slowing agentic systems down, and what the market actually looks like by 2030 when this plays out.

Topics discussed:

• $8B in enterprise LLM API spend in H1 2025 and what's actually driving it

• Decomposing agentic systems into narrow subtasks vs. single general-purpose model approaches

• Why fine-tuned models have a shelf life and the case for continuous weekly retraining cycles

• The integration and data access layer as the real production bottleneck in agentic systems

• MIT study: 90% enterprise AI initiative failure rate and what separates the 10% that work

• Iddo's 2030 prediction: 50-60% of tokens flowing to specialized models, not large labs

• Model agnosticism as a structural hedge against LLM provider lock-in

Every trust and security system in payments was built around one assumption: a human is on the other end. CAPTCHA, email confirmation, UI-based checkout flows — none of it works when the buyer is headless. That's the wall AI agents are running into right now, and it's not a model problem. It's an infrastructure problem.

Jim Nguyen, Co-Founder and CEO of InFlow, has watched payments evolve through the online, mobile, and crypto shifts. Each one introduced a new buyer type and a new interaction model — and the payment layer always had to be rebuilt to match. This shift follows the same arc. The difference is that agents transact through APIs, not interfaces, which means the entire onboarding and trust layer has to be rearchitected from scratch.

The bottleneck isn't just payment execution. An agent can do the work — build the site, write the code, complete the output — and then stall completely when it hits a third-party service it can't access because it can't open an account, enter a credit card, or verify an email. Jim's proposed fix is deliberate: the human sets the policy upfront, assigns a spend limit per site, and the agent executes within those bounds. Anything outside that threshold comes back for approval. Wallet solutions don't solve this on their own. If the agent can pay but still can't self-onboard to the service, you've only solved half the problem.

Topics discussed:

• AI agents as the third buyer type requiring a new commerce interaction model

• Why headless API-only transactions break existing payment trust infrastructure

• The onboarding gap that wallet-only solutions fail to address

• Human-defined spend policies as the guardrail model for agent transactions

• How sellers need to support a third buyer flow alongside mobile and browser to enable agent transactions

• Jim's vision for agent-managed travel, purchases, and bill management by 2030

• Trust and compliance as the ceiling on how fast this gets deployed at scale

  
  

  Listen more at: https://www.cadreai.com/ai-2030-podcast

Traditional competitive moats collapse when anyone can replicate your product by afternoon. Dmitry Shapiro, CEO of MindStudio and former Google executive, explains why the ability to continuously refactor operations in 5-30 minutes matters more than what you initially build, and why the companies resisting this shift are already behind.

Over 400,000 agents deployed on MindStudio reveal a pattern enterprises miss: organizations aren't people using tools, they're poorly integrated tech stacks (averaging 130 SaaS products for mid-market) held together by humans acting as connective tissue. Dmitry calls this "AI duct tape"—the intelligence layer that bridges system gaps without traditional integration work. A newspaper holding company deployed 400+ agents built by one non-technical person, automating court case monitoring that previously consumed an hour per journalist daily. When Claude Code can rebuild your entire stack overnight, organizational velocity becomes the only defensible advantage. Companies refactoring in 30 minutes rather than quarters are pulling ahead. The real constraint isn't model capability. Chat works for simple queries, but complex workflows need custom UIs with draggable elements for multi-dimensional control that can't be articulated through prompts. Product managers now outperform engineers because communication mastery beats technical skills when AI writes the code.

Topics Discussed

• AI duct tape bridging 130 SaaS products without data warehouse infrastructure

• 5-30 minute refactoring cycles as competitive advantage over quarterly roadmaps

• Product manager communication skills outperforming engineering technical depth

• Custom UI requirements for high-fidelity AI instruction beyond chat limits

• Newspaper company: 400+ agents from one non-technical builder

• Agentic approach replacing data warehouse investments for smaller companies

• Organizational velocity determining winners when code becomes commodity

• Ray Kurzweil's 2029 singularity prediction and exponential thinking gaps

RAG isn't just another AI buzzword, it's the architectural foundation that determines whether enterprise AI delivers value or burns budget. Eva Nahari, former Chief Product Officer at Vectara and four-year venture investor, explains why separating data from models matters more than the models themselves, and why 90% of AI implementations fail at the execution layer, not the technology layer.

The standard approach, dumping an 80-page PDF into a custom GPT, fails because accuracy requires proper data architecture, not better prompts. RAG addresses this by feeding models precise context rather than expecting them to ingest everything at once. But implementation creates new problems: multiple teams building isolated RAG systems across the same enterprise, creating governance nightmares when those hobby projects need to scale. The companies succeeding aren't the ones with the best AI talent, they're the ones who treated data management seriously before the AI hype arrived.

Topics Discussed:

• RAG architecture separating data from models for compliance traceability

• Retrieval quality as the primary bottleneck before generation accuracy

• RAG sprawl problem from independent team implementations across enterprises

• Real-time governance systems using guardian agents for multi-step workflows

• Intent logging requirements for auditing agentic decision paths

• Agent-in-the-loop pattern replacing human-in-the-loop for workflow efficiency

• Documentation quality emerging as critical AI infrastructure investment

• MCP standard adoption for cross-system data retrieval and access control

Customer support exists to paper over product gaps. As AI handles more tier-one resolution, the question isn't whether automation replaces humans, but where human intervention becomes luxury versus necessity. John Wang, Co-founder and CTO at Assembled, outlines the execution challenges leaders overlook when deploying AI support systems.

AI tackles straightforward requests, but high-touch service remains defensible. The Four Seasons commands premium pricing despite automation everywhere else in hospitality because customers pay for human judgment in complex situations. Support will bifurcate the same way. But the real constraint isn't model capability. AI performance is capped by what you feed it. Most companies point agents at outdated Confluence wikis expecting magic. Documentation quality now directly impacts support economics, and teams that treated internal docs as nice-to-have now face a forcing function.

Topics discussed:

• Bifurcation between tier-one AI automation and premium human support

• Four Seasons pricing model applied to customer support economics

• Documentation quality as primary bottleneck for AI support performance

• Outdated Confluence documentation creating AI failure modes

• AI-generated requirement docs reducing documentation friction

• Organizational discipline around SOPs determining AI adoption speed

• Internal documentation shifting to critical AI training infrastructure