What go-to-market playbook works best for IT Services / MSP in 2027?

The revenue problem being solved

The structural squeeze on IT Services revenue is not a demand problem. Most regions still show more open IT roles than qualified applicants, and SMB and mid-market buyers have not stopped needing infrastructure, security, and support. The squeeze is a mix problem: the revenue lines that historically funded the business are shrinking faster than the new lines are growing.

Three forces drive it.

Resale compression. Hardware, endpoint, and license resale have moved toward low single-digit gross margins in most commodity categories. Distributor and vendor marketplaces now sell direct to the end customer at prices a reseller cannot beat, and the buyer knows it. Firms that still forecast revenue on a resale-plus-services blend find that the resale half of the forecast is now a rounding error on gross profit while still consuming quoting, procurement, and logistics labor.

Labor arbitrage pressure. Tier-1 and tier-2 support work has been industrialized. Remote monitoring and helpdesk labor is available at a fraction of onshore cost, and automation handles password resets, patching, and standard provisioning. Any service line that is defined as "we answer the phone and fix the laptop" is now a commodity with a visible market price. Buyers can and do benchmark it.

Consolidation and roll-ups. Private-equity-backed platforms acquire MSPs specifically to arbitrage the same labor and tooling across a larger base. That gives them pricing power on tooling and the ability to bid aggressively on seat-count contracts. An independent firm trying to win a 150-seat deal on price against a platform that owns 40,000 seats is playing a game it cannot win.

The revenue consequence is specific. A firm that was running 55% gross margin on a blended seat-plus-project mix can watch that fall into the low 40s without losing a single client, simply because the mix shifted toward the low-margin resale and commodity support lines. Net revenue retention looks fine while gross profit per technician stalls. That is the trap: the top line holds, the unit economics rot.

The escape is not better marketing. It is changing what you sell, to whom, and how it is priced. That is what the rest of this playbook covers.

Root-cause map

Before choosing a motion, it helps to see why generic managed IT stopped producing durable revenue. The failure is not in the sales team's effort; it is in the offer's position in the buyer's decision.

The left loop is the doom cycle most firms are in by default. The right path is the one this playbook prescribes. Note the entry point: an assessment, not a proposal. The assessment is what converts a price conversation into a scope conversation.

Benchmarks and ranges

Practitioners need numbers to sanity-check a plan against, not aspirational marketing claims. The following ranges reflect what well-run IT Services and MSP firms typically target. Treat them as planning bands, not guarantees, and adjust for region, vertical, and firm size.

Recurring versus project mix. Healthy firms typically target 60-75% recurring revenue and 25-40% project, advisory, and hardware-attached services. Firms below 50% recurring are exposed to every project-timing hiccup. Firms above 85% recurring often under-invest in the project work that seeds the next recurring expansion.

Gross margin by line. Managed services (remote monitoring, patching, endpoint management) commonly run 55-70% gross margin when the tooling is standardized and the labor is tiered. Co-managed and dedicated-technician arrangements run lower, often 40-55%, because they are labor-pass-through with limited leverage. Project and implementation work runs 35-50% depending on whether licensed engineers or generalists do the delivery. Advisory and assessment work, when it is productized, can run 60-75% because the deliverable is repeatable.

Net revenue retention. Best-in-class firms target 110-125% net revenue retention on the managed base. That means expansion from existing accounts outpaces churn. Below 100%, the firm is on a treadmill and must add logos just to stand still.

Client acquisition cost and payback. For SMB-focused MSPs, CAC payback in the 9-15 month range is a reasonable target. Verticalized offers with a defined assessment entry point often land at the faster end because the sales cycle is shorter and the offer is easier to explain.

Seat and endpoint pricing. Per-user, per-month managed service pricing for a full stack (endpoint management, patching, helpdesk, basic security) commonly sits in a wide band depending on scope and region, often roughly in the range of a few tens of dollars per user per month for lean stacks up to well over a hundred for full security-and-compliance bundles. The exact figure matters less than the discipline of publishing a catalog and holding the line.

Technician-to-endpoint ratios. A commonly cited planning ratio for remote-managed endpoints is roughly 250-500 endpoints per technician for standardized, well-tooled environments, and considerably lower where the environment is heterogeneous or the SLA is aggressive. Firms that cannot state their ratio cannot diagnose why margin is drifting.

Assessment-to-close conversion. A productized assessment (security posture, compliance readiness, or infrastructure risk) typically converts to a follow-on managed or project engagement at rates in the 40-70% range when the assessment is priced or bundled deliberately and delivered with a written roadmap. Free "audits" convert worse and attract tire-kickers.

Churn. Monthly logo churn in the 0.5-1.5% range is typical for SMB managed services. Above 2% monthly, the firm is leaking faster than it can sell.

These ranges are diagnostic tools. If a firm's recurring mix is 40%, its gross margin is 38%, and its net revenue retention is 94%, no amount of new logo hunting fixes the underlying issue. The mix has to change first.

Trade-offs and alternatives

No single motion is right for every firm. The verticalized outcome playbook is the strongest default for 2027, but it carries real costs, and there are legitimate alternatives worth understanding.

Verticalization versus horizontal breadth. Choosing two or three verticals (for example, healthcare clinics, legal, or manufacturing SMBs) lets a firm build reusable compliance templates, reference architectures, and peer proof. The trade-off is a smaller addressable market per vertical and the risk of over-concentration if one vertical hits a regulatory or economic shock. A firm that verticalizes into a sector with a single dominant software vendor also inherits that vendor's roadmap risk. The mitigation is to pick verticals that share underlying infrastructure patterns so tooling and skills transfer.

Outcome pricing versus seat pricing. Outcome or per-asset pricing (per endpoint, per site, per compliance framework) aligns the firm's economics with the client's risk and lets margin expand as automation improves. The trade-off is that outcome pricing requires the firm to actually measure and report the outcome, which means instrumentation, reporting labor, and a willingness to be accountable for a number. Firms without mature tooling often underprice outcome contracts because they cannot forecast their own delivery cost.

Productized assessment entry versus relationship-led selling. An assessment-led motion is repeatable, forecastable, and shortens the sales cycle because the buyer gets a tangible deliverable early. The trade-off is that it requires a genuinely good assessment methodology and delivery capacity; a weak assessment damages credibility faster than no assessment at all. Relationship-led selling still works in tight geographies but does not scale and does not survive the departure of the relationship holder.

Co-managed versus fully managed. Co-managed arrangements (the client keeps an internal IT person, the MSP provides tooling, escalation, and coverage) are often easier to sell into mid-market accounts and carry less delivery risk. The trade-off is lower revenue per account and a dependency on the client's internal staff quality. Fully managed carries higher revenue per account but also full accountability for outcomes the firm may not control.

Build versus buy for tooling. Building a proprietary platform or automation layer can be a genuine differentiator, but it consumes engineering budget that a mid-size MSP may not have. Buying standard tooling (RMM, PSA, documentation, security stack) keeps focus on service delivery but offers no defensible moat. Most firms should buy standard tooling and build only the automation that encodes their vertical-specific knowledge.

Geographic expansion versus density. Adding a new metro is expensive and dilutes delivery quality. Deepening density in an existing metro lowers travel cost, improves on-site response, and builds local referral networks. For most firms under a few hundred staff, density wins.

The honest summary: verticalized outcome selling works best, but only for firms willing to invest in productized deliverables, published pricing, and reporting. Firms that cannot make that investment are often better served by a disciplined co-managed motion in a single metro than by a half-executed vertical strategy.

Rollout plan

The transition from a generic managed IT motion to a verticalized outcome motion takes roughly three to four quarters for a mid-size firm. The sequence matters more than the speed.

Quarter 0: baseline. Before changing anything, measure gross margin by service line, recurring versus project mix, net revenue retention, technician-to-endpoint ratio, and CAC payback. Most firms discover their blended margin is propped up by one or two legacy accounts. Knowing this prevents the mistake of killing a line that is actually funding the transition.

Quarter 1: vertical selection and assessment design. Pick two or three verticals where the firm already has at least one referenceable client and where a compliance or risk driver creates urgency. Build a single assessment deliverable per vertical: a fixed-scope, fixed-price engagement that produces a written risk and roadmap document. Price it so it is easy to approve, and make it genuinely useful even if the client never buys managed services.

Quarter 1-2: service catalog. Publish a catalog with named tiers, included scope, exclusions, and a price per user or per asset. The catalog is the single most important artifact in this playbook because it removes the per-deal negotiation that destroys margin. Exclusions matter as much as inclusions; undefined scope is where margin dies.

Quarter 2: sales retraining. Move the sales conversation from "how many seats do you have" to "what happens to your business if this control fails." Train the team on the vertical's regulatory language, the assessment deliverable, and the roadmap handoff. Compensate on assessment bookings and multi-year recurring, not on one-time resale.

Quarter 2-3: account conversion. Take the top 20 accounts by revenue and run the new assessment for each, then present a roadmap that sequences remediation and expansion over 12-24 months. This is where net revenue retention is won or lost. Existing accounts are the cheapest expansion revenue available.

Quarter 3: instrumentation. Every outcome claim in a contract needs a data source. If the firm promises reduced downtime, it needs uptime reporting. If it promises compliance readiness, it needs control attestation. Build the reporting before the promise, not after.

Quarter 3-4: practice leadership. A vertical practice needs an owner, not a committee. Promote or hire someone accountable for the vertical's templates, references, pipeline, and delivery quality.

Quarter 4: review. Compare mix, margin, retention, and CAC payback against the baseline from Quarter 0. Expect the top line to look flat or slightly down in the first two quarters while the mix shifts. Gross profit per technician is the metric to watch, not revenue.

The most common failure mode is running this transition while still compensating sales on resale volume. If the comp plan does not change, the behavior will not change, and the firm ends the year with a new catalog and the same old revenue mix.

Related questions

How long before the new motion shows up in the numbers?

Expect two to three quarters of flat or slightly declining top-line revenue while the mix shifts, then gross profit per technician and net revenue retention improve. Firms that judge the transition on quarterly revenue alone usually abandon it too early.

Do we have to abandon break-fix and resale entirely?

No. Resale and break-fix can remain as attached services, but they should not be the led offer or the basis of the forecast. Treat them as convenience lines that support the managed relationship, not as revenue engines.

What if we only serve one vertical already?

That is an advantage. Deepen it before broadening. Build the second vertical only after the first produces repeatable assessments, published pricing, and at least three referenceable outcomes.

How do we price an outcome-based contract without losing money?

Model delivery cost from your own historical tickets and endpoint data, add a margin buffer for scope creep, and cap the outcome commitment to what your tooling can actually measure. Never commit to an outcome you cannot report on.

FAQ

Is verticalization mandatory, or can a horizontal MSP still grow in 2027? Horizontal MSPs can still grow, but growth comes from density and operational excellence rather than pricing power. Without a vertical or outcome differentiator, the firm competes on price against roll-ups and offshore delivery, which caps margin. Horizontal works if the firm is genuinely the best operator in its metro; it fails as a default strategy.

How many verticals should a mid-size firm pursue at once? Two or three is the practical ceiling for a firm under a few hundred staff. Each vertical needs its own assessment template, compliance language, reference architecture, and practice owner. More than three dilutes the investment and produces shallow expertise that buyers can detect.

What is the single most important artifact in this playbook? The published service catalog with fixed pricing and explicit exclusions. It converts every deal from a bespoke negotiation into a scope selection, which is what protects gross margin. Firms without a catalog reprice every deal from scratch and lose margin on each one.

Does outcome pricing mean we stop charging per seat? Not necessarily. Many firms run a hybrid: a per-user or per-asset base fee for coverage, plus an outcome-linked component tied to a measurable target such as uptime, patch compliance, or audit readiness. The hybrid keeps forecasting simple while capturing upside from automation.

How do we handle clients who only want the cheapest tier? Let them buy the cheapest tier, but make the exclusions explicit and put the upgrade path in writing. The catalog's job is to make the trade-off visible, not to force every buyer upmarket. Firms that hide exclusions win the deal and lose the margin.

What metric best indicates the transition is working? Gross profit per technician, tracked quarterly, alongside net revenue retention. Revenue can stay flat while both improve, which is exactly what a successful mix shift looks like in the first year. If gross profit per technician is not rising by quarter four, the motion has not actually changed.

Sources

• CompTIA Industry Outlook
• MSPAlliance
• Channel Futures
• CRN
• Gartner IT Services Research
• ConnectWise
• HBR: The B2B Elements of Value
• Bain: Net Promoter System

Related on PULSE

• [What pricing model should an MSP use in 2027?](/pricing-model-msp-2027)
• [How do you build a service catalog that protects margin?](/service-catalog-margin-protection)
• [What does net revenue retention look like for managed services?](/net-revenue-retention-managed-services)
• [How do you productize a security assessment for SMB clients?](/productize-security-assessment-smb)
• [When should an MSP verticalize its go-to-market?](/when-to-verticalize-msp-go-to-market)
• [How do roll-ups change MSP competitive dynamics?](/msp-roll-ups-competitive-dynamics)