If you're deciding how to sell cybersecurity services to an existing MSP client, begin with the service they already pay for. Confirm the included baseline, identify a specific unmet requirement, and explain the additional work you propose to deliver. Give the client the recurring price, implementation cost, responsibilities, and limits together.
I'd cut the breach headline from the opening slide. A frightening event elsewhere doesn't establish this client's gap, your service's value, or the price it needs. Start with a requirement both sides can inspect.
Show the Starting Position Before the Upgrade
The MSP Outpost model includes endpoint protection, MFA, awareness training, and email protection in every plan. Advanced tools can be paid add-ons. Use that distinction to separate an unfinished baseline commitment from a genuinely additional service.
Before the meeting, have the technical owner check what the agreement includes and what is actually delivered. If the records disagree, assign the correction. Don't describe completion of already-promised work as a new purchase the client must make.
Say a client has the model's 20 seats at $225 each per month. That is $4,500 of monthly managed-service revenue, with the baseline included under the model's approach. The existing fee is the starting position; it doesn't establish what an additional service should cost.
Show the client a concise current-service summary. Name what is included and who operates it. Leave detailed product inventories available for technical questions rather than making the client infer responsibilities from a page of vendor logos.
Identify the Decision the Client Actually Faces
Ask what the business needs that the current agreement doesn't provide. It could be a changed operating requirement, an identified gap in responsibilities, or work the client has asked you to take on. Record the requirement in the client's words, then have the technical owner verify what it means for delivery.
Paul Green, in practitioner sales-planning advice, suggests mapping what clients buy and don't buy as prompts for discussion. He distinguishes that exercise from understanding business goals and warns against treating the client only as someone to sell to. A blank box in a service matrix is a conversation prompt, not proof of a need.
For the illustrative client, suppose the discussion identifies a requirement for additional monitoring coverage outside the present scope. Before quoting it, establish the systems involved, the relevant coverage window, the receiving contact, and the actions someone must perform. Don't imply that buying a license settles those responsibilities.
If the client's requirement is still vague, clarify it before proposing a package. An account manager can own the conversation while a qualified technical colleague checks the service boundary. Neither needs to promise a quantified reduction in risk that the available evidence cannot support.
Replace the Vague Pitch With a Delivery Explanation
Here's what I'd cut: generic protection claims, unexplained security scores, and a premium package whose main distinction is the length of its tool list. Replace each with a clear change in the service and how the client can verify it.
| Before: Vague Sales Language | After: A Decision the Client Can Review |
|---|---|
| Upgrade for better protection | Name the unmet requirement and the additional service proposed |
| More tools in the premium plan | Explain who will operate them and what work is included |
| Round-the-clock coverage | Specify the actual coverage window, receiving contact, and response responsibilities |
| Lower cyber risk | Describe the intended improvement, assumptions, and what remains outside scope |
| A small monthly uplift | Show the fee, billing unit, implementation work, and ongoing commitment |
Treat these as presentation examples to adapt, not claims about a particular vendor's capabilities. Have the service lead check every coverage and response statement against the service you can actually deliver. Keep the contract and proposal language consistent.
Erick Simpson's sales-training advice recommends preparing engineers who join salesperson-led conversations to answer directly and discuss client outcomes without burying the meeting in specifications. I'd assign the commercial lead and technical lead their questions before the call. That keeps a technical answer from quietly becoming an uncosted promise.
Price the Additional Work Without Charging Twice
Build the delivery cost before setting the add-on fee. Include the supplier charge, implementation effort, ongoing administration, review, escalation, and any extra coverage required. Separate one-time work from recurring delivery so the client can see what starts and what continues.
Remove work already funded by the base agreement from the additional-cost calculation, while checking whether the proposed service expands it. For example, an existing reporting task may remain unchanged or may require a different review. Record the difference rather than assuming the whole activity is new.
The model's managed-service target is 50% gross margin after burdened delivery labor and tools. For an add-on you operate as a managed service, divide its recurring delivery cost by one minus the target margin.
A license resold on its own is a different line. The model uses about 30% product margin; don't apply the managed-service target to a resale while ignoring the associated delivery work. If the proposal combines licensing and an operated service, make the components and their costs visible.
There is no model price for the illustrative monitoring add-on. Obtain current supplier terms and calculate the work needed for this client before quoting. A price copied from an unrelated package would make the example tidier and the decision worse.
Present a Complete Commercial Choice
Put the unmet requirement, proposed service, delivery owner, price, and exclusions together. State the implementation work and dependencies, the billing unit, and how changes in that unit affect the invoice. Describe what the client must provide before the service can begin.
Keep the base monthly fee intact. The model rejects discounting monthly recurring revenue to win business and places concessions on a bonus item instead. If you propose a concession, cost it and identify the item so the recurring economics remain clear.
When the client declines, record the requirement discussed, the proposal, and the decision without presenting the record as a liability waiver. Agree what happens next and when the decision needs revisiting. A refusal to buy doesn't settle whether your existing agreement still fits the work you are being asked to do.
Measure Delivery After the Sale
Record the commercial result in the account record: proposed scope, accepted or declined, agreed fee, and reason given. Keep delivery checks with the service owner: implementation completed, responsibilities accepted, required reports reviewed, and exceptions still open.
Compare actual recurring effort and supplier costs with the estimate. If the service needs more work than priced, investigate the cause before expanding the same offer to more clients. Sales acceptance is a result of the conversation; it doesn't establish margin or prove a security outcome.
Start the next account conversation with a verified baseline summary and a specific requirement. Bring a service your team can explain, deliver, and cost. The client should leave knowing what changes, what it costs, and which decision is theirs.
mspoutpost.com/articles/how-to-sell-cybersecurity-services-without-a-scare-pitch
Written by Owen Gallagher
MSP Outpost publishes information, not legal, financial, insurance, tax or compliance advice, and reading it creates no professional relationship. For decisions about your business, talk to a qualified professional.