· 6 min read
Should a small team use Microsoft 365? An honest look at the default stack
Outlook, Teams, OneDrive, and SharePoint are what companies use — but "companies" usually means companies with an IT department. What the bundle actually costs a 5-person team, and when it's still the right call.
Most small companies don't choose Microsoft 365. They default to it. Someone's previous employer ran on Outlook, or an accountant said "you'll need Office," or the founder bought a Windows laptop and the subscription was already half-installed. Six months later the team is coordinating in Teams, hunting for files across OneDrive and SharePoint, and forwarding customer emails around a shared Outlook mailbox — and nobody remembers deciding any of it.
That's worth examining, because the Microsoft stack is genuinely good at something. It's just usually not the thing a five-person company needs.
What the bundle is actually for
Microsoft 365's pitch is coherence: one vendor, one bill, one identity system, and everything works together. Business Basic starts at a few dollars per user per month, which undercuts almost any combination of separate tools. On paper, a small team gets enterprise infrastructure for the price of a sandwich.
But look at what's in the bundle: Entra ID for identity management, Exchange admin for mail flow rules, SharePoint admin for site policies, Intune for device management on the Premium tier, Purview for compliance and data governance. These are superb tools — for an IT department. The bundle exists because a 500-person company needs central control over identity, devices, and data retention, and Microsoft sells all of it as one contract.
A five-person company has none of those problems yet. What it inherits instead is the interface to those problems: an admin center with hundreds of settings, a licensing page with a dozen near-identical SKUs (Business Basic, Standard, Premium, E3, E5, F3, Exchange Online Plan 1…), and tools whose defaults assume someone is being paid to configure them. When nobody is, the configuration just doesn't happen, and you run enterprise software on factory settings.
Where each piece falls short for a small team
Outlook and shared mailboxes. Email is the strongest part of the stack for one person and the weakest part for a team. Microsoft's answer to "we all need to handle support@" is the shared mailbox: free, no extra license, up to 50 GB. It also has no concept of ownership. Everyone sees the same undifferentiated pile; there's no way to mark a conversation as yours, in progress, or done. Read state syncs across the team, so one person opening an email makes it look handled to everyone else. Replies land in the sender's personal sent folder by default unless an admin flips a setting most small teams never find. Teams end up flagging, categorizing, and re-marking-as-unread as a workflow — which collapses the first time two people do it differently.
Teams. Teams is a meeting tool with a chat bolted on, and it shows. Threading is famously confusing — replies land in the wrong place, channels and chats are two separate systems with different features, and the notification model manages to be both noisy and easy to miss. Inviting an outside collaborator means guest access and tenant switching, which is enough friction that most small companies just email external people instead — putting the conversation right back where Teams was supposed to replace it. For video calls it's fine. As the place your team's day-to-day communication lives, it's what people tolerate, not what they'd pick.
OneDrive and SharePoint. These are one storage system wearing two brands, and the seam shows constantly. Every Teams channel silently creates a SharePoint site, so files scatter across personal OneDrives, channel sites, and whatever someone shared in a chat. "Where is that document?" becomes a genuine research task. Sync conflicts on co-edited files still happen. The permission model is powerful and inherited and almost impossible for a non-admin to reason about — which is how small teams end up with either everything locked down or everything shared with the whole company, and no idea which.
The upsell treadmill. The bundle price is the entry, not the total. Copilot is a separate per-seat subscription that costs more than the underlying plan. Advanced security is Premium. Real audit and retention is an E-tier feature. Each upgrade is small, and the total quietly becomes what you'd have paid for tools you actually liked.
When Microsoft 365 is the right call
An honest list, because the stack isn't a mistake for everyone:
- You live in desktop Excel. Financial modeling, heavy spreadsheets with macros — nothing else is close, and Business Standard is the cheapest way to license it.
- You're in a regulated industry. If you need retention policies, eDiscovery, and device management to satisfy an auditor, Purview and Intune under one contract is a legitimately good deal — and you probably have (or contract) the IT help to run them.
- Your clients demand it. Some industries run on Teams meetings and .docx attachments. Swimming upstream costs more than the subscription.
- You manage a fleet of Windows machines. Entra ID plus Intune is the sane way to do it.
Notice the pattern: every one of these is a reason a particular team needs the stack. None of them is "we're a company, so we should use what companies use."
What small teams pick instead
The alternative isn't one rival bundle — it's picking a good tool per job and accepting two or three bills instead of one:
| Job | The default | What small teams pick when choosing deliberately |
|---|---|---|
| Personal email + calendar | Outlook | Google Workspace, or any host for mail on your domain |
| Team chat | Teams | Slack (or nothing — a small team on a fast shared inbox needs less chat than it thinks) |
| Docs + files | OneDrive/SharePoint | Google Drive, Notion, Dropbox |
| Video calls | Teams | Google Meet, Zoom |
| Shared team email (support@, sales@) | A shared Outlook mailbox | A purpose-built shared inbox |
The per-seat total often lands close to a mid-tier Microsoft plan. What you're actually buying is tools that were designed for a team your size, with defaults that work before anyone configures anything.
The gap the bundle never fills: team email
Whichever way you go on the rest of the stack, the sharpest gap for a small company is the last row of that table. Customer-facing email — support@, sales@, billing@ — is a queue that needs an owner per conversation, and neither a shared Outlook mailbox nor a Google group actually provides that. (We've written an honest comparison of Google's built-in options too — they break in the same places.)
That's the piece Repliqo is built for. It can connect an existing Microsoft 365 or Outlook mailbox with no DNS changes — useful if you're staying on the stack and just fixing the shared-mailbox problem — or host support@ directly on your own domain with guided DNS setup, useful if you're leaving. Either way the team gets one queue with assignments, statuses, internal notes, and draft ownership, so "did anyone answer this?" stops being a question. Every workspace starts with a 14-day free trial for up to 5 people, no card required.
The larger point stands without us, though: the Microsoft stack is enterprise infrastructure sold at a small-business price, and the price isn't the cost. The cost is running tools built for an IT department you don't have. Choose each tool for the team you actually are — and if that examination lands you on Microsoft 365 anyway, at least this time it'll be a decision.