How MSPs Build the Kind of Client Rapport That Survives a Budget Review
You walked out of the meeting feeling good. The handshake was firm, the small talk landed, and you even got a laugh with the printer joke. You found out their kid plays travel soccer too. They liked you. You could feel it.
Then came renewal season. And your stakeholder couldn't explain to the CFO why your cybersecurity services were worth keeping.
Most of us miss that gap entirely. We confuse social rapport with the kind of rapport that survives a budget review. The schmoozing, the common ground, the "we really clicked" feeling after a prospect meeting…
All of that is real, and none of it is sufficient when the CFO starts asking hard questions.
There's a line from the movie Dan in Real Life worth borrowing here: "Love is not a feeling. It's an ability." Rapport works the same way. It's not a personality trait you're born with; it's a set of skills you practice until they become second nature. If your cybersecurity offering needs executive-level support to survive, those skills are the difference between a client who renews without blinking and one who quietly disappears at the end of the contract.
What Real Rapport Looks Like
When you've built genuine rapport with someone at the budgetary authority level, a few things become true. Your stakeholder believes you understand their business pressures, not just their security gaps. They bring you problems early because they've learned that doing so triggers a conversation, not a sales pitch. And when someone in their organization questions the cost of your engagement, they have both the words and the motivation to defend it.
A client we work with directly on enterprise cyber risk management called during budget planning and said, "I want to talk about what your price increase will be." They weren't questioning the cost. They were planning for it to grow. That's the relationship you're building toward.
The Listening Skills That Get You There
You get there through listening. Not waiting for your turn to talk, not composing your pitch while the other person is still explaining their problem, but listening with the intent to understand both what they're telling you and what they haven't said yet.
Chris Voss, who spent years as the FBI's lead hostage negotiator, teaches a technique called mirroring. After someone speaks, you repeat back a few of their key words. They say, "The board keeps asking about cyber risk and I don't have good answers." You say, "Don't have good answers?" Then you stop and let the silence sit. Almost every time, they fill it with something deeper, the real problem behind the stated problem. You never get there if you jump in with your solution first.
Labeling is the next layer. You name what you observe someone experiencing. "It sounds like you've been carrying the weight of this without much support." "It seems like the last vendor left a bad taste." You don't have to be right. If your label misses, people naturally want to correct you, and the correction often gives you more than a direct question ever would. When the label lands, you'll know it. A "that's right," a shift in body language, a moment where the professional guard drops and they start talking to you like someone who gets their world.
Open-ended questions tie the whole thing together. Questions that start with "how" or "what" give the other person room to think and draw out real information. "What does risk look like from where you sit?" opens a conversation about their world, not your products. "How can I make this easier for your team?" signals partnership rather than salesmanship. These questions work in first meetings and in year-five renewals, and the more you practice them, the more natural they become.
Where This Connects to Last Month
I talked last month about incorporating your client's business objectives into how you describe your services, drawing on Donald Miller's StoryBrand framework. The question I left unanswered then was where those business objectives come from in the first place. They come from listening, from mirroring, from labeling and asking the right questions. The rapport skills and the value translation are part of the same conversation — you can't do one well without the other.
The Secret Weapon: The Franklin Effect
In 1737, Benjamin Franklin had a rival in the Pennsylvania legislature who'd publicly opposed him. Franklin didn't fight back or try to win him over with favors. He wrote a note asking to borrow a rare book from the man's personal library. The rival sent it immediately, Franklin returned it with a thank-you note, and from that day forward the man treated Franklin as a close friend until his death.
The psychology behind it is straightforward. When you ask someone for help, you signal that they know something you don't. That's respect. Their brain resolves the cognitive dissonance in the most flattering way possible: "If I helped this person, I must like them." When you're sitting across from an owner or a CFO, that means asking them to help you understand what a successful year looks like for someone in their position. You're asking for guidance about their business, using an open-ended question, and activating the Franklin Effect all at once.
Talk Tracks You Can Use This Week
Rather than borrowing from Voss, Miller, and Franklin wholesale, here are some talk tracks adapted specifically for cybersecurity client relationships. Use them as written or make them your own — the structure matters more than the exact wording.
When you're trying to understand their world: "I know cyber risk is my world. Your world is running this business. Help me understand what your biggest pressure points are right now."
When you want to learn from their past experience: "You've been through this process before with other providers. What worked, and what didn't?"
When you want to frame the engagement around their goals: "If we get this right, what does success look like for you in the next twelve months?"
When you need to know what evidence matters to them: "What would you need to see from me to feel confident explaining this program to your board?"
When you're building a deliverable and want their input on it: "I've been working on your executive report, but I could use your help. What would make it more useful for your board meetings?"
When you want candid feedback on the relationship itself: "Could I borrow your analytical skills for a moment? What's the one thing I could do differently that would make this program indispensable for you?"
Each of these asks for help, opens with "how" or "what," and surfaces the business context you need to frame your services in language that resonates. They work when the relationship feels strong and when it feels like it might be slipping.
Go Practice
Pick the opportunity you're most tempted to walk away from — the prospect who said "no budget this year," the client whose engagement feels like it's quietly fading. Walk in with nothing to lose and try something different. Mirror instead of pitch. Label instead of defend. Ask for help instead of leading with your solution.
Some of those conversations will turn around. The ones that don't will still sharpen you for the ones that eventually will.
Business rapport isn't a feeling, it's an ability. Go practice it.
