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.
That is why you are not talking to an account manager. You are talking to the engineers who will be in your environment, and they answer for the work themselves.
How we work
Three things we hold ourselves to
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.
What you can expect from us
The commitments we make before you sign anything
- Direct accountability
- One named owner for your account, and an escalation path that ends with a founder rather than with a queue.
- Senior people on the actual work
- The engineers who assess your environment are the engineers who run it. Nothing is handed down to whoever is free.
- Honest communication, including bad news
- If we caused a problem, we say so. If something is outside what we should be taking on, we say that too, before you commit.
- Everything written down
- Scope, coverage hours, response targets, and who owns what are agreed in writing before onboarding, not discovered during an incident.
Operating with confidence
The questions a careful buyer asks a smaller provider
Working with a boutique team should mean better access, not thinner cover. Here is how that actually holds up.
Who responds if the engineer who knows us is unavailable?
Your environment is documented as part of onboarding and kept current, and more than one engineer is familiar with your account before support goes live. Cover is a documentation discipline, not a person being reachable.
How does escalation work?
Every request has an owner. If it is not moving, it escalates to a founder, there is no tier of the organization above us that you cannot reach.
What about work outside business hours?
Coverage hours and out-of-hours arrangements are written into your scope before you sign, along with what constitutes an emergency and how it is raised. We would rather set a commitment we keep than advertise one we cannot.
How do you decide you have capacity for a new client?
We onboard deliberately, and we will tell you if the timing does not work rather than take the engagement and stretch. Turning down or delaying work is a normal part of running this properly.
What happens to our environment if we leave?
Documentation, credentials, and configuration are yours. We hand them over in a usable form. Nothing about the way we work is designed to make leaving difficult.
How is our data and access protected on your side?
Access to your systems is limited to the engineers on your account, protected by multi-factor authentication, and reviewed. Our insurance position and security practices are documented and shared during procurement.
Do you work with our existing vendors?
Yes. Most environments include software and telecoms suppliers who are not going anywhere. We coordinate with them and hold them to what they committed to, rather than insisting everything moves to us.
Before you get in touch
Exactly what happens when you contact us
No mystery, no discovery-call theatre. This is the whole process.
- What we cover
- What is not working now, what it is costing you, and whether we are the right fit. If we are not, we will say so.
- What to prepare
- Nothing. Bring the frustrations. Details about your setup are useful but can wait.
- What happens after
- If it makes sense to continue, we propose an assessment. If it does not, that is the end of it.
- Will you be added to a sales sequence?
- No. We follow up once. If you are not interested, we leave you alone.
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.