One Person Walks into Wind-Tower Monitoring

All I had was a phone number. A number handed over by an intermediary — no introduction, no backstory. A few months later, the company had one more product line.

In what happened in between, the part worth writing down is not the outcome; it is where each step actually got stuck.

What a new setting means

We worked on infrastructure monitoring. Bridges, tunnels and dams were already running by then, and one class of structure was left on the list that we had never touched: wind-power towers.

A new setting is not a matter of carrying an existing solution across. The structure is different, the sources of vibration are different, and what the operator cares about is different most of all — a bridge owner asks “can it keep being used the way it is?”, while a wind-tower owner asks an entirely different set of questions. To answer them you first need real observations of that class of structure; to have observations, someone first has to let you go up and install equipment.

So the problem turned into a non-technical one: how do you get a company that has never heard of you to agree to an experiment on an asset that is currently generating power?

The first step was just to dial

I had no assistant and no connections, only that number. I made the call myself, set the meeting myself, and flew to another city myself.

Honestly, the bar for this step is absurdly low — you press dial. What makes people back away is that the failure rate is high, and that the failure is very concrete: the other side may hang up in thirty seconds, and you will have spent days preparing for those thirty seconds.

I slowly got used to something: most opportunities, by the time they reach you, are too thin to look like opportunities. The only difference is whether you dial.

The roomful of people

Only once I arrived did I learn that I was not presenting to one or two people but to a room full of experts — people who had spent years on that class of structure and knew more about it than I did.

I overturned my own preparation on the way there. I had meant to talk about how good our technology was; what I actually talked about was three things. How this experiment will affect your normal operation (the answer has to be “almost not at all,” with the reason spelled out). What the worst case is, and who handles it if something goes wrong. And what you will know afterwards that you do not know now, if it works — said in their words, not in ours.

That order is not a sales technique. When someone lets you run an experiment on their asset, the party carrying the risk is them, not you. Once that lands, the center of gravity moves on its own, from “we are very good” to “your risk is on us.”

One more thing I had prepared thoroughly: that class of structure itself. Knowing someone’s own asset better than they expect you to is a form of respect in itself, and the most effective credential of trust I have come across — worth more than any page of company introduction.

Afterwards

They agreed. The experiment worked, that class of structure had real observations at scale for the first time, and the company gained a new product line out of it.

What I took away is not something like “be bold.” It is three more concrete things:

• the barrier in front of a technology often does not sit on the technology’s side;
• persuasion runs in the other party’s language, not in yours;
• taking a paper-thin lead seriously is a habit, and a habit can be trained.

I work in a different field now; what I design every day is how humans and AI collaborate. But that lesson has not moved an inch: what really blocks something is usually permission, trust and boundaries — not whether it can be built.