“Claude” is three buying decisions that get collapsed in meetings. The model is what you call from your own software. Claude for Work is Anthropic’s hosted assistant: chats, Projects, artifacts, connectors, and admin controls. Claude also shows up inside other products. Nimbus is none of those. It is the place a strong analysis becomes an approved change in Salesforce, billing, or the policy pack — with a named person on the release.

This article compares Nimbus to Claude for Work, and to the idea that “we standardised on Claude, so we are done.” The API is complementary: Nimbus can send a step to Claude rather than replacing it. Standardising on a model is not the same as standardising on a place departments finish work.

Claude for Work is a serious product. It is built around careful long-context analysis, writing, coding help, and a safety posture enterprises actually cite in questionnaires. Projects give a person or a small team a durable bundle of files and instructions. Artifacts give you something you can look at besides a wall of prose. Connectors and company admin exist because Anthropic knows enterprises will not live in a personal claude.ai tab forever. That is a thinking partner with a workspace. It is still a thinking partner.

Words you’ll hear

Claude for Work. Anthropic’s hosted workspace: chats, Projects, artifacts, connectors, and company admin.
Project. A durable bundle of files and instructions in Claude. Excellent context for one person or a small team. Not a company job.
Constitutional AI. Anthropic’s research on training models to refuse and to be careful. That is model behaviour. It is not a company operating layer.
Workstream. In Nimbus, a shared workspace for one job, with the people, tools, and approval rules attached.
Wiki. Official playbooks agents must follow — including a discount floor, a journal policy, or a write rule.
Write-back. Changing a live system. Connectors stay read-only until a named person signs.
Lifecycle Graph. The causal record of what ran, who approved it, and what changed.
Model routing. Sending each step to the right model. Claude is often right for long, careful writing and wrong for a routine extract.

Why the difference matters

Claude for Work is excellent at what Anthropic optimises: careful long-context analysis, writing, coding help, and a safety posture enterprises actually cite in questionnaires. Anthropic’s privacy policy is the product’s own account of how the hosted assistant handles data. Read it as the privacy story for Claude-the-product. It is not a company operating system. Privacy of the assistant and provenance of a company action are related concerns. They are not the same control.

In Claude, the organisational unit is the conversation (and the Project). Memory is whatever Anthropic’s product retains for that workspace, plus the files you uploaded. When the Project is deleted, or the person leaves, the “memory” is a pile of chats. That is fine for analysis that was always meant to be personal or small-team. It is fragile for a discount exception that finance must still explain in two years.

In Nimbus, the same job is a workstream. An agent team drafts against the wiki clause that states the rule. Finance and legal can sit on the same canvas. Customer records stay read-only until a human releases the change. The Lifecycle Graph keeps what ran, who approved it, and what changed — so next quarter you are not hunting Slack for “the Claude doc.” A Project is context. A signed change is the record.

Anthropic’s Constitutional AI work is why enterprises cite Claude’s safety posture. The research is about training models to refuse and to be careful. That is valuable. A model that refuses a harmful request is not a named signer on a CRM write. A brilliant Project is still context. Those refusals still do not give you a company operating layer. Do not let a safety questionnaire stand in for a release process.

If the executive summary is “we bought Claude, therefore we have enterprise AI,” you have bought a model and a workspace. You have not bought a place departments finish work. That gap is where people start pasting Claude output straight into Salesforce — ungoverned write-back with extra steps. Careful analysis that becomes an unsigned field is still an unsigned field.

Claude’s long context is a model feature. A Lifecycle Graph is a product feature. Do not confuse a very large window with institutional memory.

The fork is practical by role. Analysts, counsel, and writers get a thinking partner that is unusually good at long documents — Claude for Work is often the right daily surface. Engineers may want the Claude API so they can own orchestration, evaluation, and tool policy: a build, not an operating layer for operators. RevOps and finance need the analysis to land as a quoted change with a signer, not another Project named after last quarter’s close. Security will like Constitutional AI as a model-behaviour story and still ask who can change production records. A COO should not be told that desktop and coding agents (Claude Cowork and similar) are the company AI programme; those personal runtimes are closer to OpenClaw or Hermes than to a company operating layer.

The job split is therefore: Claude thinks; Nimbus finishes. You can use Claude as the model behind a Nimbus step. You should not use a Claude Project as the system of record for a decision that hit the CRM.

When Claude is a better fit

Choose Claude for Work when the job is high-quality reasoning and writing on documents you can put in a Project, you do not need gated writes into the systems that hold customer and money data, and you want Anthropic as both model vendor and the place people work.

