Every MSP has a handful of accounts that are underperforming. The client missed the last two meetings. The partner promised to push prospecting licenses and never did. The renewal is coming up and the usage data does not support the price. The temptation in each case is to blame the other side. They are not engaged. They are not serious. They have other priorities.

The seller who reliably turns those accounts around does something different. Before they diagnose the client, they diagnose themselves.

Heather, a Cynomi partner account manager, describes this as the first rule of account work. When a partner is not performing the way they should be, her opening move is to take responsibility. “That’s my responsibility. That’s the only way I can help them improve, because, honestly, if what I’m doing isn’t working, I have to change what I’m doing.” It is a small shift in framing. It tends to produce a much larger shift in what happens next.

This post is for MSP owners, sellers, and partner account managers who want a reliable move for the moments when a relationship is drifting. The accountability reset does not work every time, but it works more often than the alternative, and the cost of trying it is almost nothing.

Why Blame Stalls the Conversation

When a deal or an account is stuck, the natural instinct is to identify the cause outside yourself. The client is too cheap. The partner is too disorganized. The decision-maker is too busy. Sometimes those things are true. More often, they are convenient stories that let you skip the harder question of what you could have done differently.

Blame also kills the next conversation. If you walk into a quarterly business review already convinced the partner is the problem, you will phrase every question as an accusation, whether you mean to or not. “Why haven’t you converted the trials?” lands differently than “Where did I lose you on the trial motion?” The first question makes the partner defend themselves. The second one invites them to tell you the truth.

Defensive partners do not give you useful answers. They give you excuses that get you both off the call without solving anything. And then nothing moves.

The Accountability Reset

Heather’s move is simple in form and hard in practice. When an account is underperforming, she goes to the partner first with a posture of ownership. Something like: “I’ve been thinking about where we are on the growth plan, and I don’t think I’ve set you up well. Let’s meet. I want to figure out what I’ve been doing that isn’t landing for you, and I want to fix it.”

Three things are true about that opening. First, it is almost always accurate. An account that is not performing is usually an account where the plan the two of you built together had gaps, and both sides share the responsibility for those gaps. Second, it drops the partner’s defenses. They came into the meeting braced for a confrontation. They get a collaborator instead. Third, it earns you the right to ask the harder follow-up question.

Once the partner is talking openly, you can move into diagnosis. What is getting in the way? Is the messaging not landing with their clients? Is the pricing off? Is the internal champion no longer in the role? Did the technical team lose faith after a rough implementation? Every one of those answers points to a specific next step, and you cannot get to any of them if the partner is still defending their track record.

The Point Is Not to Flatter the Partner

Leading with your own accountability has to be genuine, not a disarming move dressed up as humility. If you walk in saying “this is my fault” while privately thinking “this is your fault,” the partner will hear the gap.

Heather’s version of the move is grounded in a real belief: she cannot help a partner improve if she is not willing to change what she is doing. That belief holds even when the partner is clearly part of the problem. You change what you can change, which is your own approach. When your approach shifts, the partner’s behavior usually shifts with it, because the relationship no longer feels like an interrogation.

There is a test for whether you are doing this right. After the accountability conversation, the two of you should leave with a short list of things you are going to do differently, not the partner. One or two of those items may eventually involve actions on the partner’s side, but they come up later, after the reset has taken hold, and they come up in the context of a shared plan.

How to Apply the Same Move to Client Relationships

The accountability reset travels well beyond account management. It works for MSPs having hard conversations with their own clients.

Picture the client whose users keep clicking on phishing emails. The temptation is to tell the client their employees need more training, their culture needs more discipline, their executives need to take security more seriously. All of that may be true. And none of it will land if you say it first.

What works better is leading with what you missed. “The phishing simulation results suggest I haven’t pitched the training program in a way that got buy-in from your leadership. That’s on me. Let’s figure out what we need to do differently so the next campaign shows up.” Same facts, same problem, different owner at the start of the sentence. The client hears you as a partner working the problem with them. The conversation keeps going.

