
"My IT guy has it covered": what to do when your security pitch stalls
The short answer
When a prospect says "my IT guy has it covered", stop selling the technical problem. Talk about what it means for their business, ask questions about how they work, and speak to the person who feels the problem (usually the owner or an operations manager), not the person who would have to admit it exists.
On this page
You'll hear it in different words: "we have an IT guy", "our IT team has it covered", "we already have IT support". The answer is the same.
By Hrant Ziroyan, COO and co-founder of 0gaps. Updated 22 November 2026.
Key takeaways
- "My IT guy has it covered" usually means "I can't judge this, and I trust the person I have", not "the gap is closed".
- A technical finding forwarded to an in-house IT person is often dismissed, because agreeing means admitting a miss.
- Explain the gap as a business consequence, such as a fake invoice sent in the company's name.
- The owner or operations manager is often a better first contact than the IT person.
- If they forward it anyway, send a one-page summary written for both the owner and the IT person, and agree when you will check back.
I'm Hrant, COO and co-founder of 0gaps. A large part of my week is talking to the MSPs who use our product. Recently one of those calls changed how I think about the first conversation with a prospect, so I want to share it.
The call that started this
A business development manager at an Australian MSP told us something we didn't want to hear, and it was useful.
She sells IT services to construction, civil engineering and architecture firms. She is a salesperson who understands tech, not a technician. She tried what many MSPs try: open with a real security finding, show the prospect a screenshot, explain the risk.
Here is what happened, more than once:
- She explained the problem to the owner or manager.
- They said "my IT guy has it covered."
- If she sent a screenshot, they forwarded it to that IT person.
- The IT person said it was fine. Conversation over.
Her experience isn't unusual. "We already have someone" is one of the most common objections MSPs write about (see Giant Rocketship's list of top MSP objections and SmarterMSP on cold calls, where the author says it's rare to call someone who doesn't already have IT support). What her story adds is why the security finding didn't survive it.
Why the security finding dies in the forward
The finding is real. The problem is who ends up judging it.
When a non-technical owner gets a technical warning, they do the sensible thing: they ask the person they trust. That person is now being asked, in effect, "did you miss something?" Almost nobody answers yes to that question, especially to a stranger.
So three things work against you:
- The owner can't judge it. Words like DMARC, SPF or p=none mean nothing to them. They have no way to tell if you are right.
- The IT person has a reason to dismiss it. Agreeing with you means admitting a gap in their own work.
- You aren't in the room. The conversation about your finding happens without you.
The fix isn't to drop the finding. It's to change what you say about it, and to whom.
Talk about the consequence, not the setting
Owners don't buy a DNS record. They buy fewer bad days.
Translate every finding into what can happen to the business. For example, a missing or "monitor only" DMARC policy (p=none) is not "a DMARC misconfiguration". In plain words: someone can send an email that looks like it comes from your company, for example a fake invoice to one of your clients, and nothing stops it.
That version needs no technical knowledge to understand, and the owner doesn't need their IT person to explain it. It is also very common. In 0gaps scans of 192,586 company domains, more than half (55.3%) had no DMARC record or a DMARC policy set to "none".
Source: 0gaps scans of 192,586 company domains, April to November 2026. Data as of 11 November 2026.
We go deeper on this in Why DMARC p=none is the easiest security conversation to open and on the general idea in why we lead with the gap.
Talk to the person who feels the problem
For many MSPs, an IT manager on staff is a sign the business is hard to win, not the right person to call.
This was the second thing she told us, and it surprised us. Like most tools in this space, we had been treating the IT decision maker as the best contact. For her, the better person was usually the operations manager or the head of business development. And the right role changed by industry.
That makes sense when you think about who feels the problem:
| Who | What they care about | How a security gap lands with them |
|---|---|---|
| Owner / managing director | Risk, reputation, cash | "Could this cost us a client or a payment?" |
| Operations manager | Things running, people not blocked | "Could this stop work or confuse our clients?" |
| Office or practice manager | Day-to-day admin, often the "accidental IT person" | "Is this one more thing I have to deal with?" |
| In-house IT person | Their own systems and reputation | "Is this person saying I missed something?" |
A few practical rules we took from this:
- If the company has a real IT team, it may not be your best target. Spend more time on businesses where IT is a part-time job for someone with another role. NinjaOne calls these people "involuntary IT managers": staff who spend hours a week on IT tasks that aren't part of their job.
- Pick the contact by industry, not by title. In a construction firm with workshops in two cities, the operations manager feels downtime first. In a small architecture practice, it may be the principal.
- Ask, don't assume. On the first call, "who looks after IT for you today?" tells you whether you're talking to the right person.
Ask questions written for their role
A good discovery question makes the prospect describe the problem in their own words. Then it's their problem, not your pitch.
Questions that work better than "did you know you have a security issue?":
- For an operations manager: "If email stopped working for a day at one of your sites, what would that cost you?"
- For an owner: "Has a client ever asked you about a strange invoice or email that looked like it came from you?"
- For an office manager: "When something IT-related breaks, who do people come to? How much of your week does that take?"
- For anyone: "When you get security questions from a client or an insurer, who answers them?"
None of these mention a setting or a tool. All of them lead back to the gap you found, and let you explain it as an answer, not an accusation.
If they still want to send it to their IT person
Let them. Just make the forward work for you.
A forwarded screenshot of a DNS record invites a quick "that's fine." Instead, offer a short, one-page summary written for two readers:
- For the owner: what the gap means for the business, in one or two plain sentences.
- For the IT person: the exact finding, and how anyone can check it from outside in a few minutes.
- No blame. Say that this kind of gap is common and easy to miss, even in well-run companies.
Then ask the owner one thing: "Would it be OK if I check back in a week to see what they found?" You stay in the conversation instead of waiting for a verdict you'll never hear.
If the IT person fixes it, that's fine too. You were right, you were polite, and the owner will remember you the next time something goes wrong. (For how to stay on their radar after a "no", see How to win a business that already has an IT provider.)
What we're changing at 0gaps
Most people who use 0gaps are MSP owners and technical staff. But some MSPs, like hers, have dedicated salespeople who understand tech without being technicians. This call reminded us that we have to work well for both. A technical owner wants the exact finding. A salesperson needs to know why to contact this company today, and how to explain the gap to someone who isn't technical either.
We don't want to promise features before they exist, so here is only what's true today: marketing AI agents for MSPs like ours find local companies with technical gaps your MSP can fix, identify the decision maker and help you run personal outreach every week. We are now talking with more MSP sales teams to understand who they actually want to reach, and how they want the gap explained.
If you sell for an MSP, as an owner, a technician or a salesperson, and this sounds familiar, I'd like to hear from you. Your answer will shape what we build next. And if you want a simple way to keep outreach going alongside everything else, try a 20-minute weekly routine.
FAQ
What does "my IT guy has it covered" really mean?
Usually it means "I can't judge what you're telling me, and I trust the person I already have." It is rarely a statement about the actual gap. Answer it by explaining what the gap means for the business in plain words, not by arguing about the technical details.
What if the prospect says "we already have IT support"?
It's the same objection in different words, common when the business uses an outside IT support company. Thank them, explain what the gap means for the business, and offer to send a short summary they can share with their provider. Don't criticize the provider.
Should MSPs contact the IT manager or the business owner?
For most small businesses, contact the owner or an operations manager first. They feel the business impact of an IT problem. An in-house IT person is a valid contact for technical follow-up, but they are often the person least likely to welcome an outside finding.
Do security-led pitches work for MSP sales?
They can, if the finding is real and explained as a business consequence. They often fail when the prospect is non-technical and the finding is shown as a technical setting, because the prospect hands it to their IT person to judge.
What should I send if the prospect wants to forward my finding to their IT person?
A one-page summary: the business consequence in plain words for the owner, the exact finding and how to check it for the IT person, and no blame. Then ask the owner if you can check back in a week.
What questions should an MSP ask a prospect on a first call?
Ask about the business, not the technology: what a day without email would cost, whether clients have ever received fake emails in the company's name, who handles IT today, and who answers security questions from clients or insurers.

Written by
Hrant ZiroyanCOO and co-founder
Hrant Ziroyan is COO and co-founder of 0gaps. He leads 0gaps operations, making sure MSPs get high-quality leads and a smooth start.
Hrant Ziroyan on LinkedInKeep reading
- PlaybookHow to win a business that already has an IT provider (without trash-talking them)Most good prospects already have IT. Here's how MSPs start the conversation with a gap anyone can check, handle "we already have someone", and stay on the radar.
- PlaybookWhy DMARC p=none is the easiest security conversation to openA one-line DNS record tells you a prospect started on email security and stopped halfway. Here is how to turn that into a first meeting.
- OperationsThe 20-minute weekly marketing routine for MSP ownersWhat to review, what to approve and what to ignore each week, so marketing keeps moving without eating your week.