Most case studies do not fail because the work was weak. They fail because the story is weak.

They read like delivery summaries instead of buying arguments. They talk about the stack, the toolset, the onboarding sequence, the monitoring platform, the documentation process, the ticket flow, the security layer, the vendor relationships, and the implementation timeline. All of that may be true. Some of it may even be impressive. But it is not usually what wins the next buyer.

What Your Prospects Actually Want to Hear

Your prospect is not shopping for features in isolation. They are shopping for a better business reality.

They want fewer disruptions, faster response, lower risk, better compliance posture, stronger end-user experience, more predictable IT spend, and greater confidence that their business will keep running. In other words, they want outcomes.

The strongest business cases begin by clarifying the need, the value, stakeholder concerns, and the reason the change matters before they explain the mechanics of the solution. A good case study should do the same.

This is the first mindset shift service providers need to make. A case study is not proof that you delivered services. It is proof that a client moved from one business condition to a better one.

From downtime to stability. From reactive chaos to proactive control. From inconsistent support to a mature service desk. From fragmented security tools to a more defensible risk posture. From slow onboarding to a repeatable employee experience. Your service features matter, but only because they created those outcomes.

Why Outcomes Beat Features Every Time

That distinction is more than a writing preference. It is a selling principle.

Strong sales messages often win because they lead with a big promise, then support that promise with proof. A big promise without proof feels exaggerated. Proof without a compelling promise feels forgettable. The strongest messages combine both. That is exactly how a case study should work. Lead with the result that matters to the buyer. Then prove it.

Research backs this up. According to Stanford University research, people are 22 times more likely to remember facts when they are wrapped in a story compared to bare data. And studies on brand storytelling show that story-driven content can boost conversions by up to 30 percent.

This is where many firms default to the wrong structure. They start with “what we installed” or “how we onboarded,” and only later mention the result. But buyers do not naturally think in that order. They think in terms of business pain, business risk, and business value.

If your case study opens with “we deployed our stack, standardized the environment, and implemented layered monitoring,” you may be accurate, but you are still asking the prospect to do too much interpretive work. They have to figure out why any of that matters.

A stronger opening sounds more like this: “Within six months, the client reduced recurring support disruption, improved response consistency, and gave leadership clearer visibility into service performance.” Once the reader cares about that outcome, they are ready to hear how it was achieved.

The Difference Between Activities and Outcomes

There is a second reason to package outcomes, not features. Specific outcomes make stories clearer.

Hiring and performance experts draw a sharp distinction between activities and outcomes. Activities describe what someone does. Outcomes describe what must get done. That distinction is powerful because outcomes are objective, observable, and easier to evaluate, while activities can be busy but commercially vague.

Case studies often live on the activity side of the line. They say the team performed assessments, deployed tools, trained users, documented assets, held reviews, and aligned systems. But those are activities. They are not the commercial proof. The proof is what changed because those activities happened.

For service companies, this means every case study should answer four practical questions:

What was broken or risky before? What measurable or clearly observable change happened after? Why did that change matter to the client’s business? And what specific decisions or capabilities produced that change?

If those four questions are answered well, the case study becomes far more persuasive.

Features Explain the Vehicle. Outcomes Explain the Destination.

A useful way to think about it is this: features explain the vehicle, but outcomes explain the destination.

Buyers do not board a plane because they admire the seat materials. They board because they want to arrive somewhere better. In managed services, your stack, processes, and service model are the vehicle. The client’s improved state is the destination. If your case study only describes the vehicle, it leaves the reader emotionally and commercially unmoved.

Building Trust Through Cause and Effect

There is also a trust issue involved. Buyers are skeptical of polished marketing language, especially in IT services, where many firms claim to be proactive, strategic, responsive, secure, and client-centric.

Results are what convert cynics. Trust grows when people see not only what results were achieved, but how they were achieved. That is a critical point. A case study should not just say, “the client improved.” It should explain enough of the causal chain that the result feels believable.

What changed in the environment? What changed in process? What changed in accountability? What changed in visibility or discipline? When the cause-and-effect logic is visible, the story gains credibility.

This thinking aligns with Balanced Scorecard methodology. Outcome measures are lagging indicators. They show whether the strategy worked. But outcome measures alone can create ambiguity if the reader cannot see what drove them. The best scorecards connect outcomes to performance drivers through cause-and-effect relationships.

That is exactly how a strong case study should be built. Do not just show the result. Show the drivers behind the result.

For a service provider, those drivers might be standardized onboarding, tighter documentation, scheduled review rhythms, clearer escalation rules, stronger endpoint discipline, better patch hygiene, or more consistent client communication. The outcome is the headline. The drivers are the proof structure.

Why Outcome-Led Stories Work for Multiple Stakeholders

This matters even more because the buying decision is usually not made by one person. Owners, operations leaders, finance leaders, internal IT contacts, and office managers may all view the same proposal through different lenses.

Research from Gartner shows that B2B buying committees now typically involve around 10 stakeholders across multiple functions such as IT, operations, finance, and end users. And according to 6sense research, 81 percent of buyers already have a preferred vendor by the time they make first contact with sales.

Stakeholder perspectives and buy-in matter for exactly this reason. A feature-heavy case study tends to appeal mostly to technical readers. An outcome-led case study can speak to multiple stakeholders at once.

The owner sees reduced business risk. The finance leader sees more predictability. The operations leader sees smoother execution. The internal IT contact sees less firefighting. That makes the story easier for your champion to circulate internally.

The Retellability Test

And that is the hidden test of a great case study: can someone else retell it?

Your best case studies should function as internal sales tools inside the buyer’s organization. They should be easy for a prospect to forward with a note that says, “This is what I’m talking about.”

That only happens when the story is tight, outcome-driven, and simple enough to repeat.

One client. One problem. One meaningful transformation. One or two memorable proof points.

For a service provider, that might mean leading with something like this: a multi-location professional services firm was drowning in recurring service interruptions and inconsistent support experiences, and after standardization, process redesign, and regular service accountability, the company gained a more stable environment, clearer executive visibility, and fewer avoidable support escalations.

That tells a business story. It does not require the reader to already care about your stack.

Avoid the Feature Dump

Notice also what it avoids. It avoids feature dumping.

A long feature list often weakens a case study because it makes the message feel generic. If every provider offers monitoring, help desk, backup oversight, Microsoft 365 support, security tooling, and virtual CIO conversations, then listing features does not separate you.

What separates you is the business effect of how you deliver them. That is where your real differentiation lives.

Write Case Studies Like You Run Client Reviews

The practical implication is simple. Service providers should write case studies the same way they should run client reviews: start with outcomes, explain drivers, make the business meaning explicit, and keep the narrative clear enough for nontechnical stakeholders to understand.

When you do that, the case study stops being a brochure asset and starts becoming evidence.

And evidence sells.

Four Frameworks for Stronger Case Studies

The Outcome-First Case Study. Open with the business result, not the service package. This combines business case logic with direct-response “big promise plus proof” thinking.

The Activity-to-Outcome Shift. Replace descriptions of what your team did with evidence of what changed for the client. This comes from scorecard thinking that distinguishes activities from outcomes.

The Driver-and-Proof Model. Present the headline result, then show the operational drivers that produced it so the story feels credible and transferable. This is adapted from Balanced Scorecard cause-and-effect logic.

The Retellability Test. A case study is strong only if a buyer can forward it internally and use it to win support from multiple stakeholders. This is drawn from stakeholder-perspective and buy-in thinking.

Most case studies fail for a simple reason: they read like product tours instead of buying arguments.

They describe the platform, the process, the dashboard, the implementation steps, the methodology, the team, the timeline, and the feature list in loving detail. Then they wonder why prospects nod politely and do nothing.

The problem is not that features are irrelevant. The problem is that features are rarely what a buyer is actually trying to buy.

Buyers buy movement. They buy risk reduction. They buy speed. They buy confidence. They buy a future state that feels clearer, safer, more profitable, more controllable, or more prestigious than the present one.

That is why strong business cases begin by clarifying the need and the value, and by understanding stakeholder perspectives before jumping to the proposed solution. A case study should do the same. It should not begin with “here is what we did.” It should begin with “here is what changed.”

The Core Unit Is the Before-and-After Delta

This is the first shift worth making. Stop thinking of a case study as proof that your company delivered work. Start thinking of it as proof that a customer crossed a meaningful gap.

That gap might be from slow growth to faster growth, from chaos to control, from fragmented systems to better decisions, from waste to efficiency, or from uncertainty to predictable results.

In other words, the core unit of a persuasive case study is not the feature. It is the before-and-after delta.

That distinction matters because people evaluate ideas through outcomes long before they care about mechanics. Marketers often default to studying the product and translating features into benefits, but the strongest promotional ideas are usually built around one clear promise, one central outcome, one “big idea” that gives the message force and memorability.

A case study that tries to say ten things at once usually says nothing convincingly. A case study that organizes itself around one vivid commercial result has a far better chance of being remembered and retold.

Features Matter, But Only in Service of Results

“Outcomes, not features” should not be interpreted as “never mention features.” Features still matter, but only after they are put in service of a result.

A dashboard is not the point. Faster decisions are the point. Weekly reporting is not the point. Higher accountability is the point. Training is not the point. Adoption is the point. Automation is not the point. Reduced manual waste is the point.

The mechanism matters only after the reader understands why it mattered.

Build the Story in the Right Order

A useful way to think about this is to borrow from scorecard thinking. Effective hiring scorecards begin with mission, then define three to eight specific outcomes, and only then identify the competencies required to achieve them.

That sequence is quietly powerful. It suggests a case study should be built in the same order.

First, state the mission or business challenge. Second, identify the measurable or observable outcomes that mattered. Third, explain the capabilities, decisions, and behaviors that produced those outcomes.

Most companies reverse this order. They start with competencies, tools, or features, and only later gesture vaguely toward impact. But buyers want the logic to run the other way. They want to know what improved, why that improvement mattered, and only then how it happened.

Show the Causal Architecture of Success

There is a deeper reason this works. People are often blind to the real forces shaping behavior and results.

Research on behavior change shows that individuals routinely fall into a “willpower trap,” overcrediting motivation and underestimating the mix of personal, social, and structural influences that drive outcomes. When multiple sources of influence are aligned, behavior changes far more reliably than when people rely on one heroic effort alone.

That insight translates beautifully into case study writing.

If you only say, “the client used our software and got results,” your story feels shallow and fragile. If you show that the result came from aligned decisions, better visibility, stronger habits, clearer priorities, improved incentives, and a supportive operating structure, the case becomes more believable.

The buyer is not just seeing what you sell. They are seeing the causal architecture of success.

Respect the Reader’s Skepticism

This is where weak case studies often lose trust. They present a miracle ending without enough logic in the middle.

Stronger ones do the opposite. They respect the reader’s skepticism. They show the actual journey from problem to progress. They admit friction, constraints, and trade-offs.

One persuasive principle from research on influence is that credibility rises when a communicator acknowledges a drawback early and then follows it with the strongest argument, because the admission colors the rest of the message with trustworthiness.

In practical terms, a case study becomes more persuasive when it includes a sentence like this: “Implementation took longer than expected in the first month because three legacy workflows had to be untangled, but once that was done, the client cut turnaround time by 42 percent in the following quarter.”

Buyers believe stories that contain resistance. They distrust stories that sound frictionless.

Outcomes Are Lagging Measures of Systems

Another useful principle comes from research on habits and systems. Outcomes are lagging measures of what you repeat. Your weight is a lagging measure of eating habits. Your knowledge is a lagging measure of learning habits. Your results reflect your systems.

