The Traction Problem Thiel Never Named

Something is not working. The round is taking longer than it should. The pilot that was going to convert has gone quiet. The engineer you wanted took the safer offer.

You would call this a traction problem. Everyone does. But traction is not a cause, it is a symptom, and the word tells you nothing about what to fix.

You know something is wrong. You do not know what.

So you do what almost every technical founder does. You go back to the product.

Zero to One is one of my favourite books of all time. I have pushed it on more founders than anything else on my shelf. So take what follows as a footnote to it, not a takedown.

In Chapter 11, “If You Build It, Will They Come?”, Peter Thiel puts it plainly. “Poor sales rather than bad product is the most common cause of failure.”

His argument is that engineers carry a fantasy. They believe a sufficiently good product sells itself, and that distribution is a tax paid by people with weaker technology. So they under-invest in the one thing that determines whether anyone ever finds out what they built. Thiel’s fix is to get a single distribution channel working. Do that and you have a business. Fail and you have an invention.

He is right. For most startups that is the whole story. Build the channel and the thing sells.

But the prescription carries an assumption, and in deep tech the assumption breaks.

Distribution moves a message. It does not create one.

Thiel’s fix assumes you already have something the market can hold in its head. A better mousetrap that people can at least recognise as a mousetrap. Get that in front of enough of the right people and the machine works.

Now try it with a novel propulsion system that has no commercial analogue. Or a material that does not exist yet. Or a method that collapses years of laboratory work into days.

You can hire the best salesperson in the country. Build a perfect channel. Put your technology in front of exactly the right investor, at exactly the right moment.

They still will not get it.

The problem was never reach. It was comprehension. And when the message is incomprehensible, better distribution does not fix it. It just means more people misunderstand you, faster, at greater expense.

That is the third failure. Not the product, not the channel, but the distance between what you have built and what the market can understand. I call it the commercial translation gap, and in deep tech it sits upstream of everything Thiel described. You cannot distribute a story nobody can follow.

Fair objection, and Thiel has an answer to it. For complex products he prescribes complex sales. Seven figure deals want the CEO in the room, not a VP of sales. The founder does the selling, because only the founder can.

He is right about the mechanics. But look at what that prescription quietly does. It treats founder dependency as the model rather than the symptom.

Founder-led selling does not close the translation gap. It conceals it. And it works beautifully, right up until you need to be in two rooms at once. Or hire a sales team who cannot do what you do. Or watch a champion carry your story into a board meeting you will never attend.

Then three years of personally papering over the gap arrives all at once.

Here is what makes this expensive. Of the three failures, the translation gap is the only one that is invisible from the inside.

You cannot see it, because you already understand your technology. Every explanation you give sounds clear to you, because you are the one person on earth for whom it is clear. The gap never shows up in your data. Nobody names it in a rejection. No investor writes to say the science is excellent but your third slide is where I stopped listening. They say it is a bit early for us.

So you reach for the explanation you can act on. The product.

Building is the thing you are good at. It is measurable, it is controllable, and it feels like progress. Rebuilding the product is a decision you know how to make. Accepting that nobody understands you is not.

I have watched founders spend six months and half a runway improving something that was never the problem. They came back with a better version of a thing the market still could not parse. Same silence. Different quarter.

All three failures produce the same symptom, which is why they get confused. They do not behave the same way.

A product problem fails consistently. People understand exactly what you have made. They just do not want it, or it does not work well enough yet. The feedback is specific. They tell you what is missing. You lose for reasons you can name, and you lose in the same way every time.

A distribution problem fails silently. Nobody is saying no, because nobody is hearing about you at all. Your pipeline is thin rather than leaky. The people who do find you convert at a reasonable rate. There simply are not enough of them.

A translation problem fails inconsistently, and it fails in the room. You get the meeting. The technical people nod along. Then the moment someone non-technical has to repeat what you do to a colleague, it dissolves. You lose deals to companies with worse technology and clearer stories. Your best conversations are with engineers and your worst are with the people holding the cheque book. Your own team describes the company three different ways. And you spend the first twenty minutes of every meeting explaining what you do, which means you are teaching, not pitching.

That last one is the tell.

If your technology only makes sense while you are in the room, you do not have a product problem. You have a translation problem. And no distribution channel ever built will carry a story that cannot survive without you.

Thiel was right that founders blame the product when they should look at how it reaches people. In deep tech, look one step further back. Before you can distribute it, someone has to understand it.

Continue reading