Field GuideUnofficial · enterprise field edition
Menu

Know where they beat you.

6 competitors, each with an honest loss column. A card that cannot name where the other product is better is marketing, and a technical buyer will read it that way in about four seconds.

How to use these

Position on fit, never on their engineering

Every “where we win” below is about fit, workflow, or operating model. None of them claim the other vendor builds bad software, because that argument cannot be won in front of a customer who already owns the thing and chose it deliberately.

Each card carries a trap question — the one that exposes the seam without you having to narrate it. Let the customer find the gap. A gap they describe themselves is a requirement; a gap you point at is a sales pitch.

6 of 6 shown

Microsoft Intune

Platform-bundled

Already paid for inside an M365 E3/E5 agreement. Almost never a displacement fight — the realistic outcome is coexistence, and pretending otherwise costs you the room.

You hear: "We already have Intune, it comes with our licensing."

Where they genuinely win

  • Cost, as the customer sees itIt is bundled. Any comparison that starts from per-endpoint price loses before it begins, so do not start there.
  • Windows and Entra ID depthConditional Access, compliance policies tied to identity, Autopilot provisioning. If the estate is Windows and cloud-joined, this is genuinely strong and saying otherwise makes you look uninformed.
  • Single-vendor consolidation storySecurity teams standardising on Microsoft have a real architectural reason to prefer it, and that reason is not wrong.

Where we win

  • Third-party patching without a bolt-onIntune's third-party application patching typically requires an additional product or a packaging pipeline somebody maintains. Ask who owns that pipeline today and what happens when they are on holiday.
    Verified sourcesNinjaOne Autonomous Patch Management ↗
  • Cross-platform servers and LinuxIntune is an endpoint-management tool, not a server-operations tool. If they run Linux or a meaningful server estate, that work is happening somewhere else today — usually in scripts.
    Verified sourcesNinjaOne policies: types, inheritance, and assignment ↗
  • Support workflow with real device contextRemote support, background action, and a ticket carrying device state is a different job from configuration management. Intune configures; it does not run a service desk.
    Verified sourcesNinjaOne Remote product guide ↗NinjaOne Ticketing ↗
  • One asset record that agrees with realityIntune knows about enrolled devices. It cannot see what it does not manage, which is exactly the population that shows up in an audit.
    Verified sourcesNinjaOne IT Asset Management ↗

The question that exposes the seam

“Outside Intune, what still runs on a script, a spreadsheet, or a second console?”

Listen for: Any hesitation names the gap for you. If the honest answer is 'nothing', they are a mature Microsoft shop and you should say so rather than manufacturing a problem.

Landmines

  • "Intune can't really do endpoint management." It does a great deal well, the room knows it, and the overclaim ends your credibility on everything else in the meeting.
  • Leading with price. It is bundled. You cannot win an argument about the cost of something they already own.
  • Proposing displacement in the first meeting. You are asking them to abandon a sunk investment before you have earned the right.

When to say they are the right fit

A Windows-only, cloud-joined, Autopilot-provisioned estate with no server footprint and no third-party patching pain is genuinely well served by Intune. Say that plainly. You will be remembered for it when their estate changes.

ConnectWise

MSP incumbent

Deeply embedded in how the MSP runs its business, not just its technology. The PSA is usually the real switching cost, and it is a business-continuity risk to touch it.

You hear: "We're a ConnectWise shop — everything runs through it."

Where they genuinely win

  • PSA depth and ecosystemContracts, agreements, procurement, accounting integrations. A long tail of workflow that a technical comparison never captures and that the owner feels every day.
  • Switching cost as a moatYears of ticket history, billing configuration, and staff muscle memory. That is not inertia, it is a genuine risk calculation.
  • Partner community and available skillsTechnicians arrive already knowing it. For an MSP onboarding staff constantly, that is a real operational advantage.

Where we win

  • Attack the reconciliation seam, not the PSAThe question is not which PSA wins. It is where device counts, ticket time and contract terms reconcile today, and who does that by hand every month.
  • Technician time-to-productivityConsole complexity has a training cost that shows up in every new hire. Ask how long before a new tech is billable.
  • Agent consolidationA stack assembled over a decade usually has four or more agents on every endpoint. Count them on ten machines and the list makes the argument.
    Verified sourcesNinjaOne Endpoint Management ↗

The question that exposes the seam

“How long does month-end billing take, and who does it?”

Listen for: A named person and a number of days is the business case, in their numbers, before you show a single screen. Multiply by their loaded rate.

Landmines

  • "You should consolidate onto our PSA." You have just proposed a business-threatening migration in the first meeting.
  • Criticising their stack. They built it. The person defending it is often your strongest potential champion.
  • Assuming they want to replace the PSA. Most want the manual reconciliation fixed, not a migration.

When to say they are the right fit

An MSP mid-way through a ConnectWise implementation, or one whose entire billing model depends on a deep customisation, should not be switching. Come back at renewal with the seam quantified.

Datto

MSP incumbent

BCDR-first. The backup appliance is usually the anchor and the RMM came along with it, which means the competitive centre of gravity is data protection rather than endpoint management.

You hear: "Our backup is Datto, and we picked up the RMM with it."

Where they genuinely win

  • BCDR maturity and the appliance modelLocal appliance plus cloud, with instant virtualisation. For an MSP selling recovery guarantees this is a proven, well-understood story.
  • Recovery time on a failed serverSpinning up a failed server on the local appliance is a genuinely strong capability and customers who have used it in anger trust it.

