TL;DR

Syncro pricing is per technician with endpoints unlimited and no per-device fees, which is the opposite basis from most tools an internal IT team compares it against. Built for managed service providers, it can be unusually good value for an in-house team with a small number of admins and a lot of machines.

  • Per technician. Endpoints are unlimited and free.
  • Two published plans, each with an annual and monthly rate.
  • Great when few admins manage many devices.
  • Poor when you have many part-time admins.
  • The $6,444 figure is a worked example, not a plan.
  • Built for MSPs, so some of it is not for you.

Per technician, endpoints unlimited

The page states it plainly: per-technician pricing, unlimited endpoints, no per-device fees.

Two plans publish a price, per user per month. Core is $129 annual, $159 monthly. Team is $179 annual, $209 monthly. The page states a saving of 19 per cent for annual.

User here means a technician seat, not an employee whose laptop you manage. That distinction is the whole article.

So a company with 400 devices and two admins pays for two seats. A company with 40 devices and two admins pays exactly the same. The bill tracks your team, not your estate.

The figure to read carefully

The page carries $6,444 per year, described as three technicians on the annual Team Plan, all-in. That is a worked example rather than a plan price, and the arithmetic checks out at three seats times $179 times twelve months.

When this basis wins

Three shapes, and the first is common in companies that never considered an MSP tool.

Few admins, many machines. A two person IT team supporting several hundred endpoints. Every per-device tool scales with the fleet; this one does not.

A fleet that grows faster than the team. Hiring fifty people usually adds fifty devices and no admins, so your bill is flat while a per-device bill rises.

Seasonal or contractor-heavy estates. Devices appear and disappear without changing the seat count.

Run the comparison with your real numbers. Against a per-device tool, the crossover point is simply where device count times the per-device rate exceeds seat count times the seat rate, and for a small admin team that point arrives earlier than people expect.

When it loses

Equally plain, because the basis is not universally favourable.

Many part-time admins. If support is spread across eight people who each do a little, you are paying eight seats for less than two people’s work. Per-device pricing would be cheaper.

A small estate. Forty devices and three admins is an expensive way to buy management, since the unlimited endpoints are not doing anything for you.

Occasional access for non-IT staff. Anybody who needs to log in counts, which catches teams that wanted a manager to see a dashboard.

The question to settle before pricing is how many people genuinely need a seat, and the honest answer is often fewer than the list you were given.

Your shape Per technician
2 admins, 400 devices Strongly favourable
2 admins, 40 devices Poor value
8 part-time admins Expensive
Fleet growing, team static Improves over time

It is built for MSPs and that shows

Worth saying so you know what you are buying into.

The product is aimed at managed service providers, and the pricing page is organised around them. There is a separate IT Teams route at the Team rate, which is the one an internal department would take.

The practical consequence is that a share of the product assumes multiple client organisations: billing, invoicing, client separation, margin reporting. None of that is useful in house, and you are paying for a product that carries it.

Whether that matters depends on whether the parts you do want are strong enough. Remote access, patching, scripting, alerting and ticketing are the ones an internal team would actually use.

endpoint management software covers how the category splits between MSP tools and in-house tools, which is a more useful frame than feature lists.

What sits outside the seat price

The page publishes one add-on and implies others are quoted.

A Microsoft 365 backup capability is listed at $1.90 per user per month, covering granular recovery, unlimited storage and regional data residency across the US, Canada, UK and Australia. Note the unit changes: that one is per user in the ordinary sense, not per technician.

That shift is easy to miss and it matters. A seat-priced platform with a per-employee add-on behaves like two different pricing models on one invoice, and a 200 person company adding that line is adding a cost that scales with headcount rather than with the admin team.

Model add-ons separately from seats for exactly that reason, and check the unit on each one rather than assuming it matches the platform.

What no RMM covers

Three, and they are the recurring theme across every tool in this comparison.

Remote management reaches a device that is online and enrolled. It does not procure hardware, ship it across a border, or handle the import paperwork, and those are the costs that arrive unplanned in a quarter with heavy hiring.

It cannot physically recover anything. A leaver with a laptop at home is a logistics problem, not a scripting one, and RemoAsset’s laptop retrieval is the counterpart at 25+ countries.

