Your Assessment Found the Problem. Your Prospect Shrugged, Because You Used the Technical Name for It.
November 4, 2026

Your Assessment Found the Problem. Your Prospect Shrugged, Because You Used the Technical Name for It.

You've just finished a readout and you thought it went great. You walked the prospect through everything your team found, you used all the right terms, and you were careful not to leave anything out. They nodded the whole way through. When you finished they said it was really helpful and that they'd like to think about it.

Then nothing happens. A week goes by, then two, and you're left wondering how a report full of serious findings got a shrug.

I've learned this one the hard way, over a lot of readouts, and I want to save you some of the pain. The problem wasn't the findings. It was how we said them.

Think about a doctor for a second. Say you go in for some tests and the doctor comes back and tells you the technical, Latin name for what you've got. It could be something that changes your whole life, but unless you went to medical school you'd just nod, because the name doesn't mean anything to you. It isn't until somebody puts it in plain words that your stomach drops.

There's a medical term for harm that's caused by the care itself, it's called iatrogenic. I'd bet most people reading this just stopped for a second. But researchers at Johns Hopkins published a study a few years ago estimating that medical error is one of the leading causes of death in this country, and part of the reason you never hear about it is that it doesn't show up well on death certificates. Something that serious, and the word for it doesn't alarm anybody.

That's exactly what happens when we read a prospect their report. We say things like "unpatched server with a known remote code execution vulnerability" and to us that's a five alarm fire. To a business owner it's a string of words that sounds like the IT guy being thorough.

It's easy for us to do this, and I'm not saying it to be hard on anybody. Technical people use technical words because they're precise, and because the words carry weight when you know what's behind them. But precision is for the expert, and it just turns to fog for the person listening.

Here’s what I want you to do instead. For every finding, get ready to say three things. What it is in plain words, what it could do to this specific business, and what that would cost them in time or money or trust. If you can't say all three without a technical term in them, you're not ready to present it yet.

 

No multi-factor authentication on admin accounts turns into "if one password gets stolen, a stranger has the keys to everything you own." That unpatched server with the known vulnerability turns into "someone outside your company can take over the system that holds all your email, and they don't even need a password." And backups that were never tested turns into "you think you have a safety net, but nobody has ever checked to see if it opens."

Do you see the difference? Same findings, but now they can picture it.

The part I think matters most comes next. Even in plain words, if you stand there and tell them it's serious, they'll push back or they'll go quiet. People don't like being told they have a problem. But if they work it out themselves, it's a different thing entirely, because now it's their idea.

If that account got taken over on a Friday night, what happens Monday morning? Who would you have to call first? How long could you run the business without that system? And then stop talking, which is the hard part, and let them answer. When a prospect says out loud that they'd be shut down for a week, you don't need to convince them of anything.

I want to be careful here, because I'm not telling you to scare people. Overstating a risk is easy to spot and it'll cost you your credibility fast. Being honest means telling them what's serious and being just as clear about what isn't. If you tell them everything is a disaster, nothing is. That proportion is what makes the serious ones land.

There's a reason to care beyond making the prospect feel something. People buy to fix problems they can feel. If they understand what's at stake, they're not comparing your price to a vague worry anymore, they're comparing it to a consequence they can picture, which is a lot easier to justify. That's how you stop getting beat by the cheap quote.

I'd also say this is something you can train. It's not a personality trait, it's a skill. Have everybody who presents a readout write each finding out in those three parts before the meeting. Have somebody else read them and flag anything that still sounds like a ticket note. Record a readout every now and then and watch it together. If you've got T2s and T3s building these reports, and a lot of the time they're the same people presenting them, this belongs in how you evaluate them too.

If the prospect asks what that means, or goes quiet, it didn't land. If they start asking what it would take to fix it, it did.

 

Put the readout format, the three part translation and the questions in your field guide so everyone on your team delivers it the same way, whoever's in the room. That's the kind of thing we help MSP owners build at www.builttorunmsp.com.

Frequently Asked Questions

Why don't prospects act on security assessment results?

Often because the findings are presented in technical terms they can't connect to their business. When a prospect doesn't understand how serious a finding is, they nod and say they'll think about it instead of acting.

How do you explain cybersecurity risk to a non-technical business owner?

For each finding, say what it is in plain words, what it could do to their specific business, and what it would cost them in time, money or trust. Avoid technical names unless the owner asks for them.

How do you get a prospect to believe change is needed without pushing them?

Ask questions that lead them to the consequences themselves, such as what would happen Monday morning if a key account was taken over on Friday night, and then let them answer. A conclusion they reach on their own carries more weight than one they were handed.

How can an MSP train its engineers to explain findings to clients?

Have each presenter write every finding in plain language before the readout, have a second person review it, and review recorded readouts together. Treat it as a skill to coach, and include it in how you evaluate the engineers who present.

About the author
Bruce McCully

Bruce McCully

Bruce McCully built his first company, an MSP, from zero to $8.5 million in recurring revenue. A significant part of that came from cybersecurity incident response. Going into hospitals at 2am and recovering them from ransomware attacks. He didn't learn what happens when a business is unprepared by reading a case study. He was in the room when it happened. Then he founded Galactic Advisors. He scaled it to eight figures in recurring revenue, then stepped down as CEO to focus on MSP Advancement full time. Not because he lost interest. Because the systems he built meant the company no longer needed him to operate it day to day. He remains Chairman of the Board and majority owner. And now he's doing the only thing he wanted to do all along: helping MSPs level up.