For case studies, that means the most credible stories do not merely celebrate the end result. They reveal the repeatable system that made the result possible.

Buyers are not only asking, “Did this work there?” They are asking, “Could this work here, in a way that can last?”

A persuasive case study should therefore show not only a spike in performance, but the operating rhythm behind it. What changed in reporting cadence? What changed in team behavior? What changed in prioritization? What changed in measurement?

The result is attractive, but the repeatable system is what makes the result portable.

Write for Multiple Stakeholders

The best case studies are written for multiple stakeholders, not just one reader.

In a real buying committee, the CFO may care about cost and risk. The operator may care about workflow simplicity. The executive sponsor may care about strategic alignment. The frontline team may care about ease and adoption.

A feature-centric case study usually speaks only to the technical evaluator. An outcome-centric one can speak to all four.

It can show revenue impact for the executive, efficiency gain for operations, payback logic for finance, and usability for the team. That makes the story not only more persuasive but more usable inside the prospect organization, where your champion has to retell it to others.

Make It Easy to Retell

That retellability matters more than most marketers realize.

In organizations, influence depends less on formal authority than on personal power, trust, and the ability to help others create positive outcomes through collaboration and buy-in.

A great case study should therefore function as a portable internal selling tool. Your prospect should be able to forward it to a colleague and say, “This is what I mean.”

That will only happen if the story is simple enough to repeat. Again, the one-big-idea principle helps. One client. One problem. One meaningful transformation. One memorable proof point.

Each Case Study Should Prove One Thing Well

There is also a strategic discipline required here. If you try to make every case study prove everything, you dilute them all.

Each case study should sit in a specific sweet spot. It should be designed to prove one category of value for one kind of buyer.

One might prove speed to value. Another might prove cost reduction. Another might prove strategic clarity. Another might prove talent performance or customer retention.

The more specific the proof, the more useful the asset.

What a Better Case Study Sounds Like

So what should a better case study actually sound like?

It should sound less like a brochure and more like a business case wrapped in a story. It should open with the buyer’s tension, not your company’s bio. It should define success in concrete language. It should show the constraints honestly. It should explain the small number of decisions or interventions that mattered most. It should connect those interventions to business outcomes. And it should end by helping the reader see themselves in the story.

A Simple Narrative Sequence

A simple narrative sequence works well.

Start with the stakes: what was at risk if nothing changed? Then define the old reality in operational terms. Next, name the decision trigger: why did the client act now?

After that, show the intervention in plain English, focusing on the few changes that really mattered. Then show the outcomes, prioritizing metrics when available and strong qualitative shifts when numbers are confidential.

Finally, interpret the result. Do not leave the reader alone with raw numbers. Tell them what the numbers mean.

A 17 percent improvement in conversion is nice. A 17 percent improvement that shortened payback time and gave sales leadership more forecast confidence is much stronger.

Show How the Organization Changed Its Way of Working

The final principle is cultural. Strong outcomes are easier to sustain when leaders model the behavior they want and connect beliefs and behavior directly to measurable results.

This means your best case studies should not just celebrate tools or tactics. They should reveal how the client organization changed its way of working.

Did leaders reinforce accountability? Did teams build a new review rhythm? Did the company define fewer, more meaningful priorities? Did the environment make good decisions easier?

These details elevate a case study from “vendor success story” to “organizational proof.” That is what sophisticated buyers want: evidence that the result was not accidental.

The Real Job of a Case Study

In the end, case studies sell when they help the reader make a decision, not when they help the writer describe an engagement.

Buyers do not need an archive of your activities. They need a believable map from pain to progress.

When you package outcomes instead of features, you are doing more than improving your marketing. You are showing that you understand how value is actually perceived, justified, shared internally, and adopted in the real world. You are moving from description to persuasion.

And that is the real job of a case study. Not to say, “Look what we built.” But to prove, “Here is what changed, why it mattered, and why the same kind of change could happen for you.”

Seven Principles for Case Studies That Sell

The Outcome Gap Framework. Define the case study around the gap between the client’s old reality and new reality, not around your solution stack.

The One-Proof Principle. Each case study should prove one major promise, one big idea, and one memorable commercial result, rather than many loosely related benefits.

The Causal Credibility Model. Show the specific personal, social, and structural changes that produced the outcome so the result feels believable and repeatable, not magical.

The Lagging-Measure Method. Treat metrics as evidence of a changed system, habit, or operating rhythm, not as isolated trophies.

The Honest Friction Rule. Acknowledge a real constraint, trade-off, or obstacle early to increase trust and make the eventual result more persuasive.

The Multi-Stakeholder Story. Write every case study so an executive, operator, finance lead, and frontline user can each find a reason to care and a sentence to repeat internally.

The Portable Buy-In Test. A case study is finished only when a champion could forward it inside their company and use it to win support from others.

Most sales teams think they have a proposal problem when they actually have a qualification and demonstration problem.

They complain that prospects ask for too many proposals, that engineering gets dragged into too many scoping cycles, that too much time goes into statements of work that never close, and that buyers keep shopping their quotes.

But usually, there’s a deeper issue: a proposal is supposed to come after the prospect is qualified, not serve as the tool for qualification itself.

In a well-designed sales process, stage one is to qualify the prospect or customer. Only if that qualification is complete should the team advance to stage two, the proposal. The proposal is where you lay out objectives, scope, tasks, timing, and costs. It is not supposed to be the thing that tells you whether the buyer was serious in the first place.

That single distinction changes a lot. If your team is producing too many proposals, the fix is not simply to write proposals faster. The fix is to run better demos, better discovery, and better qualification so that fewer prospects ever deserve a formal proposal.

Why “Better Demos, Fewer Proposals” Is Really a Positioning Strategy

This idea sounds like a productivity tactic, but it is really a positioning strategy. The goal is to stop showing tools and start showing business outcomes.

Once that happens, two things improve at once. First, buyers better understand your value. Second, your team stops wasting time on opportunities that should never have reached proposal stage.

A lot of providers still demo the wrong thing. They show dashboards, ticket systems, backup portals, security consoles, and reporting screens. They walk a buyer through features, menus, and acronyms.

Internally, those tools matter. Externally, most executive buyers do not care unless you translate those tools into uptime, risk reduction, budget predictability, scalability, and less executive distraction.

You’ll improve conversion if you use executive language and tie the conversation to uptime, security, predictability, and total cost. Teach slowly, summarize as business outcomes, and move the buyer toward the next step once the “aha” moment appears.

What a Better Demo Actually Looks Like

A demo should not be a technical tour. It should be a structured teaching moment that helps the buyer see the cost, risk, and operational drag of their current state, and why a different operating model creates a better result.

In that sense, the best demo is often not even a software demo at all. It is a business-case demo.

Think of it as the Outcome-First Demo Model with five steps: qualify, diagnose, teach, compress, and then propose.

Step One: Qualify Before You Invest

Before your team spends engineering time or writes a scope, the seller should determine whether the buyer actually fits your target profile and whether there is a real business need.

The right questions at this stage include: Are they in your desired geography, vertical, and size? Do you support the technology they have or want? Why are they seeking the service? How important is quality to them? What happens if it goes wrong? Are they the check-signer? Does a rough budget range fit their expectations?

Those are not administrative questions. They are filters that tell you whether the deal deserves more investment.

That means a better demo starts before the meeting itself. It starts with deciding who gets one.

Step Two: Diagnose the Real Situation

High-performing providers do not just assess the technical environment. They also assess the prospect’s operational maturity and the way they manage IT decisions.

Top performers evaluate how the customer plans, governs, funds, and manages IT because that strongly affects service quality, customer satisfaction, and profitable growth. The assessment is not just about uncovering technical facts. It is about minimizing the risk of “winning” a customer that is not worth winning and differentiating yourself with those who are.

This matters because a buyer asking for a proposal may still be a bad fit. They may be price-only. They may resist standards. They may create rework and squeeze margins after the deal is signed.

A good diagnosis helps surface that before your service team gets trapped in unpaid design work.

Step Three: Teach Instead of Present

This is where most demos should spend their energy. The goal is not to impress the buyer with product knowledge. It is to help them understand what their current operating model is costing them and what a better model would change.

Effective talk tracks focus on standards, downtime math, leadership time, governance, security testing, and whether the client runs by plan and metrics or by tickets and emergencies. The approach should be calm teaching rather than arguing, even with skeptical buyers.

When interest appears, you trial-close to the next logical step: paid assessment, remediation roadmap, or a full managed services proposal with your standards.

This is a much more powerful use of a demo than opening with tools. Tools support the story, but they should not be the story.

Step Four: Compress Complexity Into Outcomes

Compress the complexity of your offer so the buyer focuses on outcomes, not ingredients.

High-performing providers maintain a very detailed internal cost model, but the customer-facing proposal is one or a few lines. The point is to focus the customer on the meal, not the ingredients.

Lower-maturity providers do the opposite: they expose simplistic line-item models, invite menu-picking, and trigger price-shopping. À la carte offers do not scale, cause buyers to choose badly, and leave everyone unhappy. Top performers simplify toward one optimal full-meal offer.

This idea should shape the demo just as much as the proposal. If your demo walks through every tool, every SKU, every module, and every exception, you are training the buyer to think in pieces. That nearly guarantees more proposals, more revisions, and more comparison shopping.

If instead your demo presents a coherent operating outcome with a clear business case, the proposal becomes easier because the buyer already understands the whole.

Step Five: Propose Only After You Have Earned It

The point is not to avoid proposals altogether. It is to reserve them for opportunities that have earned them.

The most expensive mistake is writing proposals for prospects you lose, because proposal effort consumes expensive engineering and management time. A poor sales force uses the proposal to qualify the customer. A good sales force qualifies the customer before writing the proposal.

That principle becomes even stronger when you connect it to paid discovery. Top-performing firms require paid discovery on scoping, gate access to pre-sales through a pre-qualification checklist, and train sales and service on “value not price.” They shift pre-sales accountability toward services and make discounting hard to do casually.

In other words, top-performing firms treat proposal effort as valuable labor, not free bait.

Three Cleaner Paths Forward

Better demos reduce proposal volume because a strong outcome-first demo often creates one of three cleaner paths:

1. The prospect is clearly qualified and ready for a proposal. 
2. The prospect is interested but needs a paid assessment or roadmap before a full proposal makes sense. 
3. The prospect reveals that they are not the right fit at all.

All three outcomes are healthier than writing a custom proposal to find out what should have been discovered earlier.

Why This Improves Your Pricing Power

There is also a financial reason to do this.

The most mature pricing approach starts with business value: if the client stays as they are, they carry a higher risk of missing business goals. Hiring you lowers that risk, and the value of that reduction is far above what you charge.

A tool-first demo makes value-based pricing difficult because it teaches the buyer to compare features. An outcome-first demo supports value-based pricing because it frames the conversation around risk, performance, and business results.

Better Demos Improve Your Entire Funnel

It also improves sales efficiency. Proposal counts, open proposals, proposal values, and close ratios are all measurable sales metrics. That means proposal volume is not automatically a good sign. It can indicate activity, but it can also reveal wasted motion.

If proposal conversion is poor, the issue may be upstream in qualification, needs analysis, or how the sales process is being executed. Better demos improve those upstream stages because they help you diagnose and improve the funnel, not just the output.

The Culture That Makes This Work

There is a cultural piece here too. When sales is rewarded for revenue alone, they are tempted to over-demo, over-scope, and over-discount.

