How the M365 consulting market actually splits
If you sat through a Microsoft partner sales call recently, you've seen the shape. The big system integrators — Accenture, Avanade, Microsoft Consulting Services — staff their M365 practices to deliver multi-month, multi-team rollouts for the largest enterprises. The minimum engagement size is six figures because the cost structure demands it: solution architects, change managers, training leads, governance consultants, premium support tiers. That's what F500 buyers expect and what F500 deal shapes can absorb.
On the other end, Microsoft Learn and YouTube tutorials cover the small-business case. A 15-person firm with a tenant admin who's also the IT director can read the docs, follow the wizards, and stand up SharePoint sites, Teams channels, Power Automate flows. The community is generous. The footguns are real but survivable.
In between sits the 50–500 employee mid-market business. Big enough that DIY is no longer responsible — somebody is going to misconfigure conditional access and lock everyone out, or build a Power App that runs against an under-licensed data source. Too small to write a $300k check for an Accenture engagement when what they actually need is two senior engineers for eight weeks.
What mid-market M365 buyers actually need
The shape of the work, in our experience:
- Scoped, fixed-fee engagements. Not time-and-materials with a six-month minimum. A defined deliverable, a defined fee, a defined date
- Senior practitioners doing the work, not a partner pitch followed by an offshore implementation team. The person on the call is the person typing
- Honest framing. Sometimes the right answer is to buy a SaaS product instead of building a Power App. A good consultant says that even when it shrinks the engagement
- Real Microsoft expertise.Not generalist consultants who'll learn SharePoint on your dime. People who've been in the platform long enough to know what the docs don't say
- Modern delivery pace.AI-accelerated workflows in the consultant's own shop, not a 2018-vintage waterfall plan with a six-week discovery
The typical mid-market M365 engagement shapes
The most common requests we see at ACM, all of which fit the published Discovery Sprint or AI-Accelerated Sprint:
SharePoint Online tenant rationalization. You inherited a SharePoint estate that grew organically: 700 sites, ambiguous ownership, no retention, no labels. You need an honest inventory, a target architecture, and a migration plan that doesn't require freezing the business for a quarter. Typical scope: 4–8 weeks
Power Platform automation portfolio. You have a backlog of department-specific automations someone keeps asking for. Approvals, intake forms, deal-room workflows, invoice routing. You need an opinionated build-vs-buy review and a stack of shipped flows by the end of the engagement, with proper environment promotion and governance baked in. Typical scope: 4–6 weeks
Identity governance cleanup. Entra ID groups have proliferated, external sharing is unaudited, conditional access has gaps. You need a senior identity architect who can walk the tenant and ship a remediated state. Typical scope: 2–4 weeks
Mid-tenant migration. M&A merged you with another firm and now you have two tenants that need to consolidate. The Microsoft FastTrack scripts cover the happy path. You need the senior engineer for the unhappy path. Typical scope: 8–12 weeks
Why mid-market gets ignored
The big SIs don't take mid-market work because their cost structure makes it unprofitable below a certain minimum. A 30-person delivery org can't afford to spin up for a $50k engagement.
The small-business consultants cantake mid-market work but often don't have the senior bench to do it safely. A misconfigured conditional access policy at a 15-person company is a Slack channel ping. At a 300-person company it's a Tuesday afternoon outage that costs $80k in lost productivity.
The gap is a real one. It's the shape ACM was built for.
What “published pricing” lets you skip
The reason we publish prices — Discovery Sprint at $7,500, Sprint at $25k–$100k, Fractional Team at $20k–$50k/mo — is specifically to remove the half-hour-on-a-call to figure out if we're affordable. Mid-market buyers don't have time for that dance. They have an M365 estate that needs work, they have a budget, they want to know if those two numbers are compatible. We tell you before you book the call.
If your stack is Microsoft and your business is mid-market and your team is small — let's talk. Or read the capabilities page first. Either order.