Speaking slots tell you what a leader is selling inside

When a leader speaks at a conference, they're not only talking to the audience. They're pitching their own company.

The talk is the public version of the plan they're trying to get funded inside.

Why leaders take the stage

Senior people don't give talks for fun. It takes prep time, travel and approval from communications. They do it when it helps them.

And it helps in two ways. Outside, it builds their name. Inside, it puts a stake in the ground. A CIO who stands up and says the company is moving every system to a single platform in three years has just made that plan harder to walk back. Their boss sees the clip. Their peers see the post. The idea becomes real.

So a speaking slot tells you what the leader believes, what they're betting their reputation on and what they need to go well.

What to read

Start with the abstract. Event sites publish the title and a short description of every session. It's usually written by the speaker or their team, and it's the most compressed statement of their agenda you'll find anywhere.

Read the title for the claim. Read the description for the problem. A session called something about scaling data across fifty plants tells you there are fifty plants and the data doesn't scale yet.

Then look at the panel. Who else is on stage? A leader on a panel with a cloud provider is probably deep with that provider. A leader on a panel with peers from the same industry is sharing a common problem.

Then look for the recording or the recap. Many leaders post a summary afterward. That's where they say what they're proud of and, sometimes, what's still hard.

Stack it with the account

A talk alone tells you the agenda. It doesn't tell you whether there's money behind it.

So check the account. Are they hiring for the work the talk describes? Does the 10-K name the same program? Did the speaker start the role in the last year? A talk, a filing and a set of job posts that all point the same way is a strong reason to write. There's more on combining signals in the buying signals guide.

What to send

Don't send a compliment on the talk. Every vendor in the audience sends one.

Send a hypothesis about the gap between the talk and reality. The speaker described where they're going. Your guess is about what's in the way.

Say a VP of operations at an industrial equipment maker gives a talk on connecting maintenance data across all of the company's plants. Her company has four open roles for reliability engineers, and the latest 10-K mentions a plant modernization program.

Your talk on connecting maintenance data across the plants made the goal plain, and the 10-K backs it with a modernization program. That's a public commitment with your name on it. My guess is the older plants are the hard part, with equipment data that's still on paper or local servers, and the reliability roles are slow to fill. Is that close, or is the harder piece something else?

It respects what she said. It shows you read the filing. And it names the problem she probably skipped in a twenty-minute talk.

Timing matters

Before the talk is fine if you have something to add. After the talk is usually better. She's just put the plan in public, she's getting reactions, and she's thinking about what comes next.

The few weeks after a talk are when a leader is most open to people who understood it. Wait two months and the moment has passed.

Don't stop at the speaker

The speaker is usually the economic buyer or close to it. But the people who'll do the work sat in the audience at the company's own town hall, not at the conference.

Find the champion who'll run the program and the technical lead who'll build it. Write them their own versions. For the champion, the talk is a deadline they now have to hit. For the technical lead, it's an architecture they now have to deliver. There's more on that in sell to the committee, not the contact.

A talk is a leader telling the world what they want. Write to the gap between the stage and the shop floor.