The better way is to align incentives to actual delivered gross margin and company outcomes, not just top-line bookings. Implement paid discovery, standards-first selling, no free change orders, and stronger approval controls around discounting.

The result is a cultural shift: sales sells what the company can deliver at margin, defends scope and price, and both sales and service celebrate the gross margin dollars that actually hit the income statement.

That is exactly the environment where better demos thrive. In a mature organization, the demo is not a performance by an isolated salesperson trying to win affection with features. It is a disciplined commercial event that helps both sides understand fit, business value, and the right next step.

What You Should Actually Demo

So what should you actually demo?

Demo the cost of staying the same. Demo the operational friction in their current model. Demo what standards make possible. Demo what predictability feels like. Demo the difference between running by metrics and running by emergencies. Demo the future business state, not the admin console.

That does not mean never showing tools. It means tools should appear only after the buyer understands why they matter.

A dashboard is useful only once the customer sees it as evidence of control. A security platform matters once the buyer sees it as reduced business risk. A reporting system matters once it is tied to accountability and planning. Otherwise it is just software theater.

The Real Promise of Better Demos

In the end, fewer proposals is not about doing less selling. It is about doing more of the right selling earlier.

Better demos create clearer thinking, sharper qualification, stronger value framing, and cleaner next steps. They make the proposal more meaningful because by the time it appears, the buyer already understands the business case.

When sales teams learn to sell outcomes instead of tools, they stop confusing activity with progress. They stop using proposals to compensate for weak discovery. They stop training buyers to shop features. And they start building a sales process where every major step earns the next one.

That is the real promise behind better demos and fewer proposals. Not just less work, but better work. Not just a shorter sales cycle, but a healthier one. And not just more wins, but better-fit wins that service can actually deliver profitably.

The fastest and cleanest way to improve profit is usually sitting right in front of you: your pricing. Specifically, the prices you actually charge in the market relative to how productively your team delivers services. 

If your pricing doesn’t reflect the true value you create and the real cost of turning your engineers’ time into outcomes for clients, you’ll work harder every quarter for the same mediocre economics or worse.

The transformation from owner who constantly sells and rescues everything to CEO who builds a business that compounds earnings over time begins with pricing that tells the truth about your business and teaches your clients what excellence actually costs.

This guide lays out a practical approach to pricing for IT services businesses. 

How to anchor on the right financial foundations. How to build prices that scale with how productively your team works. How to implement price increases without destroying relationships. And how to protect pricing integrity when you’re selling. 

It’s based on sound financial principles, execution discipline, and behavioral science, all translated into practices you can implement this quarter.

Price What You Actually Sell: Outcomes at Scale, Not Time on a Clock

Hourly billing misleads everyone involved. Clients mentally anchor on time spent rather than value created. Your engineers feel pressure to move fast instead of getting things right. You feel like a price taker because in hourly billing, the clock becomes the product rather than the outcome.

A healthier and more honest framework is straightforward: you sell outcomes at scale, delivered through a standardized technology stack and a professional system. Price the outcomes and the system that reliably produces them.

That means shifting conversations away from “how many hours will this take” toward “what risks disappear, what productivity improves, and what reliability can you expect.” 

When you move to tiered, outcome-based service packages, you create a default structure that naturally guides clients toward the right combination of coverage, response commitments, change management, security measures, and governance that your team can deliver repeatedly and well.

You also earn the right to price separately for things that fall outside the standard model: projects with significant change risk or integration complexity, expedited requests that disrupt your normal workflow, or non-standard tools that require specialized expertise. 

Service packaging isn’t just a marketing wrapper. It’s how you keep price, cost, and value in the same conversation and prevent them from drifting apart.

Here’s a quick test of whether your current pricing actually reflects outcomes: look at your most demanding, high-touch clients. 

Are they paying materially more than low-touch clients with the same number of users, specifically because their behavior and environment demand more from your systems and team? If they’re not, you’re using averages to hide exceptions, and your pricing is absorbing the financial blow while your team absorbs the stress.

Build Your Pricing From the Inside Out: The Labor Productivity View

Every price you publish should pass a simple check: will this service offering, based on our expected delivery patterns, generate rising gross profit per labor dollar as we standardize our approach and learn over time? If the answer is no, your business model won’t scale profitably no matter how many clients you add.

This is where many IT service businesses go wrong. They price a service package at what seems like a reasonable market rate per user or per device, then discover that a heavy support ticket load, excessive rework, or client-specific tools completely consume the margin. They respond by adding roles to cope with the chaos. A dispatcher here to triage better.

A project assistant there to keep things moving. Suddenly the business is extremely busy, everyone is exhausted, and profit remains stubbornly unpredictable.

Reverse that order completely. Start from your required gross profit per labor dollar and your understanding of your delivery capacity. 

Model the expected mix: what percentage of work will be Tier 1 support versus Tier 2 versus engineering projects, expected ticket volumes by category, and the proportion of standardized versus custom work. 

Then set your price so that, even with conservative assumptions, the package clears your financial guardrails and improves your gross profit per labor dollar ratio as your team follows your standard processes.

If a service offering can’t meet that standard, it’s either underpriced or under-standardized. Fix the standardization first by removing unnecessary variation and complexity. If your standards are already solid, raise the price. Period.

This sounds coldly analytical because it needs to be. You’re not pricing a wish or a hope. You’re pricing a system that converts human expertise and time into reliably managed outcomes for clients. Stop expecting the market to magically forgive arithmetic that doesn’t work.

Stop Discounting Out of Habit: It’s Stealing From Your Future

Price discounts feel like helpful grease that keeps deals moving. In reality, they’re a quiet tax on your future delivery capability. Every percentage point you give up during the sales process must be earned back later through heroic efficiency that may or may not be possible, or it gets carried forever as permanent margin loss that gradually weakens your business.

Even worse, discounting often correlates strongly with poor client fit. The prospects who demand significant price concessions early in the relationship tend to be the same ones who demand constant exceptions and special treatment later. 

You don’t need a sophisticated financial model to avoid this trap. 

You need a simple, clear sales approach that focuses on right-fit prospects, with language that crisply explains the value your system creates and the costs and risks it prevents. 

You need salespeople trained to protect price integrity as a core professional skill. 

Consistency beats charisma. Fewer concessions beats fancier presentations.

If you want a practical policy you can implement immediately, make it this: price reductions require a corresponding and documented reduction in scope or risk acceptance in the service agreement. No naked discounts ever. 

If a buyer absolutely insists on a lower price, ensure the change is visible and clear. A lower service tier. Slower response commitments. Fewer included changes or projects. This teaches the market the correct lesson: price is how we express scope and risk allocation, not our mood today or how badly we want this particular logo.

When to Raise Prices and How to Do It Without Destroying Relationships

If your prices haven’t increased meaningfully in the last twelve to eighteen months, you’re almost certainly behind where you need to be. Costs rise steadily. Technical complexity increases. Client expectations expand. Your pricing must track with the actual value you deliver as all of these factors evolve.

The right time to raise prices is as soon as you realize your current service mix cannot fund market-based owner compensation and your pre-tax profit floor on a forward-looking basis without either starving your team or shortchanging your clients. The wrong time is “after this big project finishes” or “after we hire two more technicians.” Endless delays become culture, and culture becomes your prison.

How you implement price increases matters enormously. Simple announcements and one-time webinar explanations will not carry the change effectively. Treat the price increase as a genuine behavior change initiative for both your clients and your own staff.

First, align your internal team using multiple sources of influence working together. Build personal ability by giving your account managers the exact language to explain the change and practical tools to handle common objections. 

Strengthen personal motivation by connecting the price increase clearly to the outcomes and stability clients actually want and value. 

Leverage social proof by quickly sharing early wins and positive reactions from clients who understood and accepted the change. And critically, change the work environment so the new price becomes the default path of least resistance, not the exception. 

Update proposal templates, configure your CRM defaults, and modify billing systems so the new pricing structure is what naturally happens unless someone actively intervenes.

Make structural levers work for you. Tie expedited or rush requests to expedite fees automatically. Require prepaid blocks for ad hoc project work outside normal service agreements. Move approval processes into your systems where scope changes can be tracked and priced in real time. Behavior change sticks when multiple levers all pull in the same direction instead of working against each other.

Second, have direct accountability conversations with the clients who will feel the change most significantly. Anchor these conversations on commitments and economics, not emotion or history. 

Here’s what we originally agreed to provide. 

Here’s how the technology environment and client expectations have changed since then. 

Here’s what it actually takes to deliver reliably under current conditions. 

And here are your options moving forward.

Your goal isn’t to win an argument or force compliance. It’s to make it crystal clear that both parties need sufficient motivation and ability to continue the relationship on a stable, sustainable footing. 

Some clients will step up and pay the new rates because they value what you deliver. 

Some will scale down their service level to match what they can afford. 

A few will leave for cheaper alternatives. 

All three outcomes are healthier for your business than continuing to carry subsidized relationships that drain your team and distort your economics.

Pricing and Cash Flow: Making the Money Actually Arrive

Even a beautifully priced IT services business can feel perpetually cash-poor if the money arrives slowly or unpredictably. Your pricing must be paired with payment terms and collection discipline that prevent you from becoming your clients’ involuntary bank.

Handle three things consistently. First, shorten the path from service delivery to cash in hand. Pre-bill for services where clients will accept it. Tie project invoices to clear acceptance milestones rather than completion of vague phases. 

Automate polite but consistent collection reminders. Make sure your service agreement language removes ambiguity about what “done” means so billing doesn’t stall over subjective interpretations.

Protect the key uses of cash flow: taxes you owe, debt service if you have any, core capital investments needed to maintain and grow the business, and distributions to owners. 

Your operating model must fund all four from normal operations without requiring heroics, miracles, or emergency measures. Pricing that looks good on paper but can’t actually feed these cash needs is a story you cannot afford to tell yourself.

Second, make late payment genuinely expensive for clients. If a client habitually pays late, you are funding their working capital needs with your money. 

Change the relationship structure: require deposits up front, move to automatic payment, or offer a significantly lower-touch service tier that your team can deliver without building resentment. 

Clients who truly value your outcomes will prefer clarity and fair terms over constant negotiation.

Finally, measure the right indicators. How long your billing cycle takes. Accounts receivable aging that stays within policy. Work in progress that predictably converts to cash. These are pricing outcomes just as much as they are finance outcomes. Proof that your price is paired with a system that reliably converts delivered value into money on your expected schedule.

Operational Excellence Is Your Strongest Pricing Argument

Pricing becomes far more defensible when operations become more reliable. That’s not just a pleasant slogan. It’s why clients will pay your rates and renew at your rates instead of shopping around constantly.

Build an execution rhythm that turns promises into routines you can confidently point to.  A regular cadence isn’t management theater for its own sake.

It’s how you sustain the habits that make your pricing feel like a bargain in hindsight when clients reflect on what they received.

There’s also a direct productivity connection. Standardizing your technology stack and change management calendar reduces rework. It raises first-contact resolution at the appropriate support tiers. 

It improves project predictability and budget accuracy. These operational wins flow directly into gross profit per labor dollar, which creates the confidence to charge and hold prices that fund quality delivery without constant firefighting.

When clients consistently see fewer unpleasant surprises and experience faster, cleaner outcomes, price concerns naturally fade. You’ve already proven the value with their actual experience, not just your marketing slides.

The Quarterly Pricing Routine That Maintains Alignment

Pricing isn’t an annual announcement you make and forget. It’s an ongoing management discipline and habit. Establish a simple quarterly routine.

