Key Takeaways

  • Early in hard tech, impose specific commercial constraints on your product scope to ensure focus and long-term survival, rather than chasing every technical challenge.
  • Prioritize building "compounding technology," where each new piece of work, like an improved operating system or better dev tooling, makes the entire system more valuable, rather than being discarded.
  • For early-stage startups, select a “small, deep problem space” to dominate, instead of a broad, shallow one that spreads resources too thin.
  • Do not blindly copy strategies from mature companies or founders with established networks; your startup's stage, team's unique skills, and market context dictate the right path.
  • Define your product space using first-principles thinking, directly matching your co-founders' and early team's skills with specific customer pain points you hear from the market.

The Iron Box of Commercial Constraint

When you're building hard tech, it's easy to get lost in the sheer difficulty of the technical problem. Applied Intuition, now a $15 billion company building physical AI for autonomous machines, could have done just that. But co-founder Kassar Ounounas warns against it. He argues that ambitious founders in hard tech should impose commercial constraints from day one. “My biggest advice... in this like almost like commercialization of technology is I think often the that constraint so we talked about like hardware constraints and we talked about uh there's also like on the commercial side there's constraints which is we're going only do things that fit in this box. That is, I think, very good for founders.”

This isn't about avoiding hard problems. It's about channeling your technical prowess into a commercially viable product that can actually scale. Applied Intuition didn't build everything for everyone; they focused on a specific operating system for autonomous machines. This tight focus, an "iron box" of sorts, forces you to solve problems that customers will pay for, increasing your chances of reaching the finish line.

Build Tech That Compounds, Not Crumbles

Survival in hard tech, Ounounas explains, gives you the chance to see a different kind of return: compounding technology. Most early-stage work can feel like building sandcastles, only for them to wash away as the market shifts or your understanding grows. Applied Intuition, however, designed its core tech to compound. “This is truly compounding technology. A lot of the work that we do just compounds it. We don't throw it away. It it gets better. The operating system work gets better. The de dev tooling gets better. The models get better,” Ounounas says.

Imagine every line of code, every simulation model, every piece of infrastructure directly improving the overall system. This means you're not constantly starting from scratch. Each new feature adds to a growing base of value, making the system more powerful and robust with every iteration. The commercial constraints help you survive long enough to experience this. “If you can put a little constraint on on commercials that has a small ability for you to more likely see the other end of that that walk because you get to the other end you will get the big return from compounding technology just a lot of people just don't make it,” Ounounas warns.

Ditch Generic Advice, Know Your Own Cards

Every founder absorbs advice, but Ounounas cautions against blindly adopting strategies, especially from founders with different contexts. An early-stage hard tech company can't operate like a well-funded, mature Google spin-out. For instance, the advice to build in stealth works well for founders with strong existing networks. “Well, yeah, if you're a YCCOO. Yeah, you can because we Yeah, we worked, you know, together at Google. We have a long history and we don't and which mean which is another way of saying we have big networks,” Ounounas points out. Without those pre-existing advantages, stealth might just mean obscurity.

Instead, he advocates for a first-principles approach: “The only the only solution you really have is use first principal thinking and say based on my skills, my co-founder skills, the skills of my early team members and the what I'm hearing from customers, what's the product space that I should I should build in.” This grounded approach ensures your strategy aligns with your unique strengths and direct market feedback, not someone else's playbook.

What to Do With This

This week, take Kassar Ounounas' advice literally. Define your startup's "commercial box": what specific customer segment, technical problem, and immediate business value will you solve, to the exclusion of all others? Then, list three major features or technical initiatives you plan for the next six months. For each, ask: how does this explicitly make an existing part of our system better and more powerful, not just add a new capability? Finally, conduct a "first principles audit" for your product direction. Ignore competitors and trends. Map your co-founders' and early team's top three unique technical skills against the top three most urgent, specific pains you've heard directly from potential customers. See where they overlap. That is your small, deep problem space.