What Nimbus replaces in your current stack

Most companies did not choose an AI stack. They accumulated one. Slack or Teams became the filing cabinet. A search product became “the knowledge layer.” Microsoft 365 Copilot became the programme. ChatGPT or Claude became the unofficial thinking surface. A studio or a Power Platform flow became “agents.” None of those products is a bad tool. Each was stretched into a job it was not designed to finish.

Nimbus is an enterprise AI operating system: isolation of jobs, scoped tools, fail-closed writes, a budget, and a record that survives the session. It does not replace your CRM or try to be Word. It replaces the overlay — the products you bought so AI work would have somewhere to live, which still leave the signed change in someone’s private thread.

McKinsey’s 2025 State of AI keeps showing the same split: use is common, scale is not. Scale fails when find-and-draft is licensed per head and execution is still folklore. This page maps what to stop stretching, what to keep, and why one operating layer is usually cheaper than the overlay — and better at the jobs the overlay never owned.

The stack you already paid for

A typical “we have AI” environment looks like this:

None of the left-hand products disappears because Nimbus exists. What disappears is the pretence that the right-hand column is free. Search is not memory. A recap is not a write-back. A channel is not a workstream. The four pillars — Communication, Collaboration, Automate, Governance — are the jobs the overlay split across vendors. Nimbus hosts all four on one job object.

What Nimbus replaces in Slack and Microsoft Teams

Slack and Teams are excellent at conversation. They are a poor system of record for decisions, and a worse runtime for agents.

What actually happens: the discount exception lives in a DM. The hold reason lives in #warehouse. “Legal is comfortable” is a thumbs-up from whoever was online. Next quarter, finance searches the characters p-r-i-c-e and calls the hit memory. Decisions made in direct messages is that cost. It is not a chat outage. It is a missing object.

Nimbus replaces Slack and Teams as the place AI work lives:

• A named workstream, not a channel with a bot
• Files bound to the job; guests without every connector
• A loop that notifies a roster, not a dead channel
• A refused write as a record, not “Sarah said it looked fine”

Conflux is the workspace hub — orientation, then a handoff into governed execution. Keep Slack for “are you free at 3.” Stop using it as the ledger. Operator test: hide the channel. Can a stranger reconstruct the signer, the payload, and the policy version? If the answer is Slack search, you have folklore with push notifications.

What Nimbus replaces in Glean and other context layers

Glean is permission-aware workplace search. SharePoint search, Notion AI, and “company knowledge” in ChatGPT are cousins: indexes that try not to leak. Nimbus does not try to crawl 2019.

The stretch is the problem. Search vendors added assistants, then agents, then production credentials “because the index already respects permissions.” Permission to see is not permission to change. Nimbus vs Glean is the full cut. The short version:

Nimbus replaces the context layer as an operating system. It does not replace Glean as a universal search bar across a 20,000-person corpus. Keep that knowledge programme if you have one. If RevOps needed a signed opportunity update this quarter and was told to wait for the crawl, you bought the wrong graph.

Perception is ordinary language over the scoped world you attached. The wiki is what the company asserts. Search cannot invent a signer.

What Nimbus replaces in Microsoft Copilot

“Copilot” is several products. Microsoft 365 Copilot is the $30/user/month add-on in Word, Outlook, Teams, and the Copilot app, grounded in Microsoft Graph. Copilot Studio is the low-code environment for agents that leave Microsoft. Collapsing those in procurement is how E5 gets treated as an operating layer.

Nobody else will recap this thread and the attached deck as well as Copilot inside Outlook. That recap is tenant productivity. Updating forty opportunities in Salesforce is company operations. Nimbus vs Microsoft Copilot is the product cut. This page is the stack cut: Copilot is the personal assistant. Nimbus is collaborative AI — several people, one job, a named stop.

Keep Copilot in Office. What Nimbus replaces is the sentence “every knowledge worker has a Copilot licence, so we have an AI operating model.” E5 explains identity, compliance, and Office. It does not explain CRM write-back, model routing, or a company work ledger. Stay personal for solo drafting — see collaborative AI and personal assistants. Cross-department work that mutates a live system is not that job.

What else the overlay usually includes

The rest of the budget usually went here:

• ChatGPT Enterprise and Claude. The right move against shadow AI. Still an assistant. Confirmation-gated writes are not a release.
• Dust and other studios. Shared helpers. Activity logs are not a signed CRM change.
• Salesforce Agentforce. The right agent inside Salesforce. Jobs that also involve Drive and legal still need a place that is not only field history.
• RPA. Keep it where the screen is the only door. It is not a loop, a workflow, or a reasoner. See loop vs RPA.
• Perplexity. Cited answers from the web. Not a production login.
• Zapier / Make. Fine for a notification. Not a roster, a wiki clause, or a fail-closed write.

The composition you actually want is in loop vs workflow vs agent: agent for the unknown path, workflow when stops and roles matter, loop when the same signal fires again. All three on one workstream. Not three more vendors.

Drafts can travel. Write credentials should not.

Why the replacement is better, not only cheaper

The job is the unit. A workstream has a brief, a roster, scoped connectors, a budget, and a finish line. A channel has none of those. A copilot thread has a user.