Clients forgive almost everything from an MSP who shows up with humility. They forgive very little from an MSP who shows up with a finger pointed at them.

A Small Caveat

Accountability works best when it stops short of self-flagellation. You are not supposed to make up problems to own. You are supposed to find the part of the problem that is yours, claim it openly, and use that claim as the opening of a productive conversation.

If, after an honest review, you did everything you reasonably could, and the partner or client did not meet their end of the work, the move is different. You have a direct, specific conversation about what needs to change, and you make clear what happens if it does not. That kind of conversation is fair, not cruel. And it is much easier to have after you have already proven that you are willing to look at yourself first.

One Experiment for This Week

Pick the account in your book that is most stuck. Before your next meeting, write down three things you could have done differently. Bring them to the conversation. Start there.

Watch what happens.

Cynomi’s GTM Academy Sales Kit includes account-review templates, QBR frameworks, and coaching scripts designed to help partner-facing sellers run accountability conversations without losing credibility. If you want a structured way to run this move across your book, you can pick up the kit here.

When a client’s budget tightens, the cybersecurity line is usually the first one with a target on it. Executives see it as overhead. Nobody except the IT director can measure what it prevented. And the people who benefit most from the investment, the board and the CEO, rarely feel the risk directly until something goes wrong.

Attackers know this. Heather, a Cynomi partner account manager, puts it plainly: when the economy wobbles, one of the first things companies cut is cybersecurity, and the hackers know that better than anyone. If you are an MSP selling into that environment, hoping the client will stay committed on their own is not a plan. You need to give them the questions that make cutting the budget feel more expensive than keeping it.

This post is for MSP owners and sellers who are tired of watching good programs get defunded at the worst possible moment. The four questions that follow are ones Heather uses, in some form, on almost every hard client conversation. They are outcome-oriented, they make the risk concrete, and they put the decision where it belongs: on the person whose job is on the line.

Question One: If You Get Hit Tomorrow, Who Handles It?

Most clients have a loose answer to this. “We have backups.” “We have cyber insurance.” “Our MSP would handle it.” Press on any of those and the answer gets shakier. Which vectors are you covered for: data leak, website defacement, ransomware, or business email compromise? Who calls the forensic firm? Who decides whether to pay? Who tells the clients? Who tells the regulators?

The point is not to trap the client. The point is to make them answer the question out loud, in specifics, so they can hear themselves. Most executives have never had to articulate the full response plan, because nobody has ever walked them through it. When they do, the gap between what they believe they have and what they have gets visible in a hurry.

An MSP who can guide a client through that scenario, calmly and in plain language, becomes a different kind of vendor. You are no longer providing a service line. You are acting as the advisor the client should have had all along.

Question Two: How Long Until You Are Back Up, and Can You Survive It?

Downtime tolerance is a better budget conversation than threat frequency, because it is something the business side of the house understands. Ask the CFO what the company’s revenue looks like on a bad day offline, and they can tell you. Ask them whether the company can afford that number for a week, and they will start to do the math in their head.

Heather’s version of this question goes further. How long until you are back up and running? Can you survive that? And for how long? That last part is the one that usually lands hardest. A business that can absorb three days of disruption may not be able to absorb three weeks, and most incidents are closer to the second number than the first. Ransomware recovery timelines of one to three weeks are common. Cyber insurance payouts can take months.

When the client sees that their downtime tolerance and their incident survival window do not match, the cost of the gap becomes easier to quantify. And once you are talking about cost, the cybersecurity spend stops being overhead and starts being a hedge against a larger loss.

Question Three: Whose Job Is on the Line?

This is the question most sellers skip because it feels too personal. That is exactly why it works.

Every serious incident comes with a blame conversation inside the organization. The CEO wants an answer. The board wants an answer. The regulators want an answer. And whoever was responsible for the decision that left the gap open is the person who gets asked. In most mid-market companies, that person is the IT director, the CIO, or the CFO who signed off on the budget.

Asking “who is going to be held responsible if this happens” functions as a service rather than a scare tactic. You are helping the client see their own exposure before an incident does. And once they see it, the budget conversation changes. They are no longer deciding whether to spend money on security. They are deciding whether to carry risk on their own shoulders or distribute it across the security program you are proposing.

