Claude Cowork: what it does for commercial services operations, and what it doesn't

Anthropic shipped Cowork to general availability earlier this year. It's been positioned as Claude Code for non-developers; an agentic desktop tool that reads your local files, uses your connectors, and finishes multi-step work without you babysitting each prompt.

That's the marketing. The question worth asking is whether it does anything useful for a commercial GC, an MEP contractor, or a facilities operator.

The short answer: yes, in specific places. Not everywhere.

What Cowork actually is

Cowork runs inside the Claude desktop app on macOS or Windows. You point it at a folder; it can read, edit, create, and delete files in that folder. It connects to the services you already use through connectors (Outlook, Google Drive, SharePoint, Slack, and a few hundred others). It can also use your screen directly when there's no connector for a tool, though screen use is slower and less reliable than a connector.

You give it a goal, not a prompt. It plans the steps, runs them, and shows you what it's doing. You can stop it. You can make it ask permission before each step, or let it run. It writes files; it sends drafts; it builds spreadsheets.

That's the system. Now the operator question: where does it earn its place?

Where Cowork is useful for commercial services

Document-heavy work that nobody has time for. Project closeout is the canonical example. O&M manuals, warranties, as-builts, submittals, punch list documentation. A folder of forty PDFs from twelve subs, in twelve different formats, that has to become one closeout package. Cowork can read across the folder, pull what matters, and assemble a structured draft. Your PM still reviews it, but the assembly time drops from a week to an afternoon.

Estimating support. Quantity takeoff from drawings is still a specialized job. But the work around the estimate (pulling historical pricing from past projects, cross-referencing subcontractor quotes, building the bid comparison sheet) is exactly the kind of synthesis work Cowork handles. Hand it the bid folder. Ask for a comparison matrix. Review the result.

RFI and submittal tracking. Reading a dense spec section and pulling out every submittal requirement is tedious work that a junior PE typically does. Cowork reads spec sections faster than a person and surfaces what's required. Same with change order documentation; given the daily reports and the original scope, it can draft the COR narrative.

Operations reporting that gets skipped. This is the one Anthropic talks about that's actually true. If you've got a weekly ops report that you've been meaning to start producing for six months and haven't, because nobody has the two hours, Cowork can be the difference between getting it done and not. Point it at the source files. Tell it the format. Let it draft.

Where Cowork falls short

It can make real changes to your files. If you point it at a folder and tell it to organize, it will. If your instructions are loose or contradictory, the cleanup can include things you didn't want cleaned up. Anthropic flags this in their own documentation. The fix is to keep instructions specific and to use "ask before acting" mode until you trust the workflow.

It's not for regulated workloads. Anthropic explicitly says do not enable Cowork for HIPAA, FedRAMP, or financial services regulated environments. For most commercial GCs and MEP contractors this doesn't matter. For anyone working federal contracts or healthcare facilities with PHI in the mix, it matters a lot.

Complex spreadsheets are still a weak spot. If your estimating template is a forty-tab workbook with nested macros and conditional formatting that took the controller six years to build, don't expect Cowork to operate it without breaking something. It handles columnar data well; it struggles with structurally complex spreadsheets.

The computer has to be on. Cowork runs on your local machine. If your laptop is asleep, nothing is happening. There's no cloud mode. If you're going to use it for overnight work, the machine has to be awake.

It's a research preview in places. Computer use (the part where Claude clicks around in apps that don't have connectors) is still flagged as a preview. It works; it's also slower and less reliable than the connector path. Plan accordingly.

Where to start, if you start

Don't roll it out across the company in week one. Pick one workflow that meets three criteria: it's document-heavy, it's slow, and nobody is excited to do it. Project closeout is a good first candidate. So is monthly invoice review against the schedule of values. So is the weekly ops report nobody has time to write.

Run it for two weeks with one person. Measure how long the work used to take and how long it takes now. Note what Cowork got wrong, and what your reviewer had to fix. If the math works, expand to a second workflow. If it doesn't, you've spent two weeks instead of two months.

The mistake to avoid is treating Cowork as a productivity tool you buy once and roll out everywhere. It's an automation tool that earns its keep on specific, repeated, document-heavy work. Find that work first. The tool is the easy part.