Writes are releases. Connectors stay read-only until a named person signs a quoted payload. Missing signer means nothing happens. That is write-back governance, not a confirmation click people train themselves to ignore.

Playbooks are asserted. The wiki is what agents must follow — a discount floor, a journal policy — rather than a prompt pasted into a custom GPT. RBAC sits on the job.

Repeat work compiles. Loop engineering turns Monday’s close into a standing order with a run page. You stop paying a frontier model to rediscover a checklist. Agents should be disposable: the job survives the model swap.

The record is causal. The Lifecycle Graph answers “who approved this, against which policy, what changed.” Chat logs answer a different question. Governance as a multiplayer primitive is why a control only one person can operate is not an organisational control.

Context compounds; models are infrastructure. Last quarter’s signed artefact is input to this quarter’s run. Nimbus routes compact extract versus frontier judgement. You do not re-explain the company to a new chat window every Monday.

Function walkthroughs: operations, revenue, finance, legal, HR, customer support.

The pricing differential — cheaper because it is a different object

Seat-versus-seat comparisons hide the bill. Copilot is listed at $30 per user per month, paid yearly, on top of a qualifying Microsoft 365 plan. Glean does not publish a rate card; third-party estimates cluster around $45–$50 per user per month, often with a large-seat minimum. ChatGPT Enterprise is quote-only; reported deals often land near $45–$75 per user per month. Slack Business+ is $15 per user per month annually — and baked-in AI does not make the channel a ledger.

Nimbus is priced per operator, with NTUs that grow with seats and pool across the org. See pricing.

A five-seat Team org has a 2,500 NTU pool, not five private allowances. A 25-seat Scale org has 50,000 NTU. Idle seats fund busy operators. That is the opposite of Copilot, Glean, and ChatGPT, which licence the headcount and still meter the hard work as Studio credits or FlexCredits the moment you try to do something. AI token economics: seats predict people; production spend is inference, tools, and writes.

Every completed model turn posts NTUs. There is no “unlimited Perception” hiding the ladder, and a short recap does not cost the same as a 20k-token dump. Heavy work costs more units because it cost more to run. Light work does not.

Per-user list versus the overlay

Team is a few dollars above Copilot’s add-on — and Copilot is not the operating layer. Scale is below a three-product overlay at list, with writes, a wiki, and a Lifecycle Graph in the same seat.

Worked company: 100 people, 25 operators

Vendors prefer you licence AI per head. The jobs still sit with about 25 people.

The overlay is Copilot and a context product and an assistant and a studio, plus implementation. Glean-scale crawl is a programme. Copilot Studio at organisational scale is usually a partner. Nimbus is self-serve for most buyers.

A coherent coexistence is still cheaper: keep Copilot on the cohort that lives in Word; do not licence Glean-as-OS or ChatGPT-as-CRM; put the 25 operators on Team or Scale. That is $875 or $3,000 for the operating layer — not $11,000 of find-and-draft with no ledger.

Why the unit stays cheaper than seats

Seat licences never get cheaper for the same recap. Nimbus cost controls sit on one invoice:

1. Pool, not sprawl. seats × 500 on Team, seats × 2,000 on Scale. Finance sees one ceiling, attributed by job.
2. Published extra work. Commitment at Scale’s included rate ($0.06 / NTU) or PAYG (~$0.10). No surprise overage line.
3. Routing. Classify-this-ticket should not pay flagship rates. See what to look for in model routing.
4. Context that compounds. Wiki, prior runs, and the graph mean the next job does not re-explain the company from a blank chat. You pay for completed work, not for rediscovery.

If your entire programme is “summarise my mail,” Copilot at $30 is the cheaper SKU. Nimbus is cheaper for the stacked programme — the one that was supposed to change systems of record — because you stop buying four products that fail the same operator tests, and you stop licensing unused seats to people who never run a job.

What you keep — and how this shows up in Nimbus

Replacement is not a bonfire. Keep Slack or Teams for conversation. Keep Copilot in Office if Microsoft’s graph is the work. Keep Glean if permission-aware search across a huge corpus is a real programme. Keep ChatGPT or Claude as a sanctioned thinking surface so personal Plus accounts die. Keep Salesforce, NetSuite, and the HRIS as systems of record. Keep RPA where the screen is the only API. Nimbus is the system of work. What you stop buying is a second operating layer in each of those logos.

Conflux meets the communication habit without becoming another inbox. Workstreams host the job. Agent teams are department-shaped operators with scoped grants. Governance is the fail-closed write path. The Lifecycle Graph is the ledger. Integrations attach live systems read-only until a human releases a write. Models are routed, not worshipped.

You can start a trial or talk to sales. Score Nimbus the same way you would score anyone else: file bound to a job, roster with a guest, skipped loop runs, refused write. The useful outcome is whether those four demonstrations share one object.

Related reading: what is an enterprise AI operating system, how to evaluate collaborative AI, how to evaluate an agent harness, and what is AI governance.

Sources

• Microsoft 365 Copilot pricing
• Microsoft 365 Copilot architecture
• Glean
• McKinsey, The state of AI in 2025
• Nimbus pricing