Handling Objections & Following Up

Introduction

In IT Services and Managed IT, closing a deal is not a one-call event. Your first proposal rarely gets a straight “yes” on the spot. Prospects usually slow down because they’re not just deciding on price—they’re deciding on risk. They want to know: Will this team break something? Will the rollout take over their business? Will we lose visibility or control? At Level 2, your job is to catch those hidden concerns early, then follow up in a way that keeps the decision moving.

Understanding Objections

In managed IT sales, objections are often a wrapper for something more specific. “I need to think about it” usually means the prospect is worried about one of these:
- Disruption: “Will you shut us down, or mess up our systems during migration?”
- ROI and cost control: “How do I know this will reduce incidents and downtime, not add overhead?”
- Credibility: “Have you done this before with companies like ours?”
- Timeline: “When will we be live, and what will it require from our staff?”

Listen for clues in the wording. If they mention “integration,” “timelines,” “onboarding,” or “who owns what,” they’re likely worried about implementation. If they push back on “budget,” they might still be open if you can show a clear path to outcomes and predictable costs.

Building Trust

In IT Services, trust comes from proof and clarity. Prospects don’t want vague promises—they want evidence that you can run a stable rollout and handle real-world IT chaos.

Use three trust builders:
1) Proof from similar work: Share a short rollout story (what you changed, how long it took, and what improved). For example, “We replaced patching and monitoring for 120 endpoints, reduced critical incident repeats by X%, and completed onboarding without extending downtime windows.”
2) Risk-reduction: Offer a bounded commitment that reduces fear. Examples include a pilot with defined success criteria, a fixed onboarding plan with milestones, or an implementation “stoplight” timeline where they always know status.
3) Professional control: Show you have process—documented onboarding, RACI ownership (who does what), change windows, escalation paths, and clear reporting.

The Power of Follow-Up

Follow-up in Managed IT is not “checking in.” It’s helping the buyer feel safe every step of the way.

A strong follow-up rhythm for managed IT looks like this:
- After the discovery: Send a recap email within 24 hours. Include what you heard, the risks you identified, and the next step.
- After the proposal: Follow with a short “implementation reality check.” Explain onboarding phases, what they must prepare (access, contacts, system lists), and what you handle.
- During evaluation: Provide decision support assets—security and backup overview, sample ticket response SLA, monitoring coverage map, and a draft transition plan.
- When they stall: Use a “new information” touch. For example, share a brief note about a common failure point you see (missing MFA coverage, unmanaged endpoint drift, unclear escalation rules) and how your onboarding prevents it.

Follow-up should be consistent for 60–180 days, because many IT buyers compare vendors, request internal approvals, and wait until their schedule frees up. Your system should keep the conversation alive with value.

Conclusion

Objections and delays in Managed IT usually reflect fear about outcomes, implementation risk, and credibility—not just price. If you probe for the real concern, build trust with proof and controlled onboarding, and run a follow-up plan that reduces uncertainty, you turn stalled deals into signed agreements.