Start by segmenting your client base by meaningful profiles: how well they fit your ideal, their support ticket intensity and patterns, their security and compliance requirements, and their payment behavior. 

For each segment, confirm that the prices you’re actually realizing still clear your owner compensation and profit guardrails, and that gross profit per labor dollar is rising or at minimum holding stable as you standardize your delivery approach.

Where those conditions aren’t met, make a decision: upgrade your standards and the client’s behavior, raise the price, narrow the scope you’re committing to, or exit the relationship. 

Then check for structural friction in your systems. Are your proposal templates, quoting tools, and invoicing defaults all aligned with your current pricing? 

Are your account managers actually practicing the language and positioning? Are expedited or rush requests automatically priced as such rather than being absorbed as favors?

The goal isn’t chasing the absolute highest price for its own sake. It’s keeping your pricing synchronized with both the value your system creates and the cost reality of your delivery as both of those factors evolve. 

You’ll discover that when you run this routine consistently quarter after quarter, the drama and anxiety drain away. Your team stops quietly whispering “I think we way underpriced that client” because your system catches misalignment early while it’s easy to correct. 

Your clients stop being surprised by price conversations because you’ve trained them to expect clarity and options, not last-minute corrections.

When Pricing Means Saying Goodbye

Every healthy IT business eventually outgrows certain clients, service scopes, and deal structures. When raising prices exposes those growing pains, treat the moment as responsible stewardship rather than confrontation or failure.

Explain clearly the new standards and terms that protect service reliability for everyone. Offer the best available fit within those boundaries. And help clients transition professionally if they need to move to a different provider. This isn’t business failure. It’s strategic focus. You fundamentally cannot build a compounding, growing business on a foundation of constant exceptions and special cases.

This approach also directly protects your management team and technical staff. Nothing erodes morale faster than being forced to make promises that the economics cannot possibly support. 

Nothing burns out your best engineers faster than carrying subsidized client relationships where they’re expected to perform miracles with inadequate resources. 

Clear pricing becomes the clean, professional language that lets you say plainly: “Here’s what it actually takes to do this work right.” Use it without apology.

Bringing It All Together

Your pricing is the clearest possible expression of how you fundamentally see your business. Owners who price primarily to be liked end up constantly discounting their own standards and slowly destroying their businesses. 

CEOs who price to be trusted teach the market that excellence has a real cost and delivers a genuine payoff, then consistently deliver on both sides of that equation.

If you adopt the financial guardrails that force truth into your planning, design service packages that honestly reflect outcomes and risk, align your pricing with labor productivity realities, defend price integrity throughout your sales process, implement price increases with serious behavioral rigor, and keep cash flow and execution in rhythm, you’ll experience an unfamiliar sensation: profit that shows up on schedule and becomes easier to repeat over time.

That’s not luck or market conditions or having the right connections. That’s leadership exercising its primary responsibility.

If this guidance sounds uncomfortably direct and specific, that’s because pricing is the precise place where your convictions and values become mathematics. 

Set your pricing with genuine care for sustainability. 

Defend it with clarity and confidence. 

Earn it through reliable systems that deliver what you promise.

The alternative is working harder every year while your business gets weaker. You can’t call that a noble sacrifice. It’s just poor management, through  and through. You and your team deserve better.

You hired aggressive hunters, gave them a revenue quota, and handed them a check for every contract they signed. The mandate was simple: go get the Monthly Recurring Revenue (MRR), and the rest will take care of itself.

If you pay your sales team to chase MRR, they will happily chase MRR. The problem is that not all recurring revenue is created equal. Some deals arrive with healthy margins, low support loads, and customers who stick around for years. Others come with heavy discounts, custom promises that strain your engineering team, and buyers who cancel the moment the honeymoon ends. 

On a spreadsheet, both deals look identical. They are both logged as “$5,000 in new MRR.” In real life, however, one creates sustainable growth while the other is a silent profit leak.

A sales compensation plan that rewards any revenue at any cost will quietly fill your portfolio with the wrong kind of business. 

To fix this, we have to look at the tools you should already have—financial dashboards, Key Performance Indicators (KPIs), and scorecards—and use them to design a compensation strategy that pays for profitable growth, not just subscription logos.

Redefining Success Beyond the Signature

Before you can design a compensation plan that works, you need a simple, shared definition of what you are actually aiming for. Most companies stop at “new sales,” but that is insufficient. Your existing KPI references likely encourage a deeper look. 

Every good metric starts with a key performance question, usually asking to what extent the business is generating bottom-line results and using resources effectively. When we apply this thinking to recurring revenue, we have to look through three distinct lenses: margin health, retention health, and strategic fit.

Margin health asks a fundamental question about the cost of doing business. It looks at the gross margin per dollar of revenue after the direct costs of delivery and support are paid. 

You have to ask if the customer is paying enough, for a clean enough scope of work, to leave room for actual profit. If a salesperson closes a massive deal that requires twice the normal support staff to manage, that deal might actually be costing you money every single month.

Retention health is the likelihood that the customer will renew, expand, and refer others. In a subscription business, the initial sale is just the starting line. 

Churn and contraction are effectively “negative revenue” that erase all the effort your sales team put in. If a customer buys and then leaves six months later, you have lost money on the acquisition costs without ever seeing a return.

Finally, there is the question of strategic fit. 

Does this customer match your ideal profile in terms of size, segment, and complexity? Or are they an outlier that will distort your product roadmap and service model? 

When you view revenue through the “Big Picture” lens of a CFO, profitable MRR is revenue that contributes positively to gross margin, has a high chance of sticking around, and does not create disproportionate complexity in operations. Your compensation plan has a single job: to pay more for that kind of revenue and less, or nothing at all, for everything else.

Unit Economics as the Foundation

A lot of sales plans are built by copying an “industry standard.” You might hear that a 50/50 split between base salary and commission is the norm, or that paying 10% on the first year’s contract value is the way to go. This is a dangerous way to design a financial engine. Your internal financial tools point to a better starting point, which is your unit economics.

In your dashboards and KPI scheme, you are already encouraged to look at contribution margin by line of business, revenue per employee, and operational drivers like rework and defects. These concepts extend neatly into how you pay your sales team. 

Before deciding how much to pay a representative, leadership needs a rough view of the average gross margin per dollar of revenue for your main offers. You need to know the typical customer lifespan and the payback period, which is the number of months of gross profit it takes to recoup the cost of acquiring a customer.

You do not need perfect precision to make this work, but you do need direction. If your payback period is long, perhaps 18 to 24 months, paying heavy upfront commissions on every deal can be deadly to your cash flow. If your churn is high in certain segments, you probably shouldn’t richly reward closing those deals without some condition attached to their retention.

Think of this as applying a scoreboard mentality to a single customer. You must ask, given what it costs to win and serve this type of account, how much room you really have to compensate sales and still hit your margin targets. 

Only after you know that answer should you begin discussing commission rates and accelerators.

Aligning Payment with Behavior

Sales compensation is the behavioral equivalent of a KPI. It pays people to make specific trade-offs. If you are running an MRR-driven business, you generally want to reward representatives for selling the right offers at the right price, selling to the right customers, structuring healthy contracts, and partnering with the success team.

This means you want your team to hit or exceed target pricing and margins, minimizing heavy discounts and random exceptions. You want them hunting for the ideal customer profile, specifically those who have a good chance of succeeding and renewing. 

You want contracts with longer terms where appropriate, and reasonable implementation scopes rather than promising everything under the sun just to get a signature. 

You also want clean handoffs with good documentation so that the customer is supported early, rather than being “thrown over the wall” to a support team that has no idea what was promised.

Make this explicit. Your compensation plan should read like a strategic brief. It should state clearly that the company will pay the most for growing healthy, high-margin, long-term recurring revenue from best-fit customers. 

Once that statement is clear, you can translate it into the numbers that will drive the paycheck.

Design Principles for Profitable Growth

There are five design principles that align with this thinking. The first is to weight compensation toward gross profit, not just contract value. Your financial dashboards track margin and profit trends because top-line growth that erodes margin is a warning sign. You should use the same logic in sales compensation. 

You can choose to pay commissions on the gross margin of the revenue rather than the top-line number. Alternatively, and perhaps simply, you can pay on the revenue but only if target price and discount guardrails are met. 

For example, a rep might get full commission if a deal is sold at or above target price, but reduced or zero commission if the discount exceeds a certain percentage without approval. This trains the team to think about value and scope, not just getting the signature.

The second principle is to tie part of the payout to retention or customer health. Recurring revenue is only valuable if it recurs. Your KPI view of customer metrics likely includes retention, churn, and perhaps customer satisfaction scores. These can inform compensation too. 

Common patterns include paying a portion of the commission at the close and the remainder after the customer hits a retention milestone, like staying live for six months or renewing for a year. You might also include a clawback provision where the rep has to pay back the commission if the customer churns within the first few months. This sends a powerful message that you get paid most when customers stick and succeed.

The third principle is to reward mix and focus rather than just volume. Your KPI plan talks about segmenting performance by product, region, or segment so you can see where the real value lies. 

Some business lines are simply more profitable and strategic than others. You can use tiers in your compensation plan to reflect this. Offer higher commission rates for strategic offers or segments that match your ideal profile and drive better unit economics. 

Conversely, offer lower rates for low-margin or legacy contracts that keep people busy but do not build long-term value. This nudges the field toward the same portfolio decisions leadership is making.

The fourth principle is simplicity. Your internal tools likely make a big point of simplicity, favoring scorecards with a handful of numbers and dashboards that show the big picture on one page. 

Apply that to compensation. There should be no more than two or three main drivers, such as new revenue, margin quality, and retention. The formulas should be clear enough that a rep can calculate their earnings on the back of an envelope. If they need a spreadsheet and a lawyer to understand how they get paid, they will revert to the one metric they do understand, which is usually contract value, and ignore the rest of your strategy.

The fifth principle is to align compensation with your scorecards and dashboards. The most powerful systems are integrated. Scorecards feed weekly leadership meetings, and dashboards show the financial effects of operational decisions. 

Your sales compensation plan should plug into this same loop. Whatever metrics you use in compensation—whether it is new revenue, gross margin percentage, or retention—should show up on team scorecards and executive dashboards. Leaders should review them weekly. 

When performance drifts, the conversation becomes both behavioral and systemic. This keeps the compensation plan from being a dusty document in a drawer and turns it into a living part of the operating system.

A Sample Structure for Success

To visualize this, imagine a structure for a New-Logo Account Executive. Their On-Target Earnings might be split 50/50 between base salary and variable commission. The variable portion is then broken down to drive specific behaviors.

The bulk of the variable pay, perhaps 60% to 70%, is tied to New MRR at or above target pricing. The commission rate is based on the new monthly recurring revenue multiplied by a “quality factor.” If the deal is at or above target price, the factor is 1.0. If the deal has approved discounts, the factor drops to 0.5. If it creates deep, unapproved discounts, the factor hits zero.

Another 20% to 30% of the variable pay is tied to retention and expansion. This could be a quarterly bonus based on the net revenue retention of the rep’s book of business. If they retain more than 110% of their revenue through upsells and renewals, they get the full bonus. If they drop below 100%, meaning they are losing revenue, they get nothing.

The final slice, maybe up to 20%, is reserved for strategic initiatives. These are temporary bonuses or “spiffs” for closing deals in strategic segments or selling new product lines that fit the company’s growth plan. This portion is time-bounded so you can change the emphasis as the company strategy evolves.

