IT that quietly works, so your team can get on with theirs.

Responsive support, stronger security, and a clear technology plan, from a small team of engineers who take the time to learn how your business actually runs.

Built by founders who have run MSPs and IT operations for more than two decades. You will be talking to the people who did the work.

An Amplaphi engineer sitting with a client, working through something together on a laptop

Sound familiar?

Most of the cost of bad IT never appears on an invoice

It shows up as waiting, as workarounds, and as the quiet assumption that this is just how technology is.

Your team waits too long for help

Someone submits a ticket and then just works around the problem because the current provider still hasn’t resolved it. The cost never shows up on an invoice, but you feel it every day.

The same issues keep coming back

Each one gets fixed. None of them get solved. No one has been given the time to ask why it keeps happening.

Security responsibilities feel unclear

You assume it is handled. You are not certain who is handling it, or what would happen on a bad day.

IT costs are hard to predict

The monthly number moves, projects arrive unannounced, and it is difficult to explain the total to anyone else.

None of this is unusual, and none of it is your fault. It is what happens when IT is treated as a series of emergencies instead of something someone owns.

Two ways to work with us

Which of these sounds like you?

The answer changes what we do and what stays with you. Pick the one that fits and we will show you exactly where the line sits.

You do not have an internal IT department, or the one person doing it has other responsibilities. We become the team.

What this fixes

  • Nobody owns IT day to day
  • Support depends on whoever is available
  • Security and updates happen when someone remembers
  • No plan beyond the current year

What we take on

  • Help desk and day-to-day user support
  • Monitoring, updates, and preventive maintenance
  • Security controls, monitoring, and response
  • Backup, recovery testing, and documentation
  • Vendor coordination and technology planning

What stays with you

  • Final say on spend and priorities
  • Business decisions and timing
  • Your own policies and culture
A planning conversation between Amplaphi and a client leadership team

Why Amplaphi

New name. Twenty years of doing the work.

Amplaphi was started by four people who have spent most of their careers inside MSPs and IT operations. Two of them were part of a legacy MSP founded in 2003 and sold in 2018. Another was running a smaller MSP that merged into the same picture. The fourth has spent years running IT environments for organizations that needed them to work without drama.

The company is new. The work is not. Between us we have seen what happens when providers grow too fast, inherit too many accounts, and stop being the people who actually touch the equipment. We built Amplaphi to keep the standards and lose the baggage.

More about how we work

You talk to people who know your setup

The same small group of engineers works your account. You are not re-explaining your environment to whoever picks up the phone.

We fix causes, not just tickets

Recurring problems get investigated properly. A ticket that keeps returning is treated as a fault in the environment, not as normal.

We tell you what things cost and why

How pricing works is published on this site. You should not have to book a call to find out how you would be charged.

Switching providers

What the first few months actually look like

Changing IT providers is the part everyone dreads. Here is each phase, what we need from you, and how disruptive it is, including the parts that are not.

Understand

Step 01 of 4

We go through what you have, what is breaking, and what the business is trying to do. We talk to the people who actually use the systems, not just whoever manages them.

What we need from you
Access to your current setup, time with a few key people, and an honest account of what frustrates you.
What you get
A written summary of what we found, including anything we think you should know before deciding to work with us.

Disruption to your business

None. Nothing changes during this phase, we are looking, not touching.

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.

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

How it is calculated

  • Per userMost often used for fully managed IT, where the work follows people rather than machines.
  • Per deviceUsed where the count of machines drives the work: shared workstations, shift patterns, servers, or heavy on-site equipment.
  • Custom scopeUsed for co-managed arrangements, multi-site organizations, and environments with specialist or regulated systems.
View pricing

Straight answers

The questions people actually ask us

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.

Start with a conversation, not a pitch

Tell us what is not working. We will tell you honestly whether we are the right people to fix it.