It does not store or dispose of hardware, so the gap between one employee leaving and the next starting is somebody’s problem and usually a cupboard. the EPA on electronics and batteries management is the reference on handling at end of life.

CISA’s known exploited vulnerabilities catalogue is worth pairing with the patching side, since an RMM is only as useful as the cadence you actually commit to running.

Working out your own number

Four steps, all doable before a demo.

Count seats honestly. Only people who will log in. Write the names down; the list is usually shorter than the one you were handed.

Count endpoints, because you need it for every competing quote even though Syncro does not charge for it.

Price both bases. Seats times the seat rate against devices times a per-device rate from a competing tool. The answer is often not close, in one direction or the other.

Add the add-ons at their own unit, rather than folding them into the seat figure.

the NIST Cybersecurity Framework is a reasonable way to check you have covered the whole picture rather than just the tool, since management, identity and physical custody are separate problems and only one of them is on this invoice.

The question to ask on the call

Whether a seat can be shared or reassigned, and on what notice.

Per-technician pricing is sensitive to staff turnover in a way per-device pricing is not. If somebody leaves halfway through an annual term, the question of whether that seat can be handed to their replacement, or sits paid and empty, is worth more than a few percent on the rate.

Ask it before signing rather than discovering the answer in month seven. The same applies to adding a seat mid-term, where the proration terms vary and are rarely on the pricing page.

The sanity check

If the per-technician total looks too good, count the seats again. That is almost always where the optimism is hiding, usually in the form of somebody who was not on the list and turns out to need access on day one. Two extra seats changes the comparison more than any discount you will negotiate.

Unlimited endpoints still have to arrive and come back. RemoAsset handles that in 80+ countries. See RemoAsset’s laptop lifecycle management or RemoAsset’s pricing.

Frequently asked questions

How does syncro pricing work?

Per technician, with unlimited endpoints and no per-device fees. Two plans publish a price per user per month: Core at $129 annual and $159 monthly, Team at $179 annual and $209 monthly, with a stated saving of 19 per cent for annual. User means a technician seat rather than an employee whose laptop you manage, so a company with 400 devices and two admins pays for two seats.

Is the $6,444 figure a plan price?

No. It is a worked example the page gives for three technicians on the annual Team Plan, described as all-in, and the arithmetic checks out at three seats times $179 times twelve months. Treat it as an illustration rather than a tier. The 19 per cent is a discount claim for annual billing rather than a price in its own right.

When does per-technician pricing win?

Three shapes. Few admins and many machines, such as a two person team supporting several hundred endpoints, since every per-device tool scales with the fleet and this one does not. A fleet growing faster than the team, because hiring fifty people adds fifty devices and no admins. And seasonal or contractor-heavy estates, where devices appear and disappear without changing the seat count.

When does it lose?

Three cases. Many part-time admins, where support spread across eight people means paying eight seats for less than two people’s work. A small estate, where forty devices and three admins is expensive because the unlimited endpoints are doing nothing for you. And occasional access for non-IT staff, since anybody who logs in counts, which catches teams wanting a manager to see a dashboard.

Does it matter that it is built for MSPs?

It shows, and it is worth knowing what you are buying into. The pricing page is organised around service providers, with a separate IT Teams route at the Team rate for internal departments. A share of the product assumes multiple client organisations, covering billing, invoicing, client separation and margin reporting, none of which is useful in house. Judge it on remote access, patching, scripting, alerting and ticketing.

What sits outside the seat price?

The page publishes a Microsoft 365 backup capability at $1.90 per user per month, covering granular recovery, unlimited storage and regional data residency across the US, Canada, UK and Australia. Note the unit changes: that one is per user in the ordinary sense rather than per technician, so a 200 person company adding it adds a cost that scales with headcount. Check the unit on every add-on.

What does an RMM not cover?

Three things, and they recur across every tool in this category. It reaches a device that is online and enrolled, so it does not procure hardware, ship it across a border or handle import paperwork. It cannot physically recover anything, since a leaver with a laptop at home is a logistics problem rather than a scripting one. And it does not store or dispose of hardware at end of life.