Crucially, this plan includes guardrails. There is a clawback on upfront commission if a customer churns within three to six months. There is also a requirement for a deal review if the discount goes too high or the scope requires significant non-standard work. This isn’t the only way to build a plan, but it illustrates the shift from paying a percentage of any revenue to paying more for deals that create high-quality, profitable revenue.

The Transition Plan

Redesigning a compensation plan can feel daunting, but you don’t need to blow up your entire structure overnight. You can use the same incremental, test-and-learn rhythm that your scorecard tools encourage.

Start with a 30-day phase to understand your current reality. Analyze the last six to twelve months of closed deals. Look at the new revenue by segment and product, the gross margin, and the retention rates. Ask yourself where the current compensation plan is pushing the team toward the wrong kinds of deals. Identify which representatives are actually great for the business long-term and what behaviors distinguish them from the rest.

In the upcoming days, draft and test the new design. 

Create a plan using the principles of margin, ideal customer profile, and retention. 

Keep it to two or three main levers. Run the plan historically against your past data to see how payouts would have changed. 

Check that your top performers would still do well and that profitable revenue would have been rewarded more clearly. 

Socialize this draft with a small group of trusted managers and reps to see if it drives the behaviors you want and if they can explain it in their own words.

Finally, take the last days to roll out and integrate the plan. Launch it at the start of a quarter. Update your sales team scorecards to show the new metrics like margin quality and retention, not just bookings. 

Update your executive dashboards to include these profitable revenue metrics. In your weekly meetings, review the numbers like any other KPI. 

Capture learnings on where edge cases show up and where the plan might be too stingy or generous. 

Expect to adjust. Your internal materials likely state that good scorecards evolve over time as you learn what matters; compensation plans are no different.

Sales compensation is one of the most powerful levers in your system. It tells people what “winning” looks like more loudly than any speech or strategy deck. If you pay purely for volume, you will get volume, mixed with bad debt and churn. If you pay for profitable, sticky revenue, you will nudge the entire system in that direction. 

Reps will push back on bad deals, product and marketing will receive clearer signals about what works, and your dashboards will start to show healthier trends. Design your plan to match the business you actually want to build.

It’s your operating system for revenue behavior. Pay plans teach salespeople which deals to chase, which customers to qualify, how tightly to hold the line on standards, and whether profit discipline is optional or required. 

Get compensation right and you’ll see cleaner sales pipelines, healthier customers, and profit that sticks. Get it wrong and you’ll buy chaos: discounting, custom one-offs, and service teams left holding the bag.

This guide lays out a practical approach to compensating salespeople that rewards durable revenue from managed services, protects delivery profit from projects and hourly work, and keeps everyone from entry-level sales development through account managers pulling in the same direction.

Start with the North Star: Pay for Business You Actually Want

Before you pick a percentage, decide what a “good” deal looks like in your world. For most managed service businesses, good deals share five traits. They use your standard technology stack so you can support them at scale. They’re planned with discipline, meaning paid discovery when appropriate, formal change orders, and clear completion criteria. They’re priced with integrity, meaning no off-menu discounts without leadership approval. They renew and expand, with managed services contracts that have annual price increases built in. And they deliver healthy service profit when the work is performed, not just on paper.

Your compensation plan should put a bright spotlight on those traits and a dim light on everything else. In practice, that means tying variable pay to the quality of revenue and the profitability of delivery, not just top-line sales numbers.

Roles, Responsibilities, and the Right Mix of Base and Variable

Managed service sales isn’t one-size-fits-all. Compensation should reflect the impact, risk, and control each role has.

Sales Development Rep: Their mission is creating qualified first meetings for new customer managed services and project discovery. They should have heavier base salary and lighter variable pay, for example 70% base and 30% variable, with simple activity and meeting quality gates. Variable pay triggers on held meetings that meet your ideal customer profile and pass qualification for budget, need, timing, and technology alignment. The key is paying for qualified meetings, not just any meetings. Include a small bonus when pipeline progresses to proposal stage to reinforce lead quality.

Account Executive for New Customers: Their mission is closing new managed services customers and attaching standards-based projects. They should have balanced compensation, for example 50% base and 50% variable. The on-target earnings should reflect territory reality and lead flow. Variable pay triggers on signed agreements and milestone collections, with accelerators for standard stack deals, multi-year terms, and paid discovery attachment.

Account Manager for Customer Success: Their mission is retaining and expanding existing clients, driving adoption of the standard stack, and landing annual price increases. They should have balanced to base-heavy compensation, for example 60% base and 40% variable. Variable pay triggers on net revenue retention, maintaining profit margin, stack adoption milestones, and successful renewal at target pricing.

Solutions Architect or Pre-Sales: If they’re commissioned at all, their mission is scoping accurately, protecting profit, and guiding customers to standard solutions. They should have mostly base salary with a small team bonus tied to profit attainment on delivered work. Avoid deal-by-deal commissions. Instead, reward the system: accurate scoping, fewer write-offs, and strong change order capture.

Build Plan Mechanics Around How Revenue Is Earned

Managed service revenue isn’t one stream. It’s three, and each behaves differently. Your plan should reflect that reality.

For Managed Services Monthly Revenue: Reward new customers, seat expansions, and clean multi-year terms at your standard stack and target pricing. Consider provisional payout early, for example after the first successful service month, with a true-up after onboarding at month three to six to align with actual delivery performance and collections. Monthly recurring revenue is durable but front-loads onboarding risk. A split payout balances motivation with prudence.

Here’s an example. New monthly recurring revenue closes at $8,000 per month on a 36-month term. Payout works like this: 40% of the commission on first successful month, with remaining 60% at month four contingent on onboarding being complete, first three invoices collected, and delivery meeting profit and service level targets.

For Projects with Fixed Fees: Reward projects scoped through paid discovery if complex, aligned to standards, with crystal-clear assumptions. Pay on collected milestone billings with a final true-up at project close to reflect actual costs including change orders. Projects carry estimation risk. Milestone-based payouts plus true-ups reduce drama and prevent paying on phantom profit.

For Time and Materials Hourly Work: Reward adherence to rate card, minimal discounting, and accurate time capture. Pay monthly on collected invoices.

Price Integrity, Discounts, and Governance

Your pay plan is only as strong as the rules that guard it.

Require standard technology stack only. If a customer insists on exceptions to your standard stack, route to leadership for approval and require services team sign-off. Use a discount approval matrix. Never give salespeople unilateral discount power on services or monthly recurring revenue beyond a tight threshold like 5%. Larger concessions require approval from both sales leadership and delivery.

Make paid discovery a habit. For complex projects, make paid discovery the default. It improves planning accuracy, changes the buying psychology, and boosts the probability of successful delivery. Change orders are non-negotiable. Scope drift kills profit. Your compensation plan should never encourage “do it for free to close the deal.”

These guardrails protect your services team and send a message: we get paid for our expertise, not just our effort.

Setting Quotas and Earnings Targets That Won’t Break Reality

A plan that counts on miracles will create bad behavior fast. Ground your quotas and on-target earnings in math.

Start with lead flow and conversion. How many ideal customer profile leads do you generate each month? What’s your historical conversion by stage from qualified lead to discovery to proposal to win? Calculate average deal size by type: new customer monthly recurring revenue, typical project order value, average hourly work run-rate. Factor in expected profit margin and collections because delivery capacity and team utilization shape what’s actually possible.

Here’s a back-of-napkin example. Twenty ideal customer meetings per month leads to 12 discoveries, leads to 8 proposals, leads to 3 wins. Average new customer monthly recurring revenue is $6,000. Average project is $35,000. Projects attach to 2 of 3 wins. Attainable for one account executive per quarter is roughly $54,000 new monthly recurring revenue plus $210,000 in projects. Translate that into an annual target and on-target earnings that a competent account executive can hit 70% or more of the time without heroics. If you need miracles to hit plan, fix marketing, coverage, and offer quality, not compensation.

Percentages, Accelerators, and Decelerators

The exact figures will depend on your model, but here’s how to think about the controls.

Base commission rates should be calibrated so that hitting a realistic quota yields on-target earnings for on-plan performance. Accelerators reward over-performance, but only on healthy deals that are on your standard stack, at target pricing, with strong delivery profit. For example, 1.2 times payout on eligible revenue above 110% of quota. Decelerators reduce payout on deals that required deep discounts, stack exceptions, or profit misses. Special temporary incentives can be used in targeted, time-boxed ways, for example a “paid discovery attachment” bonus or “standard stack conversion” bonus to steer focus without rewriting the plan.

A quick rule: accelerators should be earned by quality as much as by quantity. No one should be able to “accelerate” by discounting their way to volume.

Ramps, Draws, Clawbacks, and Caps

These are the safety rails that keep your plan fair.

New hires need runway. Provide a ramped quota for the first two quarters, for example 50% then 75% then 100%, and training milestones that unlock full variable pay. If your market has long sales cycles, a recoverable draw can smooth cash flow in early months while keeping incentives intact. Use clawbacks sparingly and only for genuine reversals like customer non-payment, early cancellation within a defined window, or fraud. Make rules clear and enforce them consistently. Avoid hard caps on earnings. If you must cap, do it only on low-quality revenue or deals outside policy.

Make Renewal and Expansion Everyone’s Business

In managed services, the second sale, meaning renewal plus expansion, is the business. Compensation should make that obvious.

Tie a meaningful slice of account manager variable pay to net revenue retention, for example thresholds at 100%, 105%, and 110%. If your contracts include annual price increases, reward successful execution. Provide playbooks, calendars, and manager support so salespeople don’t “forget” the increase. Pay small bonuses for standard stack conversion milestones like security software rollout completed across customer, multi-factor authentication enforcement, or backup compliance. These reduce support noise and increase customer lifetime value.

Partnership with Delivery: Compensation That Respects the Hand-Off

Sales doesn’t close a spreadsheet. They close a promise that Services must keep. The healthiest managed service businesses formalize the partnership.

Align pre-sales under Services, even if they have a dotted-line reporting relationship to Sales, so planning and proposals reflect real delivery standards and costs. Require service sign-off before close for fixed-fee work and stack exceptions. Don’t create “free work” incentives. Compensation shouldn’t tempt sellers to absorb change requests without a change order. Use shared indicators. Track variance between sold and delivered profit. When variance is low, recognize both teams.

Data, Systems, and the One Key Habit

Great compensation plans die in bad data. If you want compensation to drive the right behavior, invest in three operational requirements.

First, accurate time entry and project accounting, or you can’t tell what a deal truly produced. Second, clean product and service catalog with rate cards, bundles, and standard options, or every quote becomes custom. Third, weekly pipeline discipline with stage definitions and exit criteria, or forecasts become fiction.

The single habit that transforms managed service sales is paid discovery on complex work. It buys you time to understand the environment, aligns expectations, and more than pays for itself in fewer write-offs and stronger delivery profit. A compensation plan that rewards discovery attachment will quietly make your whole company better.

Example: Turning a Good Deal Into Compensation Dollars

Let’s make it concrete with a simplified scenario.

New customer monthly recurring revenue is $7,500 per month on standard stack with a 36-month term. Onboarding project is $28,000 fixed fee, scoped through paid discovery. Hourly work add-ons total $8,000 in the first two months at standard rates.

Payout logic, which is illustrative not prescriptive, works like this. For monthly recurring revenue, provisional payout after the first successful month at 40% of the earned commission, with remaining 60% at month four once onboarding completes and invoices are collected. Accelerator applies if the deal met or exceeded target pricing and includes all core stack components. For the project, payout on collected milestones at 30%, 40%, and 30% with a final true-up at project close in case of change orders or scope variance. For hourly work, monthly payment on collections.