Choose the Claude API when you have engineers to own orchestration, evaluation, and tool policy. That path is honest: you are building. Do not pretend the API is a workstream product with a wiki and a graph.

Desktop and coding agents (Claude Cowork and similar) are personal runtimes. Choose them for a person who will look after their own machine. Do not standardise the company on them and call it governance.

Using Nimbus does not mean abandoning Claude. It means Claude stops being the place the company thinks the work finished. A healthy coexistence: people keep Claude for careful analysis; Nimbus routes some steps to Claude when the task is long, careful writing; anything that must change Salesforce, billing, or the policy pack is a workstream with a signer. Paste is a last resort, not the integration.

How this shows up in Nimbus

Nimbus is not a Claude competitor in the model sense. Claude is often the right model for long, careful writing. It is the wrong default for a routine extract, and the wrong abstraction for “how we run AI at work.” See models. Routing is how you avoid using the most expensive model for every small task, and how you keep Claude in the loop without making Claude the loop.

Nimbus keeps three planes operators actually run: asserted policy (wiki), live systems (connectors, read-only by default), and derived memory (Lifecycle Graph). Perception lets anyone ask in ordinary language — “what did we approve for this account last quarter?” — without hoping someone named the chat correctly. That is the opposite of a Project whose title only the author remembers.

You can set Nimbus up yourselves. You are not waiting on vendor engineers to invent an operating layer around Claude. If you already have Claude for Work, keep it. Attach the systems of record in Nimbus. Put the playbook in the wiki. Let Claude draft; let a human release.

See Governance.

Questions people actually ask

Does Nimbus compete with Anthropic?

At the application layer, yes. At the model layer, no. Nimbus is a customer of frontier models. Routing is how you avoid using the most expensive model for every small task. A Claude-shaped step inside a workstream is complementarity. A Claude Project used as the company archive is substitution you will regret.

Can I bring my own Claude API key?

Model routing and bring-your-own-key options are part of how Nimbus treats models as infrastructure. Talk to sales for the current enterprise path. Do not assume a one-to-one replica of Anthropic’s consumer chat inside Nimbus; the experience is workstreams and Perception, not a clone of claude.ai.

Is Nimbus “just a wrapper on Claude”?

No. A wrapper is a chat window. Nimbus ships a Lifecycle Graph, specialist agent teams, and a read-only-default path for changing records. If the model behind a step is Claude, that is routing, not wrapping. If you removed Claude and routed the same step elsewhere, the workstream, wiki, and graph would still be there.

Claude vs ChatGPT Enterprise vs Nimbus?

Claude and ChatGPT are rival assistants (and rival APIs). Nimbus can sit on either. Shortlist Anthropic vs OpenAI on model and workspace grounds — writing quality, safety posture, company knowledge, Workspace Agents versus Projects. Shortlist Nimbus when the work includes production writes and a ledger. See Nimbus vs ChatGPT Enterprise. Buying the assistant bake-off and skipping the operating-layer question is how you end up with two chats and still no signer.

Will Claude for Work update Salesforce for us?

Not as a release manager for enterprise writes. Thinking in Claude and pasting into Salesforce is productivity. It is also drift. If the plan is “an agent team drafts, a human releases, the graph stores the artefact,” you are specifying Nimbus — and you can still use Claude as the model behind the draft.

Is a Project the same as a workstream?

No. A Project is a durable bundle of files and instructions. Excellent context for one person or a small team. A workstream is a shared workspace for one job, with people, tools, approval rules, a budget, and a finish line. Projects do not give you connector-level least privilege, quoted writes, or a Lifecycle Graph. Useful for research. Not an operations unit.

Does Constitutional AI mean we can skip write-back gates?

No. Constitutional AI is model behaviour: refusal and care in training. Write-back governance is a product control: the connector cannot write until a named person signs the quoted change. A careful model can still propose a bad field update. The gate is what stops the proposal becoming a fact.

Can we use Claude for Work beside Nimbus without duplicating memory?

Yes, if you are strict about what each remembers. Claude remembers the analysis in a Project. Nimbus remembers the job, the playbook version, the signer, and the change. Do not copy the CRM into a Project “for context” and then treat that copy as official. Point at the live system from the workstream.

Who owns Claude vs who owns Nimbus?

Knowledge workers and often legal or research own Claude for Work as a thinking surface. Engineers may own the API. Operators who own systems of record own Nimbus workstreams. Security reviews both.

What is write-back governance, What is model routing, and Nimbus vs ChatGPT Enterprise.

Nimbus vs Claude: A Thinking Partner or a Place Thinking Becomes an Approved Change?