If your company runs on Microsoft 365, most of this stack is already paid for, and that is the strongest argument on this page — it is just not ours. What follows is about what assembling it actually involves, and about the fact that we are built to sit beside the suite, not to take it away from you.
Capability by capability
Every line about Microsoft 365 (Teams + Planner + Loop + Dynamics) was read on its own pages on 24 September 2026. Where we are still building something, the table says so.
| Microsoft 365 (Teams + Planner + Loop + Dynamics) |  |
|
|---|---|---|
| Conversation | ||
| How many products you are assembling | Teams for the conversation, Planner for tasks, Loop for shared pages, Dynamics 365 for the customer — four products with four sets of licensing rules. | One product, and it sits beside Microsoft 365 rather than replacing it. |
| From talk to work | ||
| What Planner needs underneath | Plans hang off Microsoft 365 Groups, attachments sit in the group’s SharePoint library, comments and My Tasks need Exchange Online, and premium plans are stored in Dataverse and run on Project for the web. | Boards are part of the same product as the chat. Nothing underneath to license separately. |
| Timeline, dependencies and goals | Premium only. A Project Plan 1 is required to create premium plans, and a colleague holding only a Microsoft 365 licence can keep collaborating on such a plan but cannot use those features. | Kanban, list, table and Gantt on every plan that has Boards. |
| What Loop needs underneath | A SharePoint or OneDrive licence for full feature access, an Exchange Online mailbox for @mentions and workspace sharing, and its files count against the organisation’s SharePoint quota. | Documents and boards live in the product and do not consume somebody else’s quota. |
| People and focus | ||
| Guests in the CRM | An invited external user gets no access to the customer engagement apps until you assign them a licence and a security role. | A guest costs no seat: one per user on Free, two on Workspace, three on Business OS. |
| Where Loop content escapes a control | Information Barriers are not supported for content stored in SharePoint Embedded containers, which is where Loop workspaces live. | One permission model across chat, boards and documents. |
| Culture, clients, tickets | ||
| Culture: kudos, surveys, eNPS | Not part of any of the four. Another vendor, another login. | From the free plan; pulse surveys and eNPS from Workspace. |
| Where it runs | ||
| Sitting beside it | This stack is the suite. Replacing a part of it means arguing with the licence you already pay for. | Mail, documents and the drive stay in Microsoft 365. Calendar syncs both ways. We replace the four to eight tools stacked on top, not the suite. |
Sources: Microsoft Planner for admins · Manage the Planner app in Microsoft Teams · Microsoft Loop requirements · Microsoft Loop compliance summary · Invite B2B users to Power Platform and Dynamics 365 · Dynamics 365 Sales overview. Checked against Microsoft 365 (Teams + Planner + Loop + Dynamics)’s own pages on 24 September 2026.
Giving the point away
Three of them, and none is a throwaway. If these are what your team runs on, Microsoft 365 (Teams + Planner + Loop + Dynamics) is the right answer and we would rather you knew now.
Teams, Planner and Loop come with editions of Microsoft 365 a great many companies already buy. Against a marginal cost of zero, no feature list wins, and we are not going to argue otherwise.
The same account, the same conditional access, the same retention and eDiscovery tooling across mail, files, chat and tasks. For a regulated company that has already passed an audit on Microsoft, that coherence is worth more than any individual feature we have.
Sales Premium, conversation intelligence, predictive scoring, the whole Power Platform underneath. Our CRM is in development. At enterprise scale this is not a close comparison.
Where the difference shows
Planner needs Groups, SharePoint, Exchange and — for premium — Dataverse. Loop needs a SharePoint or OneDrive licence and an Exchange mailbox, and eats the SharePoint quota. Dynamics needs its own licence and a security role even for a guest. Each is a place something breaks and an admin has to go looking.
Timeline, dependencies, milestones, custom fields, sprints and goals are premium in Planner. A colleague on a plain Microsoft 365 licence can collaborate on the plan but cannot use them. In taos everyone on a plan gets the same product.
Kudos, Feedback Friday, leaderboards, anniversaries, surveys and eNPS exist in none of the four, so a company that wants them adds a vendor. Ours start on the free plan.
In Dynamics an invited external user has no access until you assign a licence and a security role. Our guest costs no seat and gets one named channel and one project on Boards.
Information Barriers are not supported for SharePoint Embedded containers, which is where Loop workspaces live. In taos one permission model covers chat, boards and documents.
Mail, documents and the drive stay where they are; the calendar syncs both ways with Microsoft 365. taos replaces the four to eight tools stacked on top of the suite, which is a different argument from replacing the suite.