Build an MSP Sales Playbook Before Hiring Your First Rep

Write the Client You Can Serve

Your first document should describe the client the rep is allowed to qualify. Use your actual supported geography, environment requirements, service needs, and commercial limits. Add the conditions that require delivery review before a promise is made.

Use current accounts to make those criteria concrete, while checking margin and fit rather than copying the largest invoice. A company that buys a lot of hardware may need a different sales conversation from one seeking a managed agreement. State which kind of business the role is meant to win.

Give the seller words to establish fit: What is prompting the change, which people and systems need support, and what do you expect the new IT team to own? Record the answers in the opportunity. Don't ask the rep to infer a service requirement from the prospect's industry alone.

Also write the response when the prospect falls outside your scope. I'd use: That requirement needs a delivery review before we can offer a service or date. I'll confirm whether we can support it and bring you a clear answer. The document should say who owns that answer.

Describe the Offer and Its Boundaries

The second document is the service offer the seller can explain without improvising. Write what the monthly fee includes, how it is calculated, what remains separate, and the assumptions you need to verify before quoting. Have delivery approve that account of the work.

Keep baseline security in the managed plan. The model includes endpoint protection, MFA, awareness training, and email protection, with advanced tools treated as add-ons. A seller should know which promise belongs in the plan and which requires a separate scope.

Include the objection response as well as the service list. For a prospect asking for the full service at a lower recurring rate, I'd write: Let's compare the responsibilities you need covered. I can have a different scope costed, but I won't promise the full service at a lower monthly rate.

The model rejects recurring discounts to win a client. Its usual concession is quoted onboarding waived for a signed agreement. Put the approval and cost of that concession in the offer document, so the seller doesn't confuse a waived fee with free delivery capacity.

Prepare a Proposal the Team Can Approve

The third document is a proposal template with the required scope, fee, quantities, assumptions, exclusions, and client responsibilities. Use fields whose answers change the commercial decision. A polished page with an unknown environment behind it isn't a finished quote.

Write down who approves pricing and who approves delivery. Establish what information triggers an engineer's involvement and what remains unknown until discovery is complete. Don't make a technician responsible for approving a budget they don't control, or sales responsible for confirming work nobody has estimated.

Show the seller how to present the proposal: These are the responsibilities we would take on, this is the recurring fee, and these items are separately quoted. Which part needs more detail before you can decide? Use the prospect's actual proposal rather than reading a generic pitch.

Keep the agreed annual price step visible. The model uses a fixed 5% increase written into the agreement with advance notice. The proposal and agreement should describe the same commercial arrangement before the seller asks for a signature.

Record How Opportunities Move

The fourth document defines the sales stages and the evidence needed to move between them. Keep it close to the opportunity record. A stage should mean the same thing when the owner and the new rep read it.

Name the buyer information needed for discovery, the approval needed before a final proposal, and the action that establishes a decision. Sending a proposal is seller activity. It doesn't establish that the prospect has reviewed the scope, involved the other decision-makers, or agreed a decision date.

Give every open opportunity a sales owner, the next action, and the basis for its expected decision date. If the buyer hasn't agreed a date, show that as unknown. Use completed opportunities to learn timing rather than assigning a generic deadline to every stage.

Brendan Rose recommends mapping the intended sales process before hiring and expecting that hire to create growth. His practitioner advice cautions that prior vendor or IT sales experience doesn't replace the owner's decision about what the job should achieve. I'd use the stage document to make that decision inspectable.

Specify the Handoff Delivery Will Accept

The fifth document defines the information and acceptance needed to turn a win into service. Ask the receiving team what they need, then have sales collect it during the deal. Don't leave delivery to reconstruct the agreement from a final invoice and the seller's memory.

• The signed scope, recurring fee, quantities, and separately priced work, including any approved concession.
• The client contacts, decision-makers, and responsibilities agreed during the sale.
• The environment information gathered, known gaps, and assumptions still to confirm.
• The proposed start, dependencies, and delivery approval supporting the date.
• The account owner, onboarding owner, and place where the ongoing team can read the agreed promises.

The model keeps new-business hunting separate from account management. Its TAM and vCIO responsibilities sit in delivery labor, reporting to the owner. The handoff should identify who receives those responsibilities instead of leaving the rep to become the permanent account manager by default.

Have delivery accept the handoff and return missing information to a named owner. A signature is a sales milestone; it doesn't confirm that access, scheduling, and service readiness are settled. Make the first client update reflect the actual agreed transition.

Test the Documents Before Setting the Ramp

Run a current opportunity through the documents with the people who will use them. Ask the seller to explain the offer, prepare the proposal, record the next buyer action, and hand over the promised work. Correct the point where somebody still has to guess.

Ray J. Green cautions against expecting a new seller to close within a period no longer than the stated sales cycle when they still need training, offer familiarity, and a pipeline. His coaching view separates those stages instead of assuming qualified opportunities exist on the first day. Build your expectations from the preparation and opportunities you actually have.

The model's stable sales and marketing budget is 6% of revenue, including the rep rather than adding their pay again. Confirm which programs and lead sources the hire will receive within your funded plan. Documents don't generate opportunities by themselves.

I'd give each document an owner and revise it when an actual deal reveals a gap. Keep the first version short enough to use on a call. Hire against the defined responsibilities, and show the candidate both the process they will run and the work they are expected to improve.