ABC Disposal — Room Reading Guide

ABC Disposal — room reading guide

Owner + ops manager · friendly long-term relationship but skeptical, not default trust · 2026-05-19

Opening 60 seconds. Do not small-talk past ~90 seconds. After that, the room gets antsy and you've burned warm-up. Transition with: "Alright, I've got a 30-minute walk-through for you — let me get into it."

Signals from the owner

What you see / hear	What it likely means	What to do
Goes quiet on the cost slide (slide 7).	Doing the math, not objecting.	Wait. Do not fill the silence. They'll ask a clarifying question or move on. Filling it signals nerves about the number.
Looks at the ops manager before answering.	The ops manager has real influence here.	For the rest of the meeting, address the ops manager directly when discussing operations and migration. Don't pretend you didn't notice.
Checks phone.	You've lost them.	Skip ahead to slide 10 ("why now") and slide 11 (the ask). You can return to detail in Q&A if they re-engage. Don't grind through.
"Are you sure about that?" — tone neutral.	Skeptical-but-listening. The relationship is on the line.	Answer with the specific source. "Yes — that's from [Coalition's 2024 report / SonicWall's published lifecycle / CISA's KEV catalog]. I can send you the link after." Specificity earns the skepticism back.
"You guys have been good to us, but…"	Relationship credit being spent. They're weighing it against change risk.	Acknowledge the relationship cleanly: "And we want to keep being good to you — which is why we're recommending the change, not asking for a renewal of something that's getting worse." Then return to the slide.
Asks "what would you do if it were your business?"	Wants permission to follow the recommendation.	Give it cleanly: "If this were my business, I'd do the discovery week starting Monday and have a fixed-fee number for the rest by Friday." No hedging.
"Send us a proposal" too quickly.	Could be real interest or could be a polite close.	Pin down specifics: "Happy to — what specifically do you want in it, and when do you need it?" Specifics reveal which it is.

What you see / hear

What it likely means

What to do

Goes quiet on the cost slide (slide 7).

Doing the math, not objecting.

Wait. Do not fill the silence. They'll ask a clarifying question or move on. Filling it signals nerves about the number.

Looks at the ops manager before answering.

The ops manager has real influence here.

For the rest of the meeting, address the ops manager directly when discussing operations and migration. Don't pretend you didn't notice.

Checks phone.

You've lost them.

Skip ahead to slide 10 ("why now") and slide 11 (the ask). You can return to detail in Q&A if they re-engage. Don't grind through.

"Are you sure about that?" — tone neutral.

Skeptical-but-listening. The relationship is on the line.

Answer with the specific source. "Yes — that's from [Coalition's 2024 report / SonicWall's published lifecycle / CISA's KEV catalog]. I can send you the link after." Specificity earns the skepticism back.

"You guys have been good to us, but…"

Relationship credit being spent. They're weighing it against change risk.

Acknowledge the relationship cleanly: "And we want to keep being good to you — which is why we're recommending the change, not asking for a renewal of something that's getting worse." Then return to the slide.

Asks "what would you do if it were your business?"

Wants permission to follow the recommendation.

Give it cleanly: "If this were my business, I'd do the discovery week starting Monday and have a fixed-fee number for the rest by Friday." No hedging.

"Send us a proposal" too quickly.

Could be real interest or could be a polite close.

Pin down specifics: "Happy to — what specifically do you want in it, and when do you need it?" Specifics reveal which it is.

Signals from the ops manager