Heather’s framing on this is that the conversation has to be realistic. “Do you trust every employee at your organization with your job in their hands?” That is not a rhetorical question. Most clients have never thought about their workforce that way, and when they do, the answer usually surfaces a weakness they had been quietly ignoring.

Question Four: If You Do Not Have the Budget, Who Inside Your Organization Does?

When a client says they cannot afford the program you are recommending, the conversation has just gotten more useful, not less.

Instead of discounting, instead of dropping services, instead of walking away, ask the client who inside the company can unlock the budget. There is almost always somebody, and it is almost always someone the client has not approached yet. Sometimes it is the CEO. Sometimes it is a board member. Sometimes it is the insurance broker who is about to deny coverage unless specific controls are in place.

Then you offer to build the case with them. What do they need to take to that person? What data, what scenarios, what comparisons to peers? The conversation pivots from a no to a joint project. The client is no longer trying to cut you out of the budget. They are trying to help you both justify it.

Heather’s phrasing makes the pivot explicit: “How do we help you afford this? What do you need to take to your company to get you the budget?” It is a small shift. It keeps the two of you on the same side.

Outcome-Oriented Questions, Not Fear-Based Pitches

None of these questions comes from a place of fear. None of them predicts an attack. They ask the client to think through a scenario and answer honestly about what would happen. That posture is the difference between a pitch that shuts down the conversation and a consultation that keeps it open.

If you use these four questions regularly, two things happen. Your client conversations get harder in the first ten minutes and easier for the next ninety. And the budget conversations you had been dreading start producing different outcomes.

Cynomi’s GTM Academy Sales Kit includes full discovery frameworks, talk tracks, and client-facing materials designed to help MSPs run conversations like these at scale. If you want the supporting materials to turn these questions into a repeatable motion, they are available here.

Nobody likes being told they are wrong. That applies to your client’s CFO, your client’s IT director, and the new partner you are trying to expand. It also applies to you. The problem is that an MSP seller’s job sometimes requires telling somebody that what they are doing is putting their business at risk, or that the investment they made last year was in the wrong place, or that the security posture they believe they have does not match the reality.

How you have that conversation decides whether the client stays or walks. Heather, a Cynomi partner account manager who spends her days coaching MSPs through these moments, has a move she uses almost every week. She calls it flipping the script. It is a small reframe with a large payoff, and it rests on a distinction most sellers get wrong: the difference between sympathy and empathy.

This piece is for MSP sellers and leaders who can feel the tension in a client conversation and know they need to push, but are worried about pushing too hard. The answer has less to do with softening your point and more to do with changing whose work the client is looking at.

Sympathy Makes You a Spectator. Empathy Makes You a Partner.

Sympathy sounds like “I’m sorry to hear that.” Empathy sounds like “That’s awful. What can I do?” Both responses are well-intentioned. Only one of them gets you closer to fixing the problem.

Sympathy keeps you outside the situation, offering commentary. Empathy puts you inside it with the client, working on the same side of the problem. When you are building a case for a security investment the client has been resisting, or pointing out that their incident response plan will not survive a real incident, empathy is the only stance that earns you permission to keep talking. Sympathy politely ends the conversation.

The shift shows up in small language choices. You stop saying “you should” and start saying “here’s what I’d do with you.” You stop telling the client what is broken and start asking them what they think is broken, and then building on the answer they give you. Clients will forgive a lot from somebody they feel is in the work with them. They will forgive almost nothing from a person who sounds like a judge.

The Flip: Turn Your Problem Into Their Consult

Here is where Heather’s script move pays off. When you need to challenge a client’s approach but do not want the conversation to turn defensive, do not present the problem as theirs. Present it as yours.

The language sounds something like this: “I’ve been doing X this way and getting Y result. It isn’t working. If you saw me doing that, what advice would you give me?” Then you lay out, in plain terms, the exact problem the client has. Same situation, same missing controls, same unanswered questions. The only difference is the subject of the sentence.

