The first meeting is not a demo

The first meeting is where you find out if your hypothesis was right. It's not where you show the deck.

Services firms get this backward all the time. A senior buyer agrees to 30 minutes, and the team shows up with 40 slides, three case studies and a capabilities overview. The buyer leaves knowing a lot about the firm and nothing new about their own problem.

That meeting rarely gets a second one.

Why the demo instinct is so strong

Product companies demo. It works for them. The buyer wants to see the screen, click the buttons and judge the thing.

A services firm has nothing to click. What you sell is judgment, people and a way of working. The closest thing to a demo is a case study, and a case study is about someone else's company. The buyer is sitting there trying to translate your last client's story into their own situation, and most of them won't bother.

And there's a comfort factor. The deck is safe. You know every slide. Asking questions about their business means you might not know the answer, and that feels exposed.

But exposure is the point. You earned this meeting with a guess about their problem. The meeting is where you test the guess out loud.

What the first meeting is for

It's for three things. Confirm or correct the problem. Learn who else cares about it. Find out what happens if nothing changes.

That's it. If you leave with those three, you have a real opportunity. If you leave with a polite "send me the deck," you have nothing.

Start by restating the hypothesis that got you the meeting. Something like "When I wrote to you, my guess was that the migration plan you inherited is bigger than the team behind it. Is that still how you see it?"

Then stop talking. The buyer will either confirm, adjust or tell you you're wrong. All three are good. A correction from a senior buyer is the most useful thing you'll hear all quarter, and it's free.

A scenario

Say you reached a VP of operations at a mid-size distributor. Your opener named a cost program from their last earnings release and guessed that warehouse systems were the drag.

In the meeting, she tells you the warehouse systems are fine. The real issue is that three acquired companies still run their own order management, and nobody can see inventory across them.

If you'd brought a deck about warehouse modernization, you'd spend 20 minutes on the wrong problem. You came to listen, so you spend 20 minutes on the right one. You ask who owns order management today, who'd have to sign off on consolidating it, and what it costs them when a customer order falls between systems.

You leave with a named problem, two more names on the committee and a reason to come back.

What to bring instead of slides

Bring your research. The three or four facts that built your hypothesis, on one page, ready to share if it helps.

Bring two or three questions that go one level deeper than the opener. Who owns this today? What's been tried? What would have to be true for this to be a priority next quarter?

Bring one short story, told in a minute, about a similar problem you've seen. Not a case study with logos. A story that shows you understand the shape of the problem.

And bring a next step you can propose at the end. A working session with the technical lead. A look at the current plan. Something smaller than a proposal and bigger than "let's stay in touch."

Where this fits in the pipeline

Deals in services are won or lost early. If the first meeting confirms a real problem with a real owner, the rest of the cycle has something to stand on. If it doesn't, no proposal will save it. More on that in most quarters are lost in Stage 1.

The same idea that gets the meeting should run the meeting. You led with a hypothesis in the first message. Keep leading with it in the room. The longer case for that is in lead with a hypothesis, not a pitch.

Save the deck for the meeting where they ask for it. They will, once they believe you understand the problem.