AI Services Market › Use cases › Work & Operations
Work & OperationsDone with Claude Cowork, Claude Code May 3, 2026
Run finance project files through Claude Cowork
A portco CFO puts task files in a fresh folder for Cowork and moves them back afterward, and Claude is said to save the work of a full-time employee between projects. · May 3, 2026
- What They Did
- A portco CFO said they avoid file-deletion risk by putting only the files needed for a task into a new folder for Claude Cowork, then moving them back afterward. In the same thread, they described giving Claude project files with years of historical data plus instructions, then uploading a new ERP file so it could run scenario analysis; they also used Claude Code to build a payroll-variance web tool, with the human reviewing outputs for business-context nuances.
- How It Went
- They said Claude saves the work of an entire FTE between projects. Others in the thread reported faster modeling, flat headcount, and 10–15 hours a week saved, but stressed it has not fully automated everything and still needs checking for hallucinations and hidden errors.
- Worth Knowing
- The biggest catch described was rigor: keep Cowork scoped to a fresh folder, ask for an audit trail on Excel outputs, and expect human review rather than hands-off automation.
Try it yourself with Claude Cowork
I've put the files for [project name] in the folder [folder path]. Read everything there and do [task, e.g. build a variance analysis, reconcile the accounts, draft the board summary] following [any template or instructions file]. Save your output as [file type] in the same folder, with a short note listing your assumptions and anything you couldn't verify. Don't delete or overwrite the original files, and ask me before moving anything out of the folder.