PUBLIC EVIDENCE · DATED SNAPSHOTILLUSTRATIVE
SCOUTz public domain evidence prepared for an MSP conversation
What should an MSP say when a prospect asks, “Why were you looking?”

Disclose the public review, name its boundary, show the source, and acknowledge any surprise. Do it in that order and keep it short.

The Scan No One Asked For covers the posture behind this moment. This guide is for the thirty seconds after a prospect's tone shifts from curious to guarded.

1. Disclose the review

Before I called, I looked at what your domain publishes publicly.

Then name the source in the same breath: “Your DMARC record is in monitoring mode. I pulled that from your public DNS before we spoke.” One plain sentence does more work than a paragraph of justification after the owner feels caught off guard.

2. Name the boundary

This was one dated look at public configuration. It was not internal access or ongoing monitoring.

Most of the discomfort comes from an assumption that the review is continuous, hidden, or inside the business. State exactly what happened so the prospect does not have to imagine the broadest version.

3. Show the source

Open the DNS record, certificate, or response that supports the observation.

Do not describe the evidence from behind a report. Put it on the screen. An inspectable claim can become a useful question instead of a contest over authority.

4. Acknowledge the surprise

If the evidence landed awkwardly, recognize the surprise without apologizing for an accurate public observation.

“I'm sorry this is the first time you're hearing that I looked” is different from apologizing for the accuracy of the source. Use it only when it is true.

This is a trust moment, not an objection script

The 3AM Test for MSPs asks whether the client will call without hesitation when something breaks. A prospect who feels scouted in the first meeting is already making that judgment. Handle the moment plainly, show the evidence, and let the owner decide whether the conversation should continue.