Notice how the timing protects cash and profit while still rewarding the salesperson for doing the right things: selling the standard stack, charging for discovery, and staying inside the rate card.

Frequently Asked Questions

What if the salesperson inherits a warm lead from marketing or a partner? Great! Quota should already assume a blend of sourced and assisted opportunities. Don’t reduce payout for marketing-sourced work. Instead, measure and coach on conversion rates by source.

Should we pay higher rates on product resale? Be careful. Hardware and software resale can be low profit and high hassle. Pay something, but generally less than services and monthly recurring revenue, and only on collected invoices. Reward bundling that drives standard stack adoption rather than one-off sales.

Our projects sometimes run lean because the customer changed requirements. Do we still pay? Pay according to the policy and fix the root cause. If change orders weren’t issued, that’s a process problem. Make change orders the norm, not the exception, and your compensation plan won’t be at odds with delivery.

Can we just pay on revenue to keep it simple? You can, but you’ll teach salespeople to chase any dollars, not the right dollars. Simplicity is good. Misaligned simplicity is expensive.

How to Roll It Out Without Wrecking Morale

Changing compensation is emotional. Do it with clarity, fairness, and speed.

Publish the policy in plain language with examples. Include definitions of what counts as a qualified meeting, a standard-stack deal, and a collected milestone. Run shadow calculations for one to two months so salespeople can see the “old versus new” impact. Train the managers first. They will translate the plan in one-on-one meetings and pipeline reviews. Pick a pilot group of a few salespeople and deals to prove mechanics, timing, and reporting. Go live with a certain date and a clean slate for anything not already in contract review. Inspect weekly and tune quarterly. Don’t rewrite monthly, but do clarify and improve edge cases.

Scoreboard: Indicators That Tell You the Plan Is Working

Keep the list short and brutally relevant.

Track managed services net revenue retention by group and overall. Measure variance between sold and delivered profit on projects and monthly recurring revenue after onboarding. Track percentage of deals on standard stack and percentage with paid discovery where appropriate. Monitor average discount versus rate card and approval adherence. Measure change order capture rate and value. Watch sales cost per profit dollar, with the goal trending down over time.

If these trend the right way, your plan is doing its job.

Bringing It All Together

The best compensation plan for a managed service business is boringly consistent. It rewards standardization, real customer value, and the discipline that makes delivery predictable. It’s simple enough to explain on a whiteboard and specific enough to prevent games. And it sends the same message every day: we reward durable revenue, honest planning, price integrity, and teamwork with Services.

The result is a compensation system that pulls your business toward healthy growth instead of pushing it off a cliff. When salespeople understand that their success is directly tied to the quality and profitability of what they sell, not just the volume, behavior shifts naturally. They start asking better questions during discovery. They defend pricing because they understand the link to delivery quality. They embrace standards because they see how it makes everything else easier. And they partner with services instead of throwing deals over the wall.

That transformation doesn’t happen because of a motivational speech. It happens because the compensation plan makes the right behaviors the rewarded behaviors, consistently and transparently, month after month.

This guide gives sellers and account managers a practical questioning approach you can use on your very next call. 

It focuses on asking about real events rather than opinions, actively listening for evidence, and using a simple structure to convert answers into next-step momentum.

Why Questions About Real Events Work in Sales

Questions about real events ask buyers to recount what actually happened in their environment: recent incidents, actions they took, and results. Not what they might do in theory. 

Past behavior is one of the best predictors of future behavior, especially when you’re evaluating readiness to change vendors, standardize technology, or fund a remediation project.

A few core principles to keep front and center. History repeats itself, so ask for specific stories and you’ll learn how the organization really behaves under pressure. Specific qualities trump claims. 

Don’t settle for “we care about security.” Ask for the last time they enforced multi-factor authentication across a skeptical department and what they did when adoption hit resistance. 

Gut feelings aren’t evidence, so seek observable facts like tickets, service levels missed, incidents, invoices, and approvals. Avoid hypotheticals. “What would you do if…?” invites fiction. Ask “Tell me about the last time…” instead.

The CAR Loop: Context, Actions, Results

When a prospect answers, listen for three parts of a complete story. First, context meaning background, constraints, who, what, and when. Second, actions meaning what they actually did. Third, results meaning what happened and what changed.

This simple loop keeps you from jumping to solutions before you understand their world and gives you concrete return on investment targets later.

Use it live on calls. For context, ask “Give me the background: who was involved, and how did you first notice the issue?” For actions, ask “Walk me through the steps you took and the timeline.” For results, ask “What were the outcomes in downtime, tickets, or dollars?”

That structure mirrors how skilled interviewers listen for evidence and is just as effective in sales discovery.

The Five Discovery Outcomes Every Call Should Drive

Before you write questions, be crystal clear on what “forward” means. 

For most managed service sales conversations, a strong discovery call produces five things. First, problem clarity meaning quantified pain or risk. 

Second, stakeholder clarity meaning who signs, who blocks, and who lives with the outcome. 

Third, standard technology fit meaning are they willing to adopt your way. 

Fourth, economic clarity meaning how they’ve paid for change before and why this is worth it now. 

Fifth, next step meaning paid discovery, technical assessment, or defined pilot.

Tie these outcomes to your pipeline stage definitions so “qualified” really means qualified. High-performing teams align questions to clear stage exit criteria like “Investment intention validated” or “Purchase scope and time agreed.”

Core Question Patterns

Below are question templates built to get real stories and evidence. Use them as written, then customize the details to your service and technology stack.

“Tell me about the last time…” for recent incidents: Questions like “Tell me about the last time a user compromise or email breach disrupted your team” or “Walk me through the last attempted price increase from your current provider, what happened?” prompt concrete narratives you can measure and model.

Follow up with the context, actions, results loop. For context, ask “When did it happen? Who was involved? What systems were affected?” For actions, ask “What steps did your team and provider take in the first 24 hours?” For results, ask “How long to restore? What did it cost in overtime, lost productivity, or goodwill?”

“Give me an example…” to bridge claims to evidence: Use when prospects claim values like “security-first,” “disciplined processes,” or “we’re cloud-first.” Ask “Give me an example of enforcing a security control that a business unit resisted. What did you do to make it stick?”

“Describe a situation when…” for process and governance: Questions like “Describe a situation when a project went over scope. How did you handle change orders?” or “Describe a situation when a technology initiative slipped because of non-technology stakeholders. What did you do differently next time?”

Open-ended, then closed, then confirm: Start wide to learn, close to confirm, and commit. Open question: “What’s driving your interest in a new managed service provider this quarter?” Closed question: “Did that outage exceed four hours?” Confirm: “So the CEO expects a board-ready plan before month-end. Is that right?”

Qualification without awkwardness: Make your questions map to clear stage exits like “End-user engaged” and “Investment intention validated.” Ask “Who else will weigh in on this: security, finance, or operations?” Ask “When you funded the last cyber initiative, which budget paid for it, and who approved?” Ask “If we outline a paid discovery to verify scope, who would need to sign off?”

Price integrity and change management without discounting value: Small discounts wreck managed services profit quickly. Use questions that uncover value and protect price. Ask “When your current vendor cut price last year, what changed in service levels or response?” Ask “What would it be worth to avoid a recurrence of the last email compromise?” Then anchor the math using their story. This is how top-performing providers defend value and align incentives to delivered profit.

Turning Answers into Momentum: The Decision Debrief

After each substantive answer, do a quick decision debrief to convert story into forward motion.

First, recap the evidence. “Here’s what I heard: two outages last quarter, four hours each.” 

Second, translate the impact. “That’s roughly 64 staff-hours lost per incident.” 

Third, show standard alignment. “Our technology stack enforces multi-factor authentication and conditional access by default. Here’s how that would have changed the timeline.” 

Fourth, offer the next step. “The fastest way to confirm fit is a scoped, paid discovery. We’ll validate assumptions and hand you a board-ready plan.”

This keeps you inside a disciplined, multi-stage sales process where each exit is evidence-based rather than wishful thinking.

Questions That Disarm Resistance and Still Move Forward

Sometimes the blocker isn’t budget. It’s friction, fear, or politics. Use questions that acknowledge that reality while earning the right to proceed.

For surfacing stakeholders, ask “Who wins if this succeeds? Who loses? What do they need to feel safe?” This maps to end-user engagement and purchase scope clarity. 

For switching anxiety, ask “Tell me about the last time you switched a core system. How did you reduce risk during the cutover?” 

For competing priorities, ask “If an urgent project lands next month, what gets deprioritized? Who decides?” This helps you spot decision dynamics and set realistic timelines.

Ask Like a Pro: The Rhythm of a High-Impact Discovery Call

The best conversations are structured, time-limited, and consistent call to call. That makes answers comparable and decisions faster.

Here’s a 30 to 45 minute flow you can use. Start with agenda and outcomes for three minutes. “We’ll confirm fit, quantify impact, and agree on next steps.” Move to business context for seven to ten minutes. “Tell me about the last 90 days: wins, outages, near-misses.” 

Use context, actions, results follow-ups. Then cover systems and standards for seven to ten minutes. “Describe a situation when standards clashed with speed. What happened?” 

Address economics for five to seven minutes. “When you funded the last initiative, which budget paid, and what return on investment did you need?” This ties to “investment intention validated.” 

Cover decision path for five minutes. “Who approves this? What do they need to see, and when?” 

Close in three to five minutes by summarizing evidence, validating agreement, proposing next step like paid discovery or assessment, and booking the calendar.

Consistency isn’t boring. It’s professional, and it shortens sales cycles. In interviewing, putting structure around questions compresses the timeline to decision. The same is true in sales.

Questions by Pipeline Stage and Why They Work

Stage: Pain and Solution Qualified: Ask “Tell me about the last incident that had executive visibility. What changed afterward?” This proves real pain and avoids hypotheticals.

Stage: End-user Engaged: Ask “Who gets the call at 2 a.m.? Walk me through the last call and what happened next.” This surfaces operational impact and champions.

Stage: Investment Intention Validated: Ask “When you approved the last cyber spending, who signed, what threshold justified it, and how was return on investment measured?” This tests budget reality.

Stage: Scope and Time Agreed: Ask “Describe a situation when scope drifted. How were change orders handled?” This protects profit margin and timeline while preparing the buyer for your process.

Stage: Negotiation Completed: Ask “Beyond price, what non-negotiables would derail this: security posture, statement of work approvals, or communications plan?” This prevents late-stage surprises.

From Answers to Economic Impact So You Can Defend Price

A strong line of questioning makes commercial math feel obvious. Once you have evidence, translate incidents to dollars by calculating minutes of downtime times affected staff times average loaded hourly rate. 

Tie standards to risk reduction by showing how technology stack adoption would have changed the outcome timeline. Anchor price integrity by reminding the buyer that small service discounts can crater profit dollars, so the way to affordability is scope control and standards, not price-cutting.

When you later present options, those numbers are their numbers, not your claims.

Coaching Your Team to Ask Better and Keep Deals Moving

Managers should incorporate questioning practice into weekly pipeline reviews. Use a one-page score sheet listing qualities you expect to see evidence for on each opportunity: business impact, stakeholder clarity, economic path, standard technology fit. 

After each call, have salespeople fill it in while the evidence is fresh, exactly like disciplined interview panels do to speed up decisions and reduce bias.

Keep a collection, digital or physical, of tested questions by stage and scenario. It beats improvising, and it keeps your team from slipping into leading or hypothetical questions under pressure.

Bringing It All Together

