Selling Co-Managed IT: Start With the Internal Team

Explain Your Role Before Asking for the Problem

Give the internal IT manager enough context to judge why you're there. Say which work your MSP is equipped to handle and what you need to learn before offering it. Avoid a tour of your entire service catalog.

Ryan Robinett recommends explaining the MSP's relevant background and the problems it addresses before asking a prospect to describe their situation. That's his preferred conversation sequence, not proof that every buyer needs the same introduction. Here it can keep discovery from sounding like an interrogation by a company the manager hasn't yet placed.

A proposed introduction is: 'We provide the specialist escalation work our service team can staff under a defined agreement. I'd like to understand where that would be useful alongside your team.' Use the service you actually deliver in that sentence. Don't borrow the escalation promise if your offer is different.

Then ask for the work the manager wants help with. They may describe missing expertise, a coverage problem, or no current need at all. Keep the answer in the opportunity record instead of turning every response into confirmation that your existing package fits.

Ask What They Want to Keep

Respect becomes observable when you ask where your role should stop. Find out which technical decisions the internal team retains and who authorizes the work you might perform. Ask how they want problems raised when your recommendation conflicts with their current plan.

The wording can be direct: 'Which changes would you expect us to bring to you before acting, and who can approve them when you're unavailable?' Follow with a question about the work itself: 'What information would you need from us to trust that handoff?' These are questions for scoping, not a demand for access during a sales call.

If the manager is cautious about your involvement, investigate the condition behind the caution. They might need clarity about authority or the service your team is proposing. Don't put defensive IT manager in the CRM when the record could instead say approval route unresolved.

Ask the business sponsor to discuss the arrangement with the IT manager present. If the sponsor wants to replace the internal role while you're promising to preserve it, the offer needs correcting. Marketing can't reconcile contradictory instructions by using a warmer adjective.

Replace Broad Reassurance With a Concrete Next Step

Use a before-and-after edit on your own conversation notes. Replace the vague promise with the decision the buyer needs to make. The examples below are proposed wording, not accounts of actual prospect conversations.

Cut the broad version from the proposal too. Otherwise the salesperson and the contract will appear to offer different arrangements. Keep unresolved conditions visible rather than allowing an encouraging meeting to turn them into assumed agreements.

Bring Delivery Into the Decision at the Right Time

Involve the relevant technical lead when the proposed work needs their judgement. Give them the buyer's question and explain their role in the discussion. The purpose is to test whether your MSP can carry the responsibility, not to make the internal manager defend their whole environment.

Brendan Rose suggests involving an engineer early in selected larger proposals while distinguishing that conversation from the detailed discovery needed for a final scope and price. He also says not every deal warrants the engineer's time. That qualification matters: use technical involvement where it can resolve a specific delivery question.

Have delivery check what information it would need to accept work from internal IT. Let the manager explain the records their team already maintains. Resolve how the teams would use that information before proposing duplicate administration as the cost of partnership.

Then put the agreed responsibility and its exclusions beside the flat monthly fee, as the model recommends. Keep detailed cost calculations in the pricing work. This conversation should establish what the buyer is being asked to authorize, not use a reduced fully managed price as a substitute for an offer.

Ask How the Organization Makes the Decision

Ask who approves a recurring service and how it fits the organization's budget process. Paul Green recommends understanding when a co-managed prospect plans and approves budgets so a partnership discussion reaches the right point in that process. That's his planning advice, rather than a universal buying timetable.

Record the next decision and the people needed to make it. If funding isn't available, distinguish a future planning conversation from an active proposal. Don't manufacture a signing deadline to make the CRM look closer to a win.

Keep the IT manager involved in the handoff to your own delivery team. Paul Green describes having to explain his business again during a HubSpot migration because information from the sales process hadn't reached onboarding. That's his customer account; use it as a reason to check that your promised working relationship survives your own handoff.

Measure Agreement With the Work, Not Warmth in the Meeting

Count conversations that reach an internal-IT-approved scope review, with a named business approval route. Record that stage and its evidence in the CRM. Keep rejected or deferred conversations with their stated reasons so you can tell whether the offer, the timing, or your targeting needs changing.

Before testing the message, set the minimum count of those scope reviews needed to justify the presales time you can afford. Derive it from your available capacity and growth plan; the model doesn't supply a conversion threshold. A count below that recorded minimum would make me revise the message or the audience, even if total meetings increased.

Check delivery acceptance alongside that count. More scope reviews are little use if your service lead repeatedly rejects the responsibilities being discussed. That pattern calls for examining the offer and your capability, not congratulating the campaign on engagement.

Take the next conversation into a short written recap. Give the IT manager the responsibility they want help with, the decisions they retain, and the next unresolved question. Ask them to correct it before your team builds the proposal around it.