As aired
Nathan and Prakash briefly closed out a discussion of a newly announced frontier AI lab — characterized by ideologically motivated founders, $200M from a16z, and a reported large but undisclosed NVIDIA investment — before pivoting to the Tricia Martinez interview.
Prakash introduced Tricia Martinez, founder and CEO of Dapple, as an entrepreneur offering a 'third path' between renting shared public-cloud capacity and building private data centers from scratch. Dapple deploys dedicated, single-tenant, in-country AI clouds — isolated physical hardware governed by local law, operated with modern cloud-software interfaces. Tricia previously helped launch one of Africa's first digital banks and served as a White House Fellow across both the first Trump and Biden administrations at the Department of Energy, where she built an AI-and-energy strategy across seventeen national labs. Her co-founder and COO, Salam Al Musawi, brings an engineering background with claimed deployment of more than 300,000 AI accelerators globally. Prakash noted Dapple's announced $30M seed round backed by Raptor Group and ION Pacific, and the company's claim of over $100M in secured enterprise contracts within its first five months of operation.
After a brief audio-quality fix at the top of the segment, Nathan opened with a direct question: who is so eager to spend this money that Dapple claimed $100M in signed contracts within five months? Tricia argued that enterprise and government demand has been bottled up for years — public clouds lack capacity for large enterprise workloads, NeoCloud bare-metal options require enterprises to build their own operational stack, and on-premises buildouts are too costly and complex to staff. Dapple's 'Enterprise OS Cloud,' she said, collapses that complexity into a single operating layer for deploying and running production AI across dedicated infrastructure. She teased that upcoming growth announcements would be even more dramatic.
Prakash pressed on Dapple's heavy Azure-native marketing language — integration with Azure Machine Learning, Azure Arc, and Azure Monitor. Tricia confirmed that unifying public and private cloud into a single frictionless experience is Dapple's core IP, but declined to name the strategic cloud partners involved, saying official announcements would come within months.
Nathan questioned the 91–94% GPU utilization figure on Dapple's website, finding it surprisingly high for a single-tenant infrastructure play. Tricia explained that Dapple's deployments are backed by long-term enterprise contracts — typically three, five, or seven years — making the model about committed capacity and customer outcomes rather than spot-market utilization.
On what workloads sustain that utilization, Tricia identified three categories: large-scale model training for AI-native companies building domain-specific foundation models; production-scale inference requiring predictable performance, low latency, and strong governance; and AI agents embedded in internal operations and customer-facing products. She noted Dapple started with mission-critical verticals — finance, cybersecurity, government, defense — but said Fortune 1000 demand had turned out far larger than anticipated, with most customers simply desperate to access any capacity so they can begin building.
Prakash asked how Dapple achieves 6-to-9-month deployment timelines when even record-setting data-center builds take roughly fifteen months. Tricia described a network-orchestration model: Dapple partners with existing data-center operators and infrastructure providers, then contributes capital, GPU infrastructure, enterprise demand, and its software operating layer. In some deals Dapple helps finance the infrastructure directly; in others it deploys on partner facilities.
Nathan raised a macro risk question about the AI infrastructure finance stack — whether long-term commitments paired with short-term revenue flows could create cascading fragility under an external shock. Tricia acknowledged the market has grown more disciplined, with financing groups increasingly requiring demand-backed contracts rather than speculative buildout. She argued Dapple's model is more de-risked because enterprise customers make large upfront down payments and commit to multi-year relationships. She also cited growing regulatory risk around compute export restrictions as a mounting threat to competitors relying on certain geopolitical off-takers.
Prakash characterized Dapple as more asset-light than the typical NeoCloud. Tricia agreed, framing the company as software-first: it partners for data-center operations and GPU ownership where possible rather than trying to own everything, and believes that positioning is where Dapple will ultimately win.
Nathan explored Dapple's long-term defensibility in a world where AI coding agents could eventually simplify even hyperscaler cloud complexity. Tricia said there is no single moat; defensibility comes from three reinforcing layers: enterprise relationships and the high switching costs of moving mission-critical AI infrastructure (governance, networking, compliance, security, and operational workflows all move together); an operating platform that gets smarter with each deployment, improving placement, capacity planning, performance, cost, and policy management; and a broad ecosystem of infrastructure providers, capital partners, silicon partners, and enterprise customers that is difficult to recreate simultaneously. She drew an analogy to AWS abstracting on-premises complexity for the enterprise cloud era, calling Dapple the same abstraction layer for the AI infrastructure era.
Prakash asked what numerical KPIs enterprise customers track most closely. Tricia listed five: time to deployment; availability and reliability for mission-critical and in-country isolated workloads; scalability as AI usage grows; governance and compliance — which she called 'probably one of the most important things that no one can support them on in the market right now'; and predictable economics over the full deployment lifetime.
Nathan asked, drawing on Tricia's Africa background, how accessible AI infrastructure is to African enterprises. Tricia said Dapple's demand is concentrated in APAC, the US, and Europe, with minimal signal from South America, Africa, or parts of the Middle East. She described Africa as falling behind on AI production capacity, with cost as the primary barrier — citing new hardware like Nvidia's Vera Rubin as making deployment even more prohibitive. She called it a genuine problem that governments are trying to address but struggling to solve.
Prakash asked what mistakes enterprise AI buyers most commonly make. Tricia said most are making operating-model mistakes rather than technology mistakes: treating AI like another software project rather than recognizing it as a fundamentally infrastructure problem that requires rethinking compute, data, governance, security, and operations. A second common error is optimizing for today's proof-of-concept scale without planning for the architecture required when every business unit wants AI.
Nathan asked whether Dapple is best understood as a market maker or as an agent representing enterprise customers. Tricia rejected both frames, calling Dapple an operating platform: it orchestrates the right infrastructure for each customer's AI strategy and requirements, with Dapple's software sitting across every deployment — regardless of whether the underlying data center is owned by Dapple or a partner.
Prakash closed with a question on pricing dynamics mid-deal. Tricia described a 'take it or leave it' forcing function driven by capacity scarcity — sales cycles simply cannot stretch to six months because the capacity is gone. She said Dapple honors a quoted price once offered to a customer, even if market pricing shifts during deployment.