VoIP Strategy
MSP Growth
Revenue Architecture
VoIP Strategy
MSP Growth
Revenue Architecture
A Structured Sales Methodology for MSP Sales Reps — Selling Managed IT & VoIP/Communications Services
Map the client's world completely before you say anything about your solution.
Reveal what the client doesn't own — and what it's costing them.
Quantify the risk of inaction. Align on investment.
Design the long-term relationship before the contract is signed.
Informed by Gap Selling · MEDDIC · Winning by Design
Most sales frameworks were built for software companies. They assume a long enterprise sales cycle, a champion inside the account, and a product that's easy to demo. The MSP sale — and especially the VoIP communications sale — shares almost none of those characteristics.
The MSP rep is selling to a business owner who is also the IT decision-maker, the budget holder, and the person who will personally feel it if your solution fails. The communications sale adds another layer: you are displacing something the client already has and depends on every day. That is a fundamentally different sales motion.
| Methodology | C.O.R.E. Contribution | What It's Missing for MSP/VoIP |
|---|---|---|
| Gap Selling | Forces reps to identify and widen the gap between current and desired state before presenting anything | Doesn't account for infrastructure displacement or recurring revenue economics |
| MEDDIC | Rigorous qualification — economic buyer, decision criteria, champion, metrics, and pain identification | A checklist, not a motion. Doesn't teach reps how to guide a decision through stages |
| Winning by Design | Recurring revenue logic, the bow-tie model treating sale and post-sale as one continuous arc | Built for SaaS. Doesn't address the owner-buyer dynamic or the carrier displacement conversation |
The Core Principle: The goal of C.O.R.E. is not to teach reps how to persuade. It is to teach reps how to diagnose, map the gap, quantify the risk, and guide a decision. Persuasion is what happens when your solution doesn't have a strong enough case on its own. A well-executed C.O.R.E. conversation makes persuasion unnecessary.
Each stage has a primary objective, a set of diagnostic questions, a specific thing to listen for, and a clear condition that must be met before advancing. It is not a script. It is a structure inside which reps develop their own style and voice.
| Stage | Buyer Is Asking | Rep's Job |
|---|---|---|
| C — Current State Mapping | "Is this person worth talking to? Do they understand my world?" | Understand the full picture of where the client is today — their tech stack, their voice setup, their actual pain |
| O — Ownership Gap | "Wait — I'm missing something here. What is the real cost of how things are set up now?" | Reveal that the client doesn't own what they think they own, and show the business and financial consequences of that gap |
| R — Risk & Revenue Alignment | "If I act, what exactly am I buying, and what does staying still actually cost me?" | Quantify the risk of inaction, connect it to money, and align on the investment level required to close the gap |
| E — Expansion Architecture | "What does this look like long term? Can I trust this partner to grow with me?" | Set the conditions for a long-term relationship, establish success milestones, and design the expansion path before the contract is signed |
The single most common mistake MSP sales reps make is moving to a solution before they understand the problem. They hear "we need phones" and they start talking about seats, features, and pricing. The prospect feels sold at, not heard. Authority is gone before the second call.
Current State Mapping is the discipline of understanding the client's world completely before you say anything about your solution. The kind that makes a business owner feel like they're talking to someone who has seen their specific situation before and knows exactly what it costs.
Reps who only probe the first layer miss the conversation that closes deals.
What systems, vendors, and contracts are actually in place today
The current tech landscape and vendor relationships — the baseline
How the current setup is affecting the day-to-day running of the business
Where friction, cost, and lost productivity are actually living — the pain
What the current state is costing the business at the ownership level — revenue, valuation, risk
Why the owner should care enough to make a change — the urgency
| What They Say | What It Actually Means | How to Probe Deeper |
|---|---|---|
| "It mostly works fine" | They've normalized a level of pain they shouldn't accept | "What does 'mostly' mean? Tell me about a time recently when it didn't work." |
| "We've been with them for years" | Loyalty based on familiarity, not performance | "What would need to happen for you to consider making a change?" |
| "Our IT guy handles that" | Unclear ownership — may be part-time, overwhelmed, or unqualified | "Is that a dedicated internal resource, or someone wearing multiple hats?" |
| "We're not really a phone-heavy business" | They haven't connected calls to revenue — probe Layer 3 | "How do your clients typically reach you when they need something urgently?" |
| "We're locked in a contract until next year" | Not a blocker — it's a timeline. A future opportunity with a specific date | "When exactly does that renew? Let's make sure we're talking at the right time." |
Stage Complete When: You can describe the client's world better than they can. That is the moment authority shifts. When you say back to them what is happening in their business with more precision than they used to describe it themselves, they stop treating you as a vendor and start treating you as a diagnostician.
Most business owners believe they are "in control" of their technology. They pay a monthly bill. They have a vendor relationship. Things mostly work. What they don't realize is that paying a bill is not the same as owning the infrastructure.
The Ownership Gap stage exists to reveal that distinction — clearly, without pressure, and with evidence drawn from their own answers in the Current State stage.
The infrastructure ownership question is simple: "If your IT provider stopped showing up tomorrow, how long before things started breaking?"
Most clients have never seen a total cost of ownership analysis of their communications setup. This is one of the most powerful tools in the Ownership Gap conversation.
This is the gap that business owners feel most acutely once you surface it: are technology decisions made in service of the business, or is the business adapting to the technology it has?
The Ownership Gap only creates urgency when it has a number attached to it. Walk the prospect through a simple gap calculation. You do not need to be precise. You need to be credible.
| Cost Category | What to Ask | Rough Estimate |
|---|---|---|
| Monthly carrier cost | "What are you paying per month for voice services today?" | Their actual number |
| Support overhead | "How many hours per month does your team spend dealing with phone issues?" | Hours × avg. hourly rate |
| Missed/lost calls | "How many inbound calls do you estimate you miss per week? What's the average value of a new client?" | Calls missed × conversion × avg. deal |
| Downtime cost | "Has your phone system ever gone down during business hours? What did that cost you?" | Revenue at risk per hour × historic incidents |
| Valuation drag | "Do you have plans to sell the business? Buyers discount carrier-controlled infrastructure." | Qualitative — significant for exit-planning owners |
Why This Works: The gap calculation is not about winning an argument. It is about helping the business owner see something they could not see before you arrived. When they do the math themselves — even roughly — the urgency is theirs. Not yours. That is the difference between persuasion and diagnosis.
The Current State stage mapped the client's world. The Ownership Gap stage revealed what it is costing them. The Risk & Revenue Alignment stage answers the next question every business owner asks, even if they don't say it out loud: "Okay. So what do I do about it, and what does it cost?"
| Risk Dimension | What It Means | For Managed IT | For VoIP |
|---|---|---|---|
| Operational Risk | The risk of day-to-day failure | Downtime, slow resolution, productivity loss | Dropped calls, missed leads, failed routing |
| Security Risk | The risk of a breach or data loss event | Ransomware, phishing, compliance failure | Toll fraud, SIP exploitation, unsecured calls |
| Financial Risk | The risk of paying more for less | Unpredictable IT costs, project overruns | Carrier lock-in, add-on pricing, margin lost to agents |
| Valuation Risk | The risk of reducing business value | Undocumented systems, no transferable IP | Carrier-controlled infrastructure discounted by buyers |
| The Objection | What It Really Means | The Response |
|---|---|---|
| "It's more than we expected to pay." | They're comparing to their current cost, not to the risk they're carrying | "What are you currently paying — all in — for IT support? And what was the cost of [incident they mentioned]? We're not asking you to spend more. We're asking you to spend what you're already spending in a way that actually removes the risk." |
| "We're happy with who we have." | Loyalty based on familiarity — the Current State stage didn't surface enough pain | "I hear that. Can I ask — what does 'happy' look like for you? The gaps we identified earlier exist in your current relationship. Happy with the relationship, or happy with the outcomes?" |
| "We don't want to switch phone systems right now." | Fear of disruption — they've heard migration horror stories | "I understand. Migrations have a bad reputation because most of them are done poorly. Can I show you what a managed migration looks like when it's structured correctly? Most clients are surprised by how non-disruptive it actually is." |
This stage reflects the Winning by Design bow-tie model — treating the sale and the post-sale as a single continuous revenue arc. The handoff between "closing a deal" and "delivering a service" is where most MSPs lose the strategic advantage they built during the sale.
Before the contract is signed, the rep establishes three things: what success looks like to this specific client, how success will be measured and reviewed, and what the natural next steps are as the business grows.
Based on everything surfaced in the C, O, and R stages, work with the client to define what a successful first 90 days looks like — in measurable terms. Not vague outcomes like "better IT" or "more reliable phones."
Establish the review cadence before the contract is signed — not as a service feature, but as a commitment from both sides.
"We do a structured 30-day check-in, a 90-day impact review, and a quarterly business review every quarter. At each of those, we're reviewing specific metrics against the success criteria we define today. Does that work for you?"
"The quarterly review is where we discuss what's next — whether that's expanding the scope of what we manage, adding new services, or adjusting the program to reflect changes in your business. It's not a sales call. It's a strategy call."
Show the client their growth path before they have signed the first contract. A transparent map that shows what a mature technology partnership looks like, so they can see themselves moving through it over time.
Show this path during the sale, not after it. "Here's where we'd start, and here's what the next few years could look like as your business grows. We won't push you up this ladder. You'll want to move up it when the value becomes obvious." That framing builds enormous trust — and the expansion revenue takes care of itself.
The Deal Scorecard is the qualification and advancement tool for the C.O.R.E. framework. It prevents reps from carrying phantom pipeline — deals that feel real but have no structural basis for closing. Score each criterion 0, 1, or 2. A deal should not advance to the next stage until the criteria for the current stage score at least 6 out of 8.
| Criterion | 0 — Not Met | 1 — Partial | 2 — Confirmed |
|---|---|---|---|
| C I can describe their current state at all 3 layers | |||
| C They've acknowledged at least one Layer 2 (operational) pain | |||
| C I know their current voice setup and contract status | |||
| C They've connected IT or voice quality to a business consequence | |||
| O They've acknowledged at least one ownership gap | |||
| O We have a rough gap calculation they validated | |||
| O They've expressed urgency in their own words, not mine | |||
| R I have confirmed the economic buyer is in the conversation | |||
| R Budget range has been validated — they're in the market | |||
| R Decision timeline is defined and real | |||
| E We have defined what success looks like in measurable terms | |||
| E Review cadence has been agreed to by both sides | |||
| E They can see the expansion path and have reacted positively |
A low score is not a failure. It is information. It tells you exactly which part of the C.O.R.E. conversation did not land — and gives you a precise question to go back and answer before you move forward.
For use before calls, during pipeline reviews, and for training new reps.
| C — Current State | O — Ownership Gap | R — Risk & Revenue | E — Expansion | |
|---|---|---|---|---|
| Objective | Understand the client's world at all 3 layers before saying anything about solutions | Reveal that the client doesn't fully own what they think they own — and quantify the gap | Quantify risk, confirm the economic buyer, and align on investment | Define success, establish the review cadence, and map the expansion path |
| Key Question | "What does your current setup actually look like — and where is it creating friction?" | "If your provider left tomorrow, what would you lose? And what is that costing you?" | "Which risks feel most urgent, and who needs to be part of the decision to address them?" | "90 days from now, what would need to be true for you to call this a success?" |
| Stage Complete When | You can describe their world better than they did | They have expressed urgency in their own words | Budget, authority, and timeline are confirmed | Success is defined and the expansion path is visible to both sides |
| Never Do This | Lead with features or solutions before mapping current state | Create urgency from pressure instead of from their own stated consequences | Proceed without confirming the economic buyer is in the room | Skip to expansion before the first contract is agreed |
The one-page qualification tool used to score every active deal in your pipeline. Know exactly where each deal stands — and whether it should advance, stall, or exit.
Enter your email and we'll send it straight to you.
The C.O.R.E. framework is one pillar of MSP Revenue Architecture. The Diagnostic tells you exactly where your revenue system stands — and what to build first.