What Is Deep Tech? Why the Hardest Startups Can't Be Built in a Weekend

Deep tech is technology built on a hard scientific or engineering breakthrough, not on assembling parts that already exist. Quantum computing, advanced cryptography, novel materials, fusion, robotics, and synthetic biology all qualify. The defining trait is that the core advance has to be invented and proven before there’s a product to sell.

That makes deep tech a different animal from a typical software startup. BCG research found deep tech ventures take roughly 25 to 40% more time between funding stages, that about 70% own patents, and that around 83% are building a physical product. Episode 96 is a live case study: Kevin Kane, co-founder and CEO of American Binary, builds post-quantum cryptography — deep tech where the breakthrough is mathematical rather than mechanical. The lessons are the same ones every deep tech founder runs into.

Why it can’t be built in a weekend

The hackathon model — a small team assembling existing tools into a working product over a weekend — is the opposite of how deep tech gets built. The whole premise is that the core technology isn’t sitting in a package manager waiting to be imported.

Kane put a number on it: “Tech nowadays, especially in our area, it’s to the point where you need 20 years of cumulative knowledge to do something like we’re doing. You can’t wing it on a weekend or at a meetup with some friends and hack this.” That cumulative knowledge is the real moat, and the barrier to entry. It can’t be raised in a quarter or copied from a tutorial. It’s built one hard problem at a time, often across a career.

Timing beats thesis

Most startup advice treats market timing as having the right thesis. Kane is blunt that a thesis without execution is worthless: “Theses are meaningless if your trades aren’t executing exactly where they need to be,” he said, drawing on his earlier life in systematic trading. Real conviction means being early on something the market hasn’t caught up to yet.

For deep tech that creates a bind. You often have to start years before demand is obvious, because the technology itself takes years to mature. “When we started this company, the time was not here… It’s starting to come here now.” His worry is the opposite of being too early: “If you wait too late to start, you’re not going to catch up.” Start too early and you burn capital waiting; start too late and the cumulative-knowledge gap means you never close the distance. The same scoping discipline that separates winning AI projects from the ones that fail applies to timing a company: the bet has to match the moment, not just the slide deck.

The long road of debugging what doesn’t exist yet

The part founders underestimate most is debugging. When your technology has never run anywhere, every failure is a new failure — no Stack Overflow answer, no vendor support line, no one who’s hit the same wall.

Kane described years spent chasing a single root cause: “We were having a problem handshaking… but we didn’t know that that was the issue. There’s such a long road on learning what’s going wrong with software that is new, doesn’t exist in the wild, except for what you built.” This is where deep tech timelines actually go — not into building features, but into discovering why something that should work doesn’t, in a system no one has mapped. A founder building a cybersecurity startup on known architecture can lean on proven patterns. A deep tech founder is often writing the pattern.

Earned authority

Deep tech forces founders to defend ideas that established experts may not accept yet. Kane’s answer is that authority has to be earned through proof, not borrowed from a title. His metaphor was the three little pigs: “We built a brick house, and we didn’t build a hay house.” American Binary’s claims went through private peer review and formal verification before Kane was willing to argue them in public. Conviction without proof is just confidence, and the market eventually tests it. Conviction backed by verification is a moat.

What deep tech demands from founders

Kane was direct about the personal cost. A few of his hard-won lessons translate beyond cryptography:

• Hold a standard you won’t break, even when it costs you. The technical bar and the personal one are linked; shortcuts surface years later as failures.
• Don’t postpone happiness until after the win. His advice to his younger self: “integrate it into your work now.” Deep tech horizons are too long to defer a life against.
• Take help from people you don’t click with. Useful support often comes from people you wouldn’t pick as friends.
• Match accountability to the seriousness of the problem. Face the hard problems yourself rather than hiding behind an institution.

None of this shortens the road. It makes the road survivable. Deep tech is a long game with a small number of turns, and the founders who last are the ones who can hold a standard and a life at the same time.