Tag: claude
Should AI skills follow the org chart or the process?
AI skills need both. A skill belongs to a role, which looks after it and may change it, and a step in a written process names it, which settles when it is used. Anthropic groups skills into role bundles. Filed by role alone, people hold tools with no order of work, and filed by process alone, nobody looks after them.
Is a consumer Claude plan safe for client data, and is it cheaper than Team?
Claude Max and Ultra run under the Consumer Terms, which carry no data processing addendum, so I keep client personal data on Team or Enterprise. On price, Max costs the same per five-hour session as a Team seat billed monthly. What Ultra buys is a higher ceiling for one heavy Claude Code user.
The LLM writes, the model decides
Pair a writing LLM like Claude with a cheap decision model that only returns numbers, such as TypeSafe Jev. Three ways to split the work, why a probability Claude writes down is a self-report and not a measurement, and why a reason written after the fact for a bare number is worse than no reason.
Claude inference hooks cannot see a screenshot
Anthropic now lets an Enterprise organisation put its own server in front of every prompt and return allow or deny before the model runs. It is the strongest inline control Claude has shipped. It also never receives raw image bytes, so a screenshot of the document you are trying to stop walks straight through, and the failure mode when your server goes down is a setting somebody has to choose.
Claude US-only inference costs 1.1x and that is the cheapest part
The Enterprise console offers one toggle that keeps all model inference in US regions for a 10 per cent surcharge. Underneath it are two independent settings, one of which is a one-way door you set when you create a workspace and can never change. The surcharge is the part everybody reads and the least expensive of the three costs.
The Claude Enterprise admin console has 25 sections and no map
Claude Enterprise puts 25 settings sections behind one nav, grouped into four blocks that do not match how anybody actually governs AI. Here is the whole tree, what each block controls, and the six settings worth opening on your first day as an Owner rather than the twenty-five you will otherwise scroll past.
Claude for Excel cannot save a file, and the error will not tell you that
Ask the Claude add-in in Excel to roll a workbook forward into next month and you get a permissions error, which reads like a misconfiguration and is not one. The add-in has no file management at all, and that limit is missing from the unsupported list. Here is what it does do well, why it beat Claude Code on the same spreadsheet, and the settings field that fixes the complaint everybody has.
Why your Claude Microsoft 365 connector is still read only
Anthropic shipped write tools for the Microsoft 365 connector on July 7, 2026, and left them switched off for every organization that had connected before that date. Nothing in the product says so. Here is how to check in ten seconds, the two admin gates in two different consoles, the scope that deserves a second look, and the write path already running in your building that will derail the diagnosis.
One line in your org-wide AI instructions cuts output by 24 percent
Adding an organization-wide instruction block does add tokens to every prompt, and that objection is correct. A controlled 180-call test on Claude Sonnet 5 shows one brevity line cutting output 23.9 percent and returning 14.2x its own cost, while the block carrying it fails to break even uncached.
Why a Claude share link will not open, and what actually works
A shared Claude conversation returns HTTP 200 whether or not you can read it, and the page carries six characters of visible text. Team and Enterprise chats are organization-only by design, attached files never travel with the snapshot, and the one programmatic route is a Compliance API that has no idea what a share link is.
An MCP server is unreviewed code with your file system in scope
Treat every MCP server as untrusted code that runs with the access your agent has, because that is what it is. Anthropic docs say the directory lists connectors but does not security-audit them. A registry of approved servers with nothing enforcing it is a memo. The control that binds is a managed allowlist matched by URL or command, never by name.
Claude is allowed in regulated finance, but it has no EU data residency
Two objections kill most regulated-finance AI conversations before they start. The first, that Anthropic does not permit Claude for regulated work, is false: Claude for Financial Services exists, banks run it, and the usage policy names finance high-risk, not forbidden. The second is real and almost nobody states it plainly: first-party Claude Enterprise has no EU data residency at all. There is no "eu" inference region and workspace storage is US-only. If you are FCA-regulated, that is the fact to design around, and the only EU route runs through a hyperscaler.
Your Claude Code deny rules are not a security boundary
Before you hand Claude Code to hundreds of people you add deny rules for .env and credentials and feel locked down. You are not. Those rules govern Claude own tools, not a Python one-liner that opens the same file, and the control that actually holds, the OS sandbox, reads your whole machine by default and fails open when it cannot start. The baseline worth setting is real. Its dangerous gaps are the defaults you never changed.
Your locked-down Claude sandbox is a holding pattern, not a destination
Giving everyone Claude inside an isolated VM, no sensitive data allowed, feels like the safe way to start. It is a fine way to start. The trouble is what happens when you leave people there: the leak it was built to stop walks out by copy-paste anyway, the friction recruits the shadow AI you were trying to prevent, and the value never compounds because nothing in an ephemeral box survives the session. A sandbox is a scaffold. Scaffolds come down.
Blocking the personal Claude account is an identity problem, not a network one
Your CISO trusts the control posture Microsoft gives Copilot. To get Claude to the same bar, do not reach for tenant restrictions: that header only fires on your network, so it is theater the moment a laptop goes off-VPN. The control that holds lives at identity. Enforce SSO, then claim your domain, and know that the claim is a one-way door.
You are at phase zero, and the deck you were sold starts at phase three
Every enterprise AI maturity model starts a rung above where most companies stand and skips the one that holds the rest up: getting the tool safely into people hands. Your team already has Claude. If IT cannot produce the tenant policy, the egress allowlist, the tool allowlist, and the audit log, you are at phase zero, whatever the deck says.
The Claude Certified Architect path and the four Academy courses
The Claude Certified Architect credential sits on a free, four-course learning path: Agent Skills, the Claude API, the Model Context Protocol, and Claude Code in Action. The courses carry the value. The exam is the paperwork. What each course covers and who on your team should take it.
How the Claude Partner Network tiers actually work
The Claude Partner Network is free to join, so membership on its own tells a buyer nothing. The real structure is four tiers, each earned by three published numbers: certified people, customers in production, and public references. What every tier asks for, and what comes back at each rung.
Your AI has no whoami
Every enterprise AI platform resolves what you can access through SSO and SCIM. None of them load your team instructions from who you are. Claude gives admins one 3,000-character field for everyone. Microsoft Copilot reads your permissions but not your team playbook. Here is the gap and what works today.
Claude Team vs Enterprise: when 50 seats is not a forced upgrade
The 50 seat number that scares Anthropic Team admins is the sales-assisted Enterprise minimum, not a forced upgrade. Claude Team runs to 150 seats. The real Team to Enterprise decision is about governance features like custom roles and the Compliance API, not headcount.
You probably do not need a transfer agent: how we self-manage our cap table with AI
Most early-stage startups are not legally required to use a stock transfer agent. Delaware law lets a company keep its own electronic stock ledger. Here is how we run our cap table at Tallyfy as a version-controlled JSON file, with AI doing the reconciliation and reports, plus what the law (DGCL 219, DGCL 224, Section 12(g)) really requires.
A Claude desktop setup guide for corporate networks
Installing Claude on a personal machine takes a minute. On a corporate machine the install works and then nothing connects. This setup guide covers the clean install on macOS and Windows, then the network layer, proxy, TLS inspection, and the outbound allowlist, where the afternoon actually goes.
A complete guide to working with Claude
Working with Claude now means a dozen things: Claude Code, the Desktop app, agents, the partner network, certifications, connectors. This is the map. A hub that lays out the five regions of working with Claude and links each one to a deeper guide.
Anthropic managed agents are not office agents
Anthropic managed agents and office agents are different products with confusingly similar names. Managed agents is a developer API for running autonomous Claude agents on managed infrastructure. The interesting part is the brain-hands split: Anthropic runs the agent loop, while the sandbox can run in your own environment. This is what it is, and when to use it.
Ask Your Org, and the case for scoping Claude yourself
Claude Ask Your Org connects Claude to Slack, Microsoft 365, and Drive in one project. Its security model is sound, permission-aware and not indexed. The question it makes easy to skip is scope. Here is when to use the broad tool and when to scope Claude yourself with a filesystem MCP server.
Claude Projects vs a git fileshare for teams
Claude Projects works well for one person. For a team, it is missing the thing collaboration is built on: version control. No diff, no history, no rollback. Here is the case for a git-backed fileshare driven by Claude Code instead, and the line where each one wins.
Claude, NetSuite, and the SuiteScript governance trap
Claude writes good SuiteScript, fast. But NetSuite meters every script with a governance unit budget, and AI-generated code does not see a limit that is not in the code. Here is what Claude does well in SuiteScript, the governance trap it walks into, and a safe workflow.
Design patterns for healthcare AI on Claude
A signed BAA makes a Claude healthcare workflow legal, not safe. The engineering work is keeping protected health information away from the model. Three design patterns do most of that: de-identify before the model, keep PHI local, and log what the model saw.
Is the Anthropic Certified Architect worth it
The Anthropic Certified Architect, Foundations is the first official Claude technical certification. It is also brand new and now a paid exam at $125, which makes it hard to value. The free Anthropic Academy courses are the part worth doing today. The credential is a bet on a job market that does not exist yet.
Self-hosted vs managed AI agents is a governance call
The choice between self-hosted and managed AI agents gets treated as build versus buy, a cost question. It is not. It is a governance decision about where your data goes, what you can audit, and whether you can leave. Here is what each path gives you and how to decide.