Hardik Kabaria on Building Physics as Infrastructure with a Foundation Model for Physics
5.27.2026 | By Vinci
In this episode of BUILDERS, Hardik Kabaria explains how Vinci approached its initial beachhead, why the company started with heat transfer in semiconductors and electronics engineering, and how that decision shaped both product strategy and go-to-market execution. The conversation focuses on a practical question many technical founders face: how do you introduce a new kind of system into a market that has never bought it before?
Hardik discusses why Vinci chose a problem area that was already urgent, technically consequential, and tied directly to engineering performance. He also explains why Vinci focused on capturing existing budget line items rather than trying to create new demand from scratch, and why the long-term vision is physics as infrastructure rather than physics as a point tool.
How Hardik chose heat transfer in semiconductors as Vinci’s initial beachhead using a two-axis framework
Why Vinci’s foundation model for physics was built ground-up rather than adapted from a language model
How Vinci thinks about physics as infrastructure, not just software
Why usage-based pricing maps better to infrastructure than traditional enterprise software
The three competitive buckets in physics simulation and why legacy approaches are structurally constrained
The “moment of authority” that signals when a customer has moved from evaluation to dependency
Why whiteboard sessions with engineering teams matter more than conference presence for this category
How the right beachhead can create downstream and upstream pull across the supply chain
Why this matters
For a technical company building something new, the hardest problem is often not just the technology itself. It is finding the entry point where a new system can fit into an existing workflow, existing budget, and existing decision process. This episode is useful because it shows how Vinci approached that problem deliberately rather than assuming the market would immediately create a new category on its own.
The conversation also reinforces a broader point that matters for physical-world systems: adoption is not driven by novelty alone. These systems are evaluated against engineering workflows, validation expectations, budget ownership, and real operational dependency. That is why the framing of physics as infrastructure matters. The question is not just whether the technology is interesting. It is whether teams come to rely on it as part of how real engineering decisions get made. This synthesis is grounded in the episode’s discussion of infrastructure framing, pricing, budget capture, and customer dependency.
Why did Vinci choose heat transfer in semiconductors as its starting point?
Hardik explains that Vinci used a two-axis framework: how urgently the world needs the problem solved, and how critical that physics domain is to the product’s performance. In the episode, heat transfer in semiconductors scores highly on both.
What does “capturing existing budget line items” mean?
In this episode, the phrase refers to fitting Vinci into budgets that already exist inside engineering organizations rather than trying to persuade buyers to create an entirely new line item for a new category.
Why does Hardik describe physics as infrastructure?
He frames physics as infrastructure because the long-term goal is not occasional use. It is a system teams depend on repeatedly and evaluate on throughput, similar to how other core infrastructure systems are judged.
Why couldn’t Vinci’s system be built by adapting a language model?
The episode states that Vinci’s physics foundation model was built ground-up and cannot simply be replicated by adapting a language model, reflecting the distinct requirements of physics computation and engineering workflows.
What is the “moment of authority”?
Hardik describes it as the behavioral signal that tells Vinci a customer has moved from evaluation to dependency.
Hardik Kabaria appears on BUILDERS to discuss Vinci’s beachhead strategy, infrastructure framing, pricing model, and how the company captured existing engineering budget instead of trying to create new demand from scratch. The episode runs 25 minutes and was published May 27, 2026.
Vinci is a frontier lab building the foundation model for the physical world, with deterministic, solver-grounded systems already deployed in production engineering workflows on flagship programs.
