Claude Projects for Finance, One Project Per Cycle

A Claude Project is a workspace with its own knowledge base, its own instructions and its own memory. You load the documents once, write the standing instructions once, and every conversation inside it starts already knowing your business.

Most explanations stop at calling it a folder for chats. That undersells the part that matters for finance work, which is that each project accumulates its own separate context and keeps it away from everything else you do.

The decision that matters is how you slice them

Nearly everyone starts with one project called Work, fills it with everything, and then wonders why the answers get vaguer. The knowledge base is doing its job. You gave it too many jobs.

Anthropic’s documentation is explicit that each project has its own separate memory space and its own project summary, so context inside one stays focused and stays out of the others. That is the property to design around.

The slice that works for finance is one project per recurring cycle, not one per topic and not one per tool.

Project	What lives in it	Why it earns its own space
Month-end close	Close calendar, the checklist, last three months of variance commentary, your chart of accounts, the reporting pack template	It runs every month with the same shape. The context compounds, and by month three it knows what your recurring accruals look like.
Budget and forecast	Assumption documentation, driver definitions, the current plan, prior-year actuals	Different question and a different vocabulary from the close. Mixing them is what makes the answers vague.
A specific business partner	Their P&L, their headcount plan, the last few reviews, the things they always ask	The value here is remembering the argument you had in March about how their allocation works.
Board and exec reporting	Prior packs, the house style, the definitions your CFO uses	Tone and format matter more than analysis, and that is a distinct instruction set.
A one-off project	The deal, the system migration, the restructure	Deliberately temporary. Archive it when the thing is done rather than letting it dilute a permanent project.

The test for whether something deserves its own project: would you want a conversation about it to remember an unrelated conversation? If no, separate them.

What belongs in the knowledge base

The instinct is to upload everything. Resist it, because the knowledge base is the thing shaping every answer, and noise in it is worse than a gap.

What earns its place is the material you would hand a new analyst on day one.

• Your chart of accounts, with the definitions. Half of bad AI finance output comes from a model guessing what a cost center contains.
• The close calendar and checklist, so it knows what happens when.
• Two or three months of your own variance commentary. This is the highest-value upload on the list, because it teaches the house voice better than any instruction you could write.
• Report templates and the reporting pack format.
• Definitions your company uses that differ from the textbook. Every finance function has three or four of these, and they are the ones that cause wrong answers.

What does not belong: raw transaction exports, anything you would not put in a shared drive, and last year’s material that has been superseded. Old documents do not sit quietly. They get retrieved and cited.

On capacity, paid plans switch on retrieval automatically as the knowledge base approaches the context limit. Anthropic says this expands what a project can hold by up to ten times while maintaining response quality. That is their number rather than mine, and the practical read is that you are unlikely to hit a wall before you hit a relevance problem.

The instructions are where most of the value is

The knowledge base is what Claude knows. The custom instructions are how it behaves, and this is the part people leave blank.

A close project’s instructions should cover the things you would otherwise retype every single time.

• Who the output is for and what they already know. Commentary for a CFO and commentary for a business partner are different documents.
• The materiality threshold. Without it you get a paragraph about a movement of eleven hundred dollars.
• That it should ask rather than assume when a figure is missing. This one instruction removes most invented numbers.
• The format you send. If your pack is three bullets per variance with a driver named, say that.
• What it must never do. Mine says never state a number that did not come from a file I provided.

That last instruction is worth writing on any finance project. A model asked for a total will sometimes produce a plausible total, and a plausible total is indistinguishable from a real one until somebody checks.

Building the close project, start to finish

1. Create the project and name it for the cycle rather than the tool. Month-end close, not Claude stuff.
2. Upload the chart of accounts, the close checklist and the last three months of commentary. Nothing else yet.
3. Write the instructions, covering audience, materiality, format and the never-invent rule.
4. Test it on a month you have already closed. You know the answers, so you can grade it properly, and you will find out in twenty minutes whether the knowledge base is right.
5. Fix what was wrong in the knowledge base rather than arguing with the output. Bad answers here are nearly always a missing document rather than a bad prompt.
6. Only then use it live, and add to the knowledge base as you go rather than in one big upload.

Step four is the one people skip and it is the whole quality control loop. running a month-end close with Claude covers the close workflow itself in more detail.

What is new, and what it changes

Memory now works across chat and Cowork in the cloud, and it is the same memory. Hand Cowork a task and the context built up across months of project conversations is already there, which removes the re-explaining step that used to start every session.

For a close project that compounds usefully. The project learns your recurring accruals, your seasonal patterns and the three cost centers that always need a second look, and that knowledge is available whether you are chatting or handing off a task.

Claude Cowork covers Cowork itself, and Claude for Excel is the Excel add-in that shares the same context.

Plans, sharing and the governance question

Projects are available on every plan including free, where you are capped at five. Pro, Max, Team and Enterprise remove that limit and add the automatic retrieval behavior above.

Sharing is the Team and Enterprise feature. You can share a project with specific people at view or edit level, or with the whole organization. For a finance team that is the interesting part, because it turns a project from a personal setup into a shared standard: one close project the whole team works in, with one set of instructions, rather than five people each prompting differently.

Two things to settle before you put company data in one.

• Who can see it. A project shared organization-wide is visible organization-wide, and a close project’s knowledge base is a reasonable description of how your company makes money.
• What your retention and audit position is. Ask your admin rather than assuming, because the answer differs by plan, and it is a much easier question to ask before the upload than after.

AI governance for finance covers the wider governance picture for finance teams.

Where projects stop being the answer

Three honest limits.

A project is not a database. If the question is what were sales in March, the answer belongs in a query against your actual system, not in a chat with a document about March. Projects are for the work where judgment and context matter, and Power Query is the deterministic route for anything recurring.

A project is not version control. The knowledge base holds what you last uploaded, and if the plan changed on Tuesday and no one replaced the file, it will confidently answer from the old one. Set a habit of replacing rather than adding.

And a project does not make the output auditable. Somebody still has to be able to say where a number came from. That is a workflow you build, not a feature you switch on.

If you want the broader shelf, Claude for finance covers every Claude surface and which job each is for.