Questions that move prospects forward are disciplined, evidence-seeking, and sequenced to your sales stages. They expose real pain, real economics, and real decision paths. 

They also respect your delivery team. By probing for scope discipline, change order practices, and willingness to standardize, you avoid deals that feel great today and hurt tomorrow.

Make it a habit to ask for stories, not opinions. Listen for context, actions, and results every time. Map your questions to clear stage exits. Turn answers into a clear next step, often a paid discovery, so progress is natural, not forced.

Do that consistently and you won’t just “have better discovery calls.” You’ll build a sales system that advances qualified opportunities, protects profit, and wins trust one evidence-rich question at a time.

The most common response is to “do more”: launch marketing campaigns, buy new tools, hire faster, add more projects. Yet many businesses discover, painfully, that “more” can become the very thing that stalls growth.

Below is a candid look at why growth efforts so often fail—and how to replace busywork with momentum that actually builds on itself.

We Confuse Activity with Outcomes

When growth stalls, it’s tempting to drown the problem in initiatives: new service agreements, fresh procedure manuals, another marketing push. The trouble is that activity. The things you do—gets mistaken for results—the things you achieve. 

Classic systems thinkers warn about organizations celebrating the volume of plans, papers, meetings, and content as if those were actual accomplishments. They call it the “cancerous multiplication of paperwork” being treated as output, not as a disease.

For managed service businesses, the modern version is dashboards packed with ticket counts, marketing leads, and automation rules without a clear tie to whether customers are staying, whether you’re making healthy profit margins each month, and whether customers remain satisfied after major incidents. 

If you don’t name the few outcomes that actually matter and connect every project to them, your growth machine quietly becomes a motion machine that’s busy but going nowhere. The mental reset is simple, if not easy: define what success looks like, then cut out the activities that don’t move you toward it.

We Have Strategy Without Execution (or Execution Without Strategy)

Many managed service businesses do have a strategy: focus on specific industries, sell more security services, move into technology advisory services, or standardize technology platforms. Fewer have the discipline to connect the people doing the work with the strategy that just got announced—and still fewer run a regular operating rhythm that keeps the connection alive.

The most durable operators insist on explicit connection among three processes managing people, setting strategy, and running day-to-day operations and they run these as a single system. 

The research on execution is blunt: it’s not enough to be “right” on one or even two of those; the connection between all three is the difference between muddling through and results that build on themselves.

In practice, this means your quarterly strategy. For example, migrate 60% of customers to your security technology stack, shows up in job descriptions and weekly operations reviews. Hiring, training, capacity planning, and incentives must be aligned to that one strategic move or you’ll fight invisible friction that exhausts everyone.

We Avoid (or Mishandle) Accountability Conversations

Growth collapses where accountability is vague. The most common failure isn’t “bad people” but rather “failed promises, missed expectations, and other poor behavior”. 

Which, handled poorly, corrodes trust and performance. The discipline is to address disappointments directly and safely: describe the gap between what was expected and what happened, explore why a reasonable person might have done what they did, and solve for both motivation and ability. That is the foundation of accountability.

Notice the order: get your head right before you open your mouth, then create safety in the conversation. When there’s enough safety, you can talk to almost anyone about almost anything, starting by describing the performance gap in neutral, specific terms, then aligning consequences and support.

For managed service businesses, that sounds like: “In the third quarter we committed to completing software updates within the first 10 business days; we hit that target for 63% of devices. Let’s look at where the process broke. Was it the tools, time, or competing priorities and fix both the obstacles and the follow-through.”

We Hire for Résumés and Speed, Not Evidence and Fit

A growth spurt exposes your hiring process. Many businesses default to credentials, buzzwords, and a rushed single interview. But the evidence shows you get better hires—and faster decisions—when you run a structured, same-day panel that examines past behavior for the qualities that matter most in the role. 

Specific qualities like communication skills, follow-through and attention to detail, and people skills outpredict generic years of experience for many customer-facing roles.

The practical twist: stack all interviews in one day, score candidates against a common rubric of key qualities, and decide before the day ends. This compresses the hiring timeline and forces decisions based on shared evidence rather than gut feeling or drift.

We Grow Revenue Without Protecting Profit Reality

Here’s the hard truth: revenue growth without profit discipline is just scaled-up stress. 

Two patterns kill profitability in managed service businesses. 

The first is labor creep. As support tickets surge, managers “solve” annoyances by adding people. Costs creep up, profit per team member falls, and you slide into a trap where added revenue actually worsens your capacity and cash flow. 

The remedy is to distribute annoying work intelligently, automate relentlessly, and hold the line on hiring until the absolutely necessary moment. And you can’t do that unless you absolutely understand your numbers.

The second is pretend profit. Owners underpay themselves and call the difference “profit.” Until you pay yourself a realistic market wage inside your financial statements, your profit numbers lie to you—and you will make bad growth decisions. This principle sits at the foundation of disciplined growth in closely held firms.

The translation for managed service businesses: build a standard technology set to raise profit margins, communicate and enforce your regular review schedule to protect what’s included in your service, and track profit per team member as a key indicator across all your service lines. 

Company culture dies without profitability; profitability dies without productivity.

We Dangle Incentives That Distort Behavior and Timeframes

Monthly quotas and special bonuses can be useful. Until they pull revenue into the wrong time period, degrade service delivery, or celebrate sales the team can’t actually implement. 

Incentives tied too tightly to short intervals invite end-of-month games like pulling deals forward or pushing work out, while annual plans with quarterly partial payments keep teams oriented to sustained performance.

A simple pattern that avoids whiplash: accrue bonus eligibility based on annual performance with partial quarterly payouts that self-correct, and reserve the largest payout for year-end. So teams keep solving for the full year, not just the next 10 days.

We Starve the Very Capabilities Growth Requires

Many managed service businesses underinvest in what growth actually consumes: people development, systems, and procedures. Evaluating leaders only on short-term earnings or cash tempts cutbacks in training, documentation, and process maturity. Easy ways to show a good quarter, deadly over time.

The balanced way to manage is to fund learning and growth explicitly, building employee capability, information systems, and alignment so today’s strategy can become tomorrow’s steady state.

For managed service businesses, that means investing in skill development plans, standard procedures embedded in your management software, and a weekly ritual that turns frontline ideas into improvements. Because in today’s information economy, ideas for improving processes must come from the people closest to customers and the work.

How to Build Real Momentum (Without Burning the House Down)

What succeeds in managed service businesses is not a heroic sprint but a repeatable rhythm that compounds. Here’s a practical approach you can implement now.

Clarify the few outputs that matter and connect activities to them. Pick three to five outcomes that truly indicate success. For example, customer retention rate, profit per technician hour, security technology adoption rate and reject projects that don’t move them. This counters the confusion between activity and outcomes and forces focus.

Run an execution rhythm that links people, strategy, and operations. Every quarter, set one or two strategic priorities with specific numeric targets. Monthly, review capacity and sales pipeline aligned to those targets. Weekly, hold a 45-minute operations review that looks at variances from plan and next best actions. Insist that hiring, training, and incentives reflect the quarter’s priorities. The power isn’t any single meeting; it’s the connection between all of them.

Adopt a profit floor and guard team productivity. Install a non-negotiable labor efficiency indicator that guarantees your target profit, then design each month around protecting it. Hire at the last responsible moment and standardize your technology stack to lift margins. Treat adding people to solve annoyances as a red-flag event, not a convenience.

Fix your incentives and reporting rhythm. Move from monthly heroics to annual incentive calculations with quarterly, self-correcting payouts. Publish a simple, repeating reporting package that includes your financial statement with a realistic owner’s wage, service profit margins by line of business, profit per technician hour, how old your backlog is, and technology stack adoption. Keep the numbers you can defend; avoid vanity metrics that invite gaming the system.

Professionalize hiring—quickly. Build a candidate pipeline by recruiting continuously through employee and customer referrals, then run same-day panel interviews that probe for the qualities your roles truly require. If you do it correctly, you can decide that day. You gain speed and quality, and you stop mistaking résumés for actual capability.

Install an accountability approach. Before the conversation, master your understanding of the situation and consider the sources affecting performance—yourself, others, and the environment; motivation and ability. In the meeting, describe the gap, restore safety, agree on root causes and what support is needed, decide who does what by when, and schedule the follow-up. That sequence keeps candor and respect intact.

Budget for capability, not just quarters. Set aside explicit time and money for standard procedures, documentation, cross-training, and system improvements. Growth consumes these assets; if you don’t build them, you’ll buy them later at a panic premium.

One Keystone Habit That Changes Everything in 90 Days

If you want one habit that changes the texture of your business in 90 days, try this: every Friday, run a 30-minute “Fix Forward” session with one frontline team (service, projects, or onboarding). 

Ask three questions: What slowed you down this week? What did a customer trip over? What did we promise that our system made hard? 

Pick one improvement you can complete by next Friday. A procedure tweak, an automation, a checklist step, a template response. Assign an owner, and review it the next week.

Individually, each change is tiny. 

Together, they form an engine that builds on itself, lifting profit margins, reducing rework, and improving customer satisfaction without heroics. 

This rhythm reflects the same logic behind connecting execution to strategy and investing in capabilities: you’re making the organization a little better every week in the direction your strategy requires.

The Takeaway

Growth in managed service businesses fails less from lack of ideas and more from lack of operating discipline. The fixes are not exotic: name the few outcomes that matter, link your people and operations to strategy, have the right conversations at the right rhythm, protect profit reality, professionalize hiring, and invest on purpose in the capabilities growth consumes.

Do that consistently, and your growth won’t feel like a fight. 

It will feel like momentum.

The better way? Know your actual costs, understand your value, make buying decisions simple, and raise prices regularly. Think of pricing as a system you build once, then maintain—not just a number you pick and hope works.

Step 1: Know What Things Actually Cost You

You can’t price well if you don’t know what it costs to deliver your service. 

The math seems simple but most people get it wrong.

Here’s the wrong way: Take a technician’s $50,000 salary, divide by 2,080 hours (a full work year), and mark it up a bit. Seems logical, right? 

The problem is this ignores health insurance, payroll taxes, software tools, training time, vacation days, and the fact that nobody bills 100% of their hours. When a technician is in team meetings, doing paperwork, or waiting for a customer to respond, those are hours you’re paying for but not billing for.

The right way involves understanding the full picture. 

Successful MSPs aim to bring in at least $2.50 in revenue for every $1 they pay in wages. So if you pay someone $50,000, you need them generating at least $125,000 in revenue. 

This 2.5× rule accounts for all those hidden costs and ensures healthy profit margins. When you hit this target consistently, you’ll have enough left over to cover your office rent, your own salary, marketing costs, insurance, and still have money left for growth and savings.

Think about it this way: if you’re paying your technicians but barely breaking even at the end of the month, something is fundamentally wrong with your pricing. 

You’re essentially running a charity, not a business. 

The 2.5× rule gives you a clear target to aim for.

Here are some questions you need honest answers to. At your current prices, can you afford to pay your team well? This matters because good technicians don’t stay at companies that underpay them. 

How many billable hours can you realistically expect per technician? 

Hint: It’s not 40 hours a week. Factor in training, administrative work, team meetings, and downtime between projects. Most healthy MSPs plan for around 30 or more billable hours per technician per week, not 40.

If you need to hire senior, expensive experts, will customers pay rates high enough to cover them? This is a crucial question. If you can’t afford expensive senior people at your current prices, you need a different team structure. 

You need more junior technicians doing most of the work, with just a few experts supervising and handling the complex problems. This pyramid structure is how most successful service companies operate. 