Two things happen. The first is that the client stops protecting the choice they made and starts analyzing it. They are no longer looking at their own work, so the defensiveness drops. The second is that they get to be the expert. Most people do not enjoy being told they were wrong, but they enjoy coming up with the right answer. When the client tells you what the solution should be, and the solution happens to match what you were going to recommend anyway, the plan becomes theirs. Ownership shifts. Implementation gets easier. You do not have to convince anybody of anything because the client already convinced themselves.

Think of it as structure rather than manipulation. You are rearranging the conversation so the client can think clearly, which is hard to do when your ego is in the room. Strip the ego out, and most clients get to the right answer within a few minutes.

Outcome-Oriented Framing Without the Fear

A common failure mode when MSP sellers try to push is that they slip into fear-based language. The threat is the ransomware, the regulators, the cyber insurance renewal that will not get approved. Fear works for about twenty minutes and then the client pushes back, either by minimizing the risk or by cutting off the conversation.

Heather’s alternative is what she calls coming from a place of power rather than a place of fear. You do not tell the client what could go wrong. You ask them what happens if it does. “If ransomware hits tomorrow, what is your response? Who pays for the downtime? Who answers to the board? How long can you operate without the systems you rely on?” These are the same facts, phrased as questions the client answers out loud. You are not predicting a disaster. You are walking them through a scenario and letting them draw their own conclusion. That is a different posture, and it is the one that gets movement.

Notice that none of these questions assume the client is stupid or unprepared. They assume the client is capable of thinking through the scenario once somebody slows them down enough to do it. That posture is empathy in operating form.

When the Client Is Not Performing, Start With You

Heather’s third move is the one that takes the most discipline. When a partner is missing meetings, failing to convert trials, or generally underperforming, her first instinct is to look at her own work before she critiques theirs. “Something I haven’t done correctly. Let’s meet. I’m obviously not doing my job.”

That phrasing is strategic. It is also, when she means it, true. Most of the time, an underperforming partner is underperforming because the plan the two of you built together had gaps. Leading with your own accountability opens up a conversation that a lecture would shut down. The partner drops their defenses, tells you what is going on, and the two of you can troubleshoot the real problem. You keep the relationship intact, and you make progress on the thing that was stuck.

The same move works with clients. If a security program is not landing, ask where the plan you built together missed. The client will tell you. Their answer almost always points to the real issue faster than an audit would.

One Thing to Try This Week

Pick a single hard conversation you have been putting off. Before you have it, write down the problem as if it were yours, not the client’s. Rehearse how you would ask for advice on that problem from a peer. Then have the conversation with that script in your head.

Small change. Large difference in how the other side responds.

Cynomi’s GTM Academy Sales Kit includes conversation guides, discovery templates, and objection scripts designed to help MSPs have these exact conversations without resorting to pressure tactics. If you want frameworks for the harder moments in client work, you can find them here.

Ask an MSP owner to describe what they do, and you will get one of three answers. Some lead with relationship: “I’m the person my clients call first.” Some lead with strategy: “We build roadmaps for our clients’ security programs.” Some lead with selling: “We grow accounts and bring in new logos.” All three answers are correct. The order matters.

Heather, a partner account manager at Cynomi, works with MSPs every day who are juggling all three roles. The ones who grow their books fastest share a common pattern. They treat relationship, strategy, and selling as a fixed sequence rather than three interchangeable levers. Relationship comes first. Strategy follows. Selling is the result.

If you lead with selling, you end up chasing quota. If you lead with strategy before you have the relationship, your recommendations hit a wall. The MSPs who consistently expand inside their accounts build in the opposite direction. This post walks through the sequence, what each stage requires, and how to tell when you are ready to move to the next one.

Stage One: The Relationship Is the Foundation

Relationship work is the part of the job most sellers underinvest in because it does not show up on a dashboard. There is no line item for asking about your client’s kids, or noticing that their office moved, or remembering which team they root for. But those signals are how trust gets built, and trust is what makes the next two stages possible.

