First page of Microsoft's 100,000-partner directory, sorted by responsiveness Microsoft Solutions Partner — Security, Modern Work, Infrastructure, App Innovation Microsoft partner since 2006 1,100+ organizations under management
Home/Blog/Why Our Prices Can Be This Low

Why Our Prices Can Be This Low

2026-08-30·IT PartnerNewPricingTransparency

You're looking at our quote and thinking: that can't be right. Fair. We'd think the same in your chair. Here is what's behind the number, and what isn't.

First, the subscription lines

If your quote includes Microsoft 365, Azure, or any other Microsoft subscription, those lines are Microsoft's own published prices. Not lower, not higher. We sell at Microsoft's list price, and every quote states which monthly Microsoft price list it was built from, so you can check it against Microsoft's site in a minute. Our margin on subscriptions comes from Microsoft, not from a markup on you.

So if the total looks too low, you're reacting to the services lines. The rest of this page is about those.

We have done this more than a thousand times

IT Partner started in 2006. We have been in the Microsoft cloud since its early days, about fifteen years now, and there was more than a decade of Microsoft server infrastructure before that: our founder, Mike Mackey, earned his first MCSE back in the Windows NT days, and his Microsoft certification transcript is public on Microsoft Learn. Since 2006 we have delivered more projects than we have ever formally counted. By a conservative estimate, well over a thousand: migrations, tenant consolidations, security rollouts, Intune deployments, Azure builds, and the support that follows them.

When you do something that many times, scale starts working in your favor, and in ours:

  • Experience. We have seen the edge cases, so you don't pay us to discover them.
  • Automation. The repetitive bulk of a migration runs from scripts we have refined for years.
  • Templates. Tenant baselines, Conditional Access policies, Intune configurations, runbooks. Written once, reviewed constantly, applied in hours instead of days.
  • AI, which compresses much of what's left. More on that below.

The tenth Exchange migration takes a fraction of the time the first one did. The hundredth takes a fraction of the tenth. Not because anyone rushes, but because the unknowns are known.

We use AI. A lot.

We won't pretend otherwise. AI drafts our runbooks and documentation, writes and checks scripts, reads logs, summarizes the state of a tenant before an engineer touches it, and keeps us current on what Microsoft changed this month. It works like a very fast junior colleague.

It is supervised like one, too. Nothing AI produces reaches your tenant until a senior engineer has read it. Every order is closed by a human, and our AI-facing tools identify themselves as AI.

The practical effect: work that used to be billable hours (typing, searching, formatting, first drafts) mostly isn't anymore, and we pass that on. This website is one example. It was rebuilt by one person working with AI over a handful of working days spread across four months.

The cloud changed the math

Here is what people who priced IT projects a decade ago sometimes miss: the labor is no longer in the doing. With the right knowledge, a few lines of code spin up a thousand correctly configured virtual machines across several regions. A fully scripted Azure Virtual Desktop deployment takes us about fifteen minutes.

Compare that with how it used to go. Plan every detail up front. Size and order hardware. Wait for it. Rack it, install it, patch it, test it. Then find out the requirements changed. Weeks of labor that simply don't exist anymore. What you pay for now is knowing exactly what to type, and, just as important, what not to.

And it keeps getting easier

Microsoft ships improvements monthly and, in some services, daily. Provisioning a laptop used to mean imaging it by hand; now it's Windows Autopilot and a box shipped straight to the employee. Identity, endpoint management, migration tooling, security baselines: every year the same outcome takes less engineering time to reach. We price today's effort. If a quote you're comparing ours with was built on how long this took in 2015, that is probably where the gap is.

A few more reasons the number is what it is

  • Fixed price, pay after you approve. Project work is quoted in writing before work begins, and you pay after you approve delivery. We can price this way because we have seen the surprises; we don't pad every quote for unknowns.
  • No sales department, and no sales bonuses. Our founder takes the calls himself, and the people who handle sales work for us are on salary. More to the point, nobody here earns a sales bonus or a commission. There is no one whose pay goes up when your quote does, so there is no one with a reason to pad it, upsell it, or rush you into it.
  • No offices. We have been a fully virtual company since COVID, with the team spread across the US and Europe.
  • We play the long game. Microsoft pays us a partner margin on the subscriptions we manage for clients, and clients tend to stay for years. A project doesn't have to carry our year. It has to start a relationship worth keeping.

What "low" does not mean

The number didn't get low by cutting these:

Don't take our word for it

Every claim we make about ourselves lives in a public facts register, with evidence, step-by-step checks, and a plain list of what we can't prove. If you'd rather have your AI assistant run the background check, there's a prompt ready for it. Our monthly support statistics, including the months we missed our own SLA, are public too.

And if you're reading this thinking the price is actually too high, we wrote that one as well: Why our prices are not the lowest you'll find.

Questions about your quote? Book 30 minutes with Mike →

Questions this article didn’t answer?

Thirty minutes with Mike — our CEO, not a sales rep. Bring the hard version of the question.