What you see / hear	What it likely means	What to do
Crosses arms on the migration slide (slide 8).	Worried about disruption to dispatch / day-to-day.	Pivot directly: "I can see this is the part you're thinking about most — what's your biggest concern?" Listen 30 seconds before responding. Refer back to the parallel-run pattern.
Nods on "no more patch alerts" (slide 6).	They feel the firmware-advisory pain personally.	Dwell briefly. "That alone is worth real money in your week, isn't it." Then move on.
Asks a technical question (e.g., "what's ZTNA?").	Genuine curiosity, not a test.	Answer plainly without jargon: "Instead of a remote-access door that's open to the internet for anyone to scan, each person's laptop is approved by name, every time, before it can reach anything. No exposed door." Don't lecture.
Quiet throughout, lets owner drive.	Either deferring entirely, or saving objections for after the meeting in private.	Address them by name on the migration slide: "[Name], how does that timeline sit with your operations calendar?" Pull them in.
Starts finishing your sentences.	On board, accelerating.	Don't drag through the rest. Advance faster. Get to the ask sooner.

What you see / hear

What it likely means

What to do

Crosses arms on the migration slide (slide 8).

Worried about disruption to dispatch / day-to-day.

Pivot directly: "I can see this is the part you're thinking about most — what's your biggest concern?" Listen 30 seconds before responding. Refer back to the parallel-run pattern.

Nods on "no more patch alerts" (slide 6).

They feel the firmware-advisory pain personally.

Dwell briefly. "That alone is worth real money in your week, isn't it." Then move on.

Asks a technical question (e.g., "what's ZTNA?").

Genuine curiosity, not a test.

Answer plainly without jargon: "Instead of a remote-access door that's open to the internet for anyone to scan, each person's laptop is approved by name, every time, before it can reach anything. No exposed door." Don't lecture.

Quiet throughout, lets owner drive.

Either deferring entirely, or saving objections for after the meeting in private.

Address them by name on the migration slide: "[Name], how does that timeline sit with your operations calendar?" Pull them in.

Starts finishing your sentences.

On board, accelerating.

Don't drag through the rest. Advance faster. Get to the ask sooner.

Signals from the room as a whole

What you see / hear	What it likely means	What to do
Someone interrupts to disagree.	Engaged enough to push back.	Let them finish. Wait 2 full seconds. Acknowledge specifically: "Yeah, that's exactly the thing I was worried about too — here's what we do about it." Disagreement handled well builds more trust than agreement.
Both go silent and look at each other.	Silent decision moment.	Do not speak. Count to 5 in your head. Whoever speaks first usually decides the answer.
They point to a specific slide asking for detail.	Buying signal.	Be precise. Offer to send the underlying data after the meeting. Navigate the deck confidently.
"What do most of your clients pick?"	Looking for social proof.	Honest answer. If the answer is "we've recommended this to other clients in your situation and most have moved" — say it. If you'd be inventing, don't.
Conversation drifts onto unrelated topic.	Either rapport-building or avoidance.	Let it run ~60 seconds, then bridge back: "Speaking of — that ties to slide X actually…" Don't be a robot, but don't lose the meeting.

What you see / hear

What it likely means

What to do

Someone interrupts to disagree.

Engaged enough to push back.

Let them finish. Wait 2 full seconds. Acknowledge specifically: "Yeah, that's exactly the thing I was worried about too — here's what we do about it." Disagreement handled well builds more trust than agreement.

Both go silent and look at each other.

Silent decision moment.

Do not speak. Count to 5 in your head. Whoever speaks first usually decides the answer.

They point to a specific slide asking for detail.

Buying signal.

Be precise. Offer to send the underlying data after the meeting. Navigate the deck confidently.

"What do most of your clients pick?"

Looking for social proof.

Honest answer. If the answer is "we've recommended this to other clients in your situation and most have moved" — say it. If you'd be inventing, don't.

Conversation drifts onto unrelated topic.

Either rapport-building or avoidance.

Let it run ~60 seconds, then bridge back: "Speaking of — that ties to slide X actually…" Don't be a robot, but don't lose the meeting.

Closing 60 seconds. Always leave with the next concrete step agreed on. Specifically, with a date. With a calendar invite if possible. Open meetings die quietly.

Target close: "Great — I'll send the 1-week discovery SOW tomorrow morning. Can we book the kickoff for Monday the [date]?"