Pricing

How our pricing works

You should not have to book a call to understand how you would be charged. Here is the whole structure. The number itself depends on your environment, which is what the first conversation establishes.

How it is calculated

Three pricing bases, and when each one applies

There is no single model that fits every environment. Which one we use depends on what actually drives the work in your business.

Per user

Most often used for fully managed IT, where the work follows people rather than machines.

One monthly figure for each person supported, covering their support, accounts, and the shared systems behind them. It is the easiest basis to budget and the easiest to scale as you hire.

Per device

Used where the count of machines drives the work: shared workstations, shift patterns, servers, or heavy on-site equipment.

A monthly figure per supported device. This suits environments where several people share a machine, or where servers and specialist equipment carry most of the maintenance load.

Custom scope

Used for co-managed arrangements, multi-site organizations, and environments with specialist or regulated systems.

The scope is written first, which systems, which hours, which responsibilities, and priced against that. This is the honest answer when neither a user count nor a device count reflects the actual work.

Generally included

  • Day-to-day support for your people
  • Monitoring, updates, and preventive maintenance
  • Core security controls and monitoring
  • Backup management and recovery testing
  • Account onboarding and offboarding
  • Regular reporting and planning reviews

What moves the price

  • How many people and devices you have
  • How many sites, and how much of the work needs to be onsite
  • The condition of what you have today, and how much stabilising it needs
  • Coverage hours, and whether out-of-hours response is required
  • Regulatory or compliance requirements
  • Any specialist systems that need particular expertise

Compare engagement models

Why co-managed is priced differently

Buying an outcome and buying capacity are not the same purchase, so they are not costed the same way.

Fully managed IT

Priced per user or per device, covering the whole environment. You are buying an outcome, everything works, someone owns it, so the fee reflects total responsibility.

Co-managed IT

Priced against the written responsibility split rather than a headcount. You are buying specific capacity, overflow, coverage hours, or a workstream, so the fee reflects what you handed over, not the size of your organization.

How co-managed works

Terms

Projects, supply, onboarding, and commitment

Recurring service vs projects
Ongoing support is a recurring monthly fee. Project work, migrations, office moves, replatforming, is scoped and quoted separately, so a project never arrives inside a monthly invoice unannounced.
Hardware, licences, and cloud
These stay yours. They are billed by the vendor or passed through at cost, shown separately from the service fee, so you can always see what is service and what is supply.
Onboarding
Any transition or onboarding work is quoted in writing before you commit, with the scope attached. You will not be told about it after signing.
Contract and commitment
Term, notice period, and exit arrangements are set out in the written agreement before you sign, and we will walk you through them rather than leaving them in a schedule at the back.
How you get an estimate
One conversation to understand the environment, then a written quote with the scope attached to it. No obligation attached to either.

Related questions

While you are here

Amplaphi is new. Why should we trust you with our IT?
It is a fair question and we would rather answer it directly. The Amplaphi name is new, but the founders are not. Two of us were part of a 2003-founded MSP through its sale in 2018, another was running a smaller MSP that merged in, and the fourth has spent years running IT environments. What we can offer that a larger provider often cannot is that the founders are the people in your account. Judge us on the assessment we give you before you commit to anything.
Can you work alongside our internal IT team?
Yes, and it is one of the two ways we usually work. In a co-managed arrangement your team keeps ownership and we add capacity around them, overflow tickets, coverage hours they do not staff, projects, and specialist work. We write down who handles what so nothing falls between us.
What actually happens when we switch providers?
We move in a controlled order: access and documentation first, then monitoring and support, then anything that needs a maintenance window. Your existing arrangement stays in place until the new one is proven, and work that could interrupt your day is scheduled outside business hours. You get a written handover of every system.
How quickly do you respond?
Response targets are agreed in writing before onboarding, set against how much each system matters to you rather than as a single blanket number, and reported against so you can see whether we are meeting them.
What happens if the engineer who knows us is unavailable?
Your environment is documented during onboarding and kept current, and more than one engineer is familiar with your account before support goes live. Every request has an owner, and escalation ends with a founder rather than with a queue.
How does pricing work?
The structure is published on this site rather than held back for a sales call: we price per user, per device, or against a custom scope depending on your environment, and the page explains which applies when and what moves the number.

Want the number for your environment?

One conversation to understand what you have, then a written quote with the scope attached to it.

Let's talk(817) 435-9009