Heather describes this as cultivating rather than closing. You are learning what your partner cares about, what their clients care about, what is going on in their business outside of the quarterly business review. You are making yourself easy to call when something is wrong, not just when there is a renewal on the calendar. That cultivation is what separates a vendor who hits every month-end scramble call with “what can you do for me” from a partner who already knows what the MSP is working on and how to help them win.

A good test: if a partner told you tomorrow that they were losing a large client, would they call you? Would they tell you early, or only after the damage was done? The answer tells you how deep the relationship runs, and whether stage two is on the table yet.

Stage Two: Strategy Follows Because You Have Earned It

Once the relationship is real, you can start asking harder questions. This is where strategy lives. You are no longer a vendor checking in. You are an advisor figuring out how to help your partner grow.

Strategy work looks like diagnosis, not prescription. You are asking where the partner’s revenue comes from, which client segments are expanding, which ones are stalling, and which services are underpenetrated. You are asking what their sales process looks like today, where the deals stall, and what they would build first if they had more capacity. You are mapping where their current security offering lands on something like Cynomi’s maturity view and where the gaps are. Then you are working with them to decide which of those gaps is worth closing this quarter.

The questions are specific because you have the standing to ask them. The partner is willing to answer because you spent the prior stage earning that standing. If you skip to strategy before the relationship is real, the partner hears it as a pitch dressed up in a planning meeting. They nod along, thank you for your time, and tell you nothing actionable.

Stage Three: Selling Is the Result, Not the Goal

Selling is where most plans start, and that is the error. When selling is the first thing on your mind, everything you do bends toward the number you want to hit this quarter. You start listening for openings to pitch instead of listening for what the partner is trying to solve. The partner feels it, and the conversation closes down.

Heather’s working principle is that expansion should be the result of the first two stages, not the goal of any of them. If you have built the relationship and done the strategy work, the sale tends to surface on its own. You already know what the partner needs. The partner already knows you can help. The conversation about scope and pricing is the last two percent of the work, not the whole job.

This is a different mental model than the one most sellers were trained on, and it takes discipline. You have to be willing to walk out of a partner meeting without a close if the partner was not ready for one. You have to trust that the work you put in at stages one and two will produce the number at stage three. That trust gets easier when you see it work a few times.

How to Tell Which Stage You Are In

A few quick diagnostics. Your relationship with a partner is strong enough to move to strategy when the partner tells you things they have not told their other vendors. It is ready for selling when the partner starts asking you what you would do next. If they are still waiting for your pitch, you are not ready.

A partner who resists strategy questions is usually telling you the relationship is thinner than you thought. That is useful information. Drop back a stage and rebuild rather than pushing through.

Making the Sequence Show Up in Your Week

The sequence shows up in how you spend time. Partner account managers who default to selling block their calendars with renewal conversations and pipeline reviews. Partner account managers who default to the right sequence block time for relationship touchpoints that have no agenda, strategy sessions that are not tied to a renewal, and only then the sales conversations.

Try one experiment this month: take your three most important partner accounts and ask yourself which stage each of them is in. For the accounts that are stuck in selling mode, pull back. Schedule a conversation that is not about the pipeline. Use it to listen. You will hear things that change what you bring to the next strategy session.

Cynomi’s GTM Academy Sales Kit was built to help you structure exactly this kind of sequence across your partner conversations, with frameworks for relationship building, strategy planning, and disciplined closes. You can access it here.

There is a moment in every sales cycle when the conversation gets awkward. Maybe the prospect’s eyes glaze over when you ask about incident response. Maybe the client shifts in their chair when you bring up budget. Maybe the partner sidesteps the question about renewal. Most sellers feel the tension and retreat. The MSPs who consistently win do the opposite. They lean in.

That habit is what Heather, one of Cynomi’s partner account managers, calls “getting comfortable being uncomfortable.” It is a phrase her most treasured sales mentor drilled into her early in her career, and it has become the through line of how she coaches the MSPs in her book. If you are not uncomfortable at some point during the sales process, you did not hit all the points you needed to. You probably left the hardest, most important questions on the table. And those are almost always the questions that move a deal forward.