The expensive experts aren’t in the trenches all day—they’re guiding the team and solving the hardest problems.

The trap many business owners fall into is being too optimistic about utilization. They imagine their technicians will be busy every minute, but the reality includes gaps between appointments, time spent documenting work, internal meetings, and training on new technologies. 

When you factor in vacation time, sick days, and holidays, a technician working a full year might only have 1,800 truly available hours, not 2,080. 

And of those 1,800 hours, maybe only 1,400 are actually billable to customers. This is why the simple salary-divided-by-hours math fails so badly.

Step 2: Price for the Value You Deliver, Not Just Your Costs

Once you know your minimum viable price (your “floor”), you can charge more based on the value you provide. This is where many MSPs leave massive amounts of money on the table.

Great MSPs don’t just “match what others charge.” They price based on what they’re worth to the customer. Think about what you’re really delivering. You’re providing risk transfer, meaning you’re taking on the stress and liability of their technology. When their email server crashes at 2 AM, that’s your problem, not theirs. That peace of mind has real value. 

You’re also delivering productivity gains because their team works better when systems actually work reliably. Nobody can work effectively when they’re fighting with their computer all day. And you’re providing scalability, meaning they can grow their business without technology disasters derailing everything.

Here’s something most MSPs learn the hard way: when you launch a new service offering, you’ll always underestimate the real cost. 

Most companies discover a pattern. Their initial estimate is “This will cost us X to deliver.” Then after 20-30 customers, reality hits: “Oh, this actually costs us twice what we thought—2X.” Finally, at maturity, when they’re doing it really well and consistently, they realize “To do this properly takes three times our original estimate—3X.”

Smart companies learn from others’ mistakes. They price at 3X from day one and save themselves years of losing money while “learning.” 

Yes, this might mean your prices are higher than some competitors when you launch something new, but you’ll actually make money while they’re bleeding cash and wondering why their “profitable” new service is bankrupting them.

Here’s another counterintuitive truth: don’t discount for bigger customers. 

It seems logical at first. A company with 200 employees should pay less per person than a company with 20 employees, right? Wrong. It’s actually backwards, and here’s why. 

Bigger customers usually need more sophisticated tools, more experienced technicians, more account management time, and more careful coordination. Your cost per user goes up with bigger accounts, so your price should too.

Think about the difference between supporting a 10-person startup where everyone uses the same basic setup versus a 200-person company with multiple departments, remote workers, compliance requirements, and a CFO who wants detailed reporting. 

The 200-person company is dramatically more complex to support. You might need dedicated account management, formal quarterly business reviews, more sophisticated monitoring tools, and technicians who can handle enterprise-level challenges. 

All of that costs more, not less.

Step 3: Make Buying Simple

Don’t give customers a menu of 47 service options. 

It paralyzes them and leads to bad choices that hurt your margins. When you present too many options, customers focus on finding the cheapest possible combination rather than thinking about what they actually need.

A better approach is to offer one comprehensive service package with clear scope. Let customers think in simple terms: $X per employee per month for complete IT support, or $Y per month for their whole company. 

The detailed breakdown lives in the contract (so you can adjust when they add people), but the buying decision is simple: “Do you want your technology managed well? Here’s the price.”

This simplicity benefits everyone. Customers can make faster decisions because they’re not trying to figure out whether they need the silver plan with extra backup or the gold plan with faster response time. 

They’re just deciding whether they want comprehensive IT support or not. Your sales process gets faster too. Instead of spending hours customizing quotes and going back and forth on which services to include, you’re having a straightforward conversation about whether you’re the right fit for their needs.

The detailed units still matter, but they belong in the contract, not the sales pitch. 

The contract specifies things like “includes up to 50 users, 50 computers, 5 servers” so you can cleanly handle adds and removals. But during the sales conversation, you’re focused on outcomes: “Your team will have reliable technology, fast support when things break, proactive monitoring to prevent problems, and the security protection your business needs.”

When it comes to hourly pricing, avoid it when possible. “Call us and we’ll bill you by the hour” creates unpredictable income for you and scary surprise bills for customers. Neither party benefits from this arrangement. 

You can’t forecast your revenue, and customers are afraid to call you for help because they don’t know what it will cost.

If you must do hourly work, sell prepaid blocks like “20 hours for $3,000” that expire if unused and auto-renew monthly. This gives you predictable recurring revenue and gives customers predictable expenses. 

But recognize that this is still less stable than managed services where customers pay the same amount every month regardless of how much support they need. Managed services is where you want most of your revenue to come from.

Step 4: Raise Prices Every Year (Yes, Really)

If your prices don’t go up annually, your service quality will quietly decline. This isn’t optional, it’s mathematical reality. 

Here’s why it matters: Your team expects raises, and they should get them. If you want to keep good technicians, you need to pay them more this year than last year. Health insurance costs rise, recently by 5% to 10% or more annually. Software tools get more expensive. 

Microsoft, your monitoring tools, your security stack—they all increase prices regularly. And everything costs more due to inflation. Your office rent, your internet connection, even your coffee for the break room costs more this year than last year.

If your revenue per customer stays flat while all your costs increase, the math only works one way: your profit margin shrinks. 

Eventually you reach a breaking point where you either have to cut corners (hurting service quality), underpay your team (losing good people), or work twice as hard just to stay in the same place financially.

What great companies do is build automatic annual price increases into 90% of their contracts, typically 2% to 5% per year. This isn’t sneaky or aggressive. It’s just keeping pace with the reality that costs increase over time. 

Every other vendor your customers use does this. Their office lease goes up, their insurance premiums increase, their suppliers raise prices. It’s normal business.

Here’s what you’re probably thinking right now: “We’ll lose customers if we raise prices!” This fear is so common and so overblown. 

Here’s what actually happens: almost everyone accepts reasonable increases without complaint. The few who push back can usually be retained with a conversation about the value you provide. And the very rare customers who actually leave are usually your most difficult, least profitable customers anyway. 

Your team will actually be relieved to see them go.

One IT company owner told me he lost sleep for weeks before announcing a 5% price increase to existing customers. He drafted careful emails explaining the increase, prepared detailed justifications, and braced for an onslaught of complaints and cancellations. 

Out of 40 customers, 38 didn’t even respond to the email—they just accepted it. One called to say “that’s fine, thanks for letting us know.” And one complained but ultimately stayed anyway. 

All that anxiety for nothing.

The key is making it normal, not dramatic. Put the escalator in the contract from day one so new customers know it’s coming. Treat it as routine business, not a big negotiation. 

Send a simple notification 60 days before it takes effect: “As outlined in our agreement, your monthly rate will increase by 3% starting in March, from $5,000 to $5,150. This helps us continue delivering excellent service as our costs for tools, insurance, and talent continue to rise.”

Step 5: Run Pricing Like a Business System

Great pricing isn’t a one-time decision. 

It’s an ongoing process that you build into how your company operates.

Start by giving pricing authority to the right people. Your service delivery team, not your sales team, should own pricing. Why? Because they actually deliver the work, they know the real costs, and they care about profitability, not just closing deals. Salespeople are optimists. 

Their job is to see the possibility in every deal and find ways to yes. 

That’s valuable, but it makes them terrible at pricing discipline. 

Service managers, on the other hand, are the ones who have to deliver on the promises, so they’re naturally more realistic about what things actually cost.

Make discounts rare and require approval from service management. When salespeople can discount freely, they will, because it makes their job easier. But each discount comes out of your profit margin. 

Over time, if you require approval for every discount and make the approval process slightly uncomfortable, your team will stop expecting to discount at all. 

Discounting stops being “normal” and becomes the rare exception for truly strategic situations.

You also need to track what matters. 

Know your profit per customer, not just your revenue.

A $10,000 per month customer who requires constant hand-holding and generates only $1,500 in profit is worse than a $5,000 per month customer who runs smoothly and generates $2,500 in profit. 

Revenue is a vanity metric, profit is what actually matters.

Forecast six months ahead. Plan for hiring and spending based on expected profit, not guesses. If you know you’re adding $50,000 in monthly recurring revenue over the next quarter, and you know your target profit margins, you can calculate exactly how much you can afford to spend on hiring another technician or investing in better tools.

Review your numbers monthly. 

Are you hitting your profit targets? If not, adjust quickly. Don’t wait until the end of the year to discover you’ve been unprofitable for months. Monthly reviews let you catch problems early when they’re small and fixable. 

Maybe you need to tighten up your processes to work more efficiently. Maybe you need to have tough conversations with customers who are consuming way more time than expected. 

Maybe you need to pause hiring until revenue catches up.

When presenting prices to potential customers, talk about outcomes, not itemized lists. Don’t say “3 server check-ins per month, 47 desktop monitors, 2 on-site visits, unlimited phone support.” That invites customers to question each line item and try to negotiate removing pieces to save money. Instead say “Your technology will be reliable, secure, and supported. 

Your team can focus on their work instead of fighting with their computers. When something breaks, we fix it fast. And we proactively prevent problems before they impact your business.”

Save the detailed units for the contract itself, where they help manage adds and removals smoothly. 

The contract might specify “50 users, 50 workstations, 5 servers” so everyone’s clear about what’s included and you can easily adjust when they hire more people or add servers.

A Real-World Example

Let’s make this concrete. A 25-person company signs up for your standard IT support plan. Your calculations show you’ll spend about 1 hour per employee per month on support, plus device management and quarterly business reviews. 

With all your costs factored in—technician wages, benefits, software tools, your overhead—you charge $150 per person per month. That’s $3,750 monthly or $45,000 annually from this client.

At that price, you’re hitting your target margins. After paying your technicians, covering software costs, and accounting for management time, you have healthy profit left over.

Three months in, their CFO asks for a detailed breakdown of exactly what they’re paying for. This is a test of your positioning. 

You politely but firmly explain: “We sell outcomes and results, not itemized tasks. You’re paying for reliable technology, fast support, and the peace of mind that comes from having experts managing your systems. But your contract does show per-person pricing so we can smoothly add or remove people as you grow.”

Most CFOs accept this because it’s actually reasonable. 

They don’t itemize their payments to their lawyer or accountant either. 

They pay for expertise and results.

At renewal time, your automatic 2.5% increase applies. The price goes from $150 to $153.75 per person. You send a brief notification, and they accept it without discussion. No drama, no negotiation, no stress.

Six months in, you notice two customers are taking more time than expected. Maybe they’re less organized, maybe their previous IT setup was worse than you realized, or maybe they’re just higher-maintenance personalities. You have two levers to pull. First, you tighten up your processes to get more efficient. 

Maybe you implement better documentation so tickets get resolved faster, or you do some training with their team to reduce repetitive questions. Second, for work that falls outside the normal scope—like a network redesign or a migration project—you propose a small project add-on at additional cost.

The system works because it’s a system. You’re not guessing and hoping each month. You have a process.

The Payoff

When you run pricing as a system—knowing costs, charging for value, keeping it simple, raising prices regularly, and managing it tightly—you get more predictable income, better profits without working harder, less stress and volatility, the ability to pay your team well, and customers who value what you do.

The difference between companies that struggle and companies that thrive often isn’t dramatic. It’s not about working twice as hard or being twice as smart. 

It’s about doing these basics consistently, measuring what matters, and making small improvements that compound over time.

You don’t need to be perfect. 

You just need to treat pricing like the business system it is, rather than a number you guessed and hoped would work. 

Build the system once, maintain it monthly, and let it compound. That’s how ordinary MSPs become quietly, sustainably profitable.