Where we win

The question that exposes the seam

“Walk me through the last time you restored Microsoft 365 data, not a server.”

Listen for: Appliance-anchored shops are strong on servers and frequently have never tested a SaaS restore. The silence is the finding.

Landmines

  • Competing on BCDR head-on. It is their strongest ground and you do not need to win it to win the deal.
  • Suggesting they rip out an appliance they have already depreciated.

When to say they are the right fit

If the entire relationship is a recovery-guarantee product built on their appliance, endpoint management is not the wedge you think it is. Note it and move on.

Kaseya

MSP incumbent

Broad portfolio assembled through acquisition. Competitive conversations tend to be about integration quality and commercial experience rather than any single capability.

You hear: "We're on the Kaseya stack" — often said with a specific tone. Listen to the tone.

Where they genuinely win

  • Breadth under one commercial relationshipOne vendor, one contract, wide functional coverage. For a buyer optimising vendor count that is a real benefit.
  • Bundled pricing at scaleAggressive commercial packaging when several products are taken together.

Where we win

  • Integration coherence between modulesAcquired portfolios integrate at different depths. Ask them to trace one workflow end to end across two modules and watch where it hands off to a person.
  • Console consistencyDifferent products with different interaction models cost technician time every day, and that cost is invisible until somebody measures it.

The question that exposes the seam

“Pick two modules you own and walk me through a workflow that crosses both.”

Listen for: Where the workflow becomes manual is the seam. Let them find it — narrating it for them sounds like an attack.

Landmines

  • Repeating industry gossip or security history. It is unprofessional, it is legally risky, and a buyer who brought it up themselves will respect you more for not piling on.
  • Assuming dissatisfaction. Plenty of Kaseya shops are perfectly happy, and assuming otherwise is a fast way to look like you did no homework.

When to say they are the right fit

A shop deep into a multi-product agreement with years remaining is a renewal-cycle conversation. Get the date, leave value behind, and come back.

SCCM / Microsoft Configuration Manager

Enterprise legacy

Enterprise incumbent with deep expertise around it. Rarely displaced outright — the realistic play is the population it serves badly, which is remote and non-Windows.

You hear: "We use Config Manager for everything on-prem."

Where they genuinely win

  • Domain-joined Windows depthApplication packaging, task sequences, OS deployment, granular targeting. Inside the domain it is extremely capable and the team running it is usually excellent.
  • Sunk expertisePeople have built careers on it. That knowledge is real value and dismissing it insults the person who will decide.
  • Bandwidth-aware content distributionDistribution points and peer caching solve a genuine problem at scale.

Where we win

  • Devices that rarely touch the networkThe model assumes reachability. A laptop that has not been on the corporate network in three weeks is the gap, and hybrid work made that population much larger than the org chart suggests.
    Verified sourcesNinjaRMM firewall allow list (partner mirror of the NinjaOne global allowlist) ↗mirror

    Not an official source: NinjaOne's canonical allowlist article (ninjarmm.zendesk.com/hc/articles/211406886) requires an authenticated support account and returns HTTP 403 to anonymous requests, so it could not be cited directly. This is a partner's published mirror of that list. Treat the hostnames as a starting point and re-verify inside your own tenant before handing them to a network team.

  • macOS and LinuxWhatever covers those platforms today is almost certainly a separate tool or a pile of scripts.
    Verified sourcesNinjaOne policies: types, inheritance, and assignment ↗
  • Infrastructure to run the management toolSite servers, distribution points, SQL, and the patching of all of it. Cloud control plane removes a maintenance burden that has its own change windows.

The question that exposes the seam

“What is your compliance number for devices that have not been on the corporate network in 30 days, separately from your domain-joined number?”

Listen for: Most cannot separate the two, and the blended figure hides the problem. If they can produce both and the gap is small, they are running it well — say so.

Landmines

  • "SCCM is legacy." People who have run it well for a decade will stop listening, and they are right to.
  • Proposing wholesale replacement. Co-existence targeting the remote and non-Windows population is credible; displacement is not.

When to say they are the right fit

A fully domain-joined estate with staff on site and no macOS or Linux is well served. There is no honest wedge and inventing one will be obvious.

Atera

Direct RMM

Per-technician pricing rather than per-endpoint. Attractive to small teams managing many devices, and the pricing model itself is the competitive dynamic.

You hear: "We pay per tech, not per device."

Where they genuinely win

  • Per-technician economics at high device countsA small team managing a large estate genuinely pays less. Do not argue with their arithmetic — it is correct.
  • Simplicity and time to valueFast to stand up, little to configure. For a team without a platform owner that is a real advantage.

Where we win

The question that exposes the seam

“As the team grows, how do you stop one technician changing something outside their scope?”

Listen for: Per-technician pricing quietly encourages broad access. If the answer is 'everyone can do everything', that is a governance finding worth naming plainly and without judgement.

Landmines

  • Attacking the pricing model. Their maths is right for their shape, and telling a buyer their own economics are wrong does not work.
  • Dismissing simplicity as a weakness. For a two-person team it is the entire value proposition.

When to say they are the right fit

A small team, a flat estate, no delegation requirement, no audit pressure. They are correctly served and will know if you pretend otherwise.