This post is for MSP owners and sellers who sense there is more signal in their sales conversations than they are collecting. The skill you need has less to do with a better script and more to do with the willingness to sit inside a hard moment long enough for something useful to happen.

Why Comfort Is a Leading Indicator of a Stalled Deal

A comfortable sales call feels good in the moment. The partner agrees with you. The prospect nods. Nobody pushes back. You leave the meeting thinking it went well. And then nothing happens.

Comfort is often a sign that neither side put anything real on the table. You asked safe questions, so you got safe answers. You did not ask what happens if ransomware hits next week. You did not ask whose job is on the line if the company cannot recover. You did not ask whether the CEO would sign off on a cybersecurity investment this quarter. So the deal drifts, and you are left guessing why.

Heather’s test is simple. If you walk out of a meeting feeling easy about it, replay the conversation and ask yourself which question you decided not to ask. There is almost always one. That unasked question is where the deal is hiding.

Earn the Right Before You Ask

Discomfort is a tool, not an opening gambit. You cannot walk into a first meeting and start firing off hard questions about an owner’s risk tolerance and expect a useful answer. You have to earn the right to ask them, and that happens in a specific sequence.

The first move is to make the prospect believe you are there to help them, not to sell them. Used-car salespeople have their reputation for a reason. Buyers walk into the conversation braced for a pitch, and they spend the first ten minutes looking for evidence you are different. Give them that evidence. Ask about their business before you talk about yours. Acknowledge what they are already doing well. Be transparent about what you do not know. When the prospect feels you are on their side of the table, the hard questions stop feeling like attacks and start feeling like the work you are doing together.

The second move is to set expectations. Tell the prospect, out loud, that you are going to ask questions that might feel uncomfortable, and explain why. “In order for me to help you, I need to ask a few things that are not the easiest to answer.” That sentence does three things. It signals your competence, it gives the prospect permission to tell you hard truths, and it makes the next question feel collaborative rather than adversarial.

The Questions That Move Deals

Once you have earned the right, the questions themselves should be outcome-oriented. They should force the prospect to picture the consequence of inaction, not recite features they already have. Heather uses a short list with the MSPs she works with, and it travels well.

Start with the incident scenario. “If you get hit tomorrow with ransomware, a data leak, website defacement, or another major attack, who is going to handle it? How long until you are back up and running? Can you survive it? And for how long?” These questions do not come from fear. They come from power. You are showing the prospect what a competent advisor sounds like, and most of them have never been asked.

Move next to accountability. “Who is going to be held responsible if this happens? Whose job is on the line?” The person sitting across from you is almost always the person on that hook, and they rarely say it out loud until somebody asks.

Then move to budget. Money is one of the three things most people were taught never to discuss at the dinner table, so most sellers tiptoe around it. Do not tiptoe. Ask what the cybersecurity budget looks like today, ask whether it is realistic given the risk, and if the answer is no, ask who inside the organization can authorize more. If the contact cannot, your next question is how the two of you build a case they can take upstairs together. You have just turned a budget objection into a collaboration.

Discomfort Is a Service

Pressing on a hard question feels like confrontation, but for the client it is a service. You are making them think about something they have been avoiding, and you are doing it before the ransomware does it for them. That reframe is what makes the habit sustainable. You stop bracing for the hard question and start looking for it, because you know the conversation does not help anyone until it gets there.

A few signs you are doing it right: the prospect pauses before answering. They ask to get somebody else on the next call. They tell you something they have not told the last three MSPs who pitched them. Those are the moments the deal moves.

Where to Practice

The habit builds with reps. Pick a recurring client meeting this month and identify the one question you have been avoiding. Write it down. Ask it. See what happens. Then do it again next month with a different question in a different conversation. In a quarter, your team will have built a vocabulary of harder questions, and your pipeline will have fewer deals drifting without a reason.

Cynomi’s GTM Academy Sales Kit includes discovery frameworks, objection scripts, and client-conversation guides built specifically for the cybersecurity advisory motion. If you want to shorten the learning curve on harder conversations, start there.