Choosing the Core Tools That Run Your MSP Without Overbuying

Published by
Throne of Profit Editorial

Reviewed by
William Hassell
Founder & Chief Editor, Throne of Profit

Every MSP runs on a handful of platforms — the tool that monitors and patches endpoints, the one that ticketing and billing flow through, the layer that automates the repetitive work. Get these right and the shop runs smoothly on top of them. Get them wrong and you either fight the tools every day or pay every month for capability nobody touches. Most owners feel the second problem as a slow bleed: a stack that grew feature by feature until the invoice is large and the reasons are fuzzy. The goal of tool selection isn't buying the most capable platform — it's buying the one your team will actually run, at the depth you'll actually use.

The trap is that these platforms sell on breadth. Every demo shows a module you could grow into, and it's easy to buy the future you imagine instead of the operation you run. That future rarely arrives, and the unused half sits on the invoice as shelfware — paid for, provisioned, and ignored.

   WHAT YOU BUY  vs.  WHAT YOU USE

   RMM     ▇▇▇▇▇▇▇▇▇▇  bought
           ▇▇▇▇▇░░░░░  used  → 50% shelfware
   PSA     ▇▇▇▇▇▇▇▇▇▇  bought
           ▇▇▇▇▇▇▇▇░░  used  → close fit
   Add-ons ▇▇▇▇▇▇▇▇▇▇  bought
           ▇▇░░░░░░░░  used  → mostly shelf

Owner symptoms

• You're paying for platform tiers or modules your techs rarely, if ever, open.

• Tool decisions were made under a demo's spell or a deadline, not against how your shop actually works.

• Nobody can cleanly say which core platform owns which job — features overlap and duplicate.

Why this happens

Core MSP platforms are bought at high-pressure moments — a fast-growing client base, a migration, a renewal deadline — and sold on the widest possible feature set. Under that pressure it's natural to buy for the operation you hope to have rather than the one in front of you, and to say yes to bundled modules because unbundling them is work. Add a few years of "let's just add this" decisions and the stack becomes a layer nobody designed on purpose. Each tool arrived for a real reason; the collection was never chosen as a whole.

Common mistakes

• Buying breadth over fit — paying for a top tier when your team lives in the middle one.

• Confusing the demo with the daily job. A slick module means nothing if your workflow never reaches it.

• Overlapping tools — two platforms that both do scripting, or ticketing, so you pay twice and use neither fully.

• Never re-checking the fit. The stack you chose at ten seats is rarely the right one at forty.

• Chasing the all-in-one because one login sounds tidy, then using a fraction of it.

Business consequences

Overbought tooling costs twice: once in the monthly line item for capability you don't use, and again in the tax of running platforms your team resents or works around. Shelfware is the cleaner loss — real money for provisioned features nobody opens. The messier loss is a poor-fit core tool that adds friction to every ticket and every patch cycle, quietly slowing the whole shop. The owner who selects deliberately pays for the capability the team actually runs, gets tools people want to use, and keeps the stack coherent enough that adding a client doesn't mean adding another subscription. The difference isn't dramatic in any one month; over a year it's the gap between a lean operation and a bloated one.

How experienced operators think about it

They start from the work, not the catalog. The question isn't "what can this platform do?" — it's "what jobs does my shop need done, and what's the simplest set of tools that covers them without overlap?" They treat each core platform as owning a clear job and resist buying capability they can't name a use for this year. They read a demo skeptically, assuming most of the shine is future they won't reach. And they revisit fit on a schedule, because the right stack is a moving target that tracks the shop's size and the way it actually delivers — not the size they were promised they'd become.

Practical actions

1. List the core jobs first. Write down what your operation must do — monitor, patch, ticket, bill, automate — before you look at a single vendor.

2. Map each job to one owner. Assign each job to one platform so you can see overlap and gaps plainly, and stop paying for the same capability twice.

3. Buy the tier you use now. Choose the level that matches today's operation, not the one you might grow into; you can upgrade when the need is real.

4. Pressure-test every demo module. For each feature that sold you, name a specific job it does in your shop this year. If you can't, it's shelfware.

5. Set a fit review. Put a recurring date on the calendar to re-check whether each core tool still fits the size and shape of the shop.

Questions every owner should ask

• For each core platform, can I name the exact jobs it owns — and does anything else on the invoice overlap it?

• Am I paying for a tier or module my techs actually open, or for one that just sounded safer?

• When did I last check whether these tools still fit the shop I run today, not the one I bought them for?

Frequently asked questions

Is an all-in-one platform or a best-of-breed stack better for an MSP?
Neither wins in the abstract — it depends on what your team will actually run. All-in-one reduces logins and integration work but tempts you to pay for modules you'll never open. Best-of-breed lets you fit each job precisely but adds glue and management. Decide by the same test either way: does this cover the jobs you have, at a depth your team uses, without overlap you pay for twice? Buy for fit, not for the tidiness of one bill or the promise of one login.

How do I know if a tool is shelfware before I cut it?
Look at whether anyone actually uses it, not whether it's provisioned. For each platform tier or add-on, ask your techs to name the last time they used it and for what. Features nobody can tie to a recent, concrete job are shelfware regardless of how good they looked in the demo. Downgrade or drop them, keep an eye out for anything that breaks, and you'll usually find the answer is nothing did.

Related articles

• Running a Profitable Managed IT Services Business — the pillar.

• Getting Your Software Subscription Costs Under Control — the broader spend problem.

• Managing Your Vendors and Distributors So You're Not the Bottleneck — running the relationships behind the tools.

• Why Jobs Take Longer Than You Quoted — the general time-leak problem.

• Where Time Leaks on a Typical Job — where poor-fit tools quietly slow the work.

Every business has more decisions than time

Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.

Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.

Explore Throne of Profit