Stop Leaving Money on the Table: Pricing, Packaging & Profitability for MSPs

Presenters:
Vlad Marchenko
Michael Assraf
Thursday 14 May
20:00
8:00 PM · 59m
America/New_York

MSPs love saying they want to grow. But most price like they're scared of their own invoice.You discount too early. You package too vaguely. You sell support instead of outcomes. Then every new client feels like a margin hostage situation, and you wonder why.Kyle Christensen, Co-Founder of Empath, is dropping into the OpenMSP community to break it down.What we're covering: Why most MSP pricing problems are actually positioning problems How weak packaging creates scope creep before the deal is even signed Why your stack matters way less than you think How to stop selling a pile of services and start selling clear business outcomes (the kind that are easy to sell, and easy to sell a lot of) This isn't theory. It's the stuff that shows up on your P&L, your service desk, your sales calls, and your sanity.If you're tired of being busy, growing, and somehow still wondering where the money went, come hang out. Worst case, you walk away with one pricing tweak that pays for the next year of your stack.

BEST PRACTICESBUSINESSMSPMSP BUSINESSMSP STRATEGYPRICING
Stop Leaving Money on the Table: Pricing, Packaging & Profitability for MSPs
Past Event

Related Content

Webinars

Podcasts

Case Studies

Events

Blog Posts

Onboarding Guides

Frequently Asked Questions

MSPs use AI to triage and route tickets, cut alert noise, schedule patches, assist L1 security work, and draft client reports. Kaseya's 2025 benchmark found 30% already use it to eliminate tedious tasks, with ticket triage the most common starting point.
Most MSPs start with AI features inside their existing PSA, RMM, and ticketing systems rather than standalone products. Common categories include AI ticket triage, alert correlation, scripting assistants, and AI-native all-in-one platforms like OpenFrame that run intelligence across the whole stack.
Start with a readiness assessment, not a tool purchase. Confirm your ticket history is clean and your RMM, PSA, and monitoring systems connect. Then pick one high-volume, low-risk workflow, usually ticket triage, and pilot it on internal tickets before any client sees it.
Automate high-volume, low-risk tasks first. Ticket triage and alert noise reduction top the list because they run constantly and a human still resolves the underlying issue. Save security approvals, billing changes, and client-facing actions for later, always with a human in the loop.
Auto-remediation means the platform executes known fixes itself, like restarting hung services, clearing temp files, or retrying failed backups, then logs and documents the action. It typically covers the predictable majority of level-one infrastructure issues while escalating anything requiring judgment.
No. AI absorbs queue triage and repetitive fixes, but novel failures, judgment calls like production failovers, and client communication stay human. Technicians shift from clearing alert queues to reviewing exceptions, project work, and higher-value client engineering.
Start with telemetry hygiene: full agent coverage, consistent naming, centralized metrics. Then run predictive monitoring alongside existing thresholds until the team trusts it, and add auto-remediation for your most common ticket types. Expect the labor savings to land within a few months, not weeks.
Published industry data shows automated analysis and remediation cutting resolution times 40-60%, MTTR dropping 60% or more in strong first-year deployments, and predictive maintenance lifting uptime 10-20%. Results depend heavily on telemetry quality and how many remediation runbooks you automate.
It can be, with governance. Keep a human in the loop on high-risk actions, log every automated step for audit, and choose platforms that keep your data yours with no vendor lock-in. Pilot on internal data first so you catch issues before client systems are involved.
Set a baseline before rollout, then track tickets closed per technician, mean time to resolution, percentage of tickets resolved with no human touch, technician hours reclaimed, and cost per ticket. AI-driven automation commonly cuts operational cost per ticket by 25 to 40%.