Every new hire takes about three months to learn how your business actually runs: which client hates phone calls, where the real price list lives, why invoices go out on Thursdays. Claude Cowork gets there faster for one simple reason. It writes things down. Memory is the feature that turns a capable assistant into one that already knows your clients, your folder structure and your standing rules. This guide explains what Claude Cowork stores, where those files live, and how Australian businesses should manage them.
What Claude Cowork actually remembers
Cowork memory is not a mysterious black box. It is a folder of plain Markdown files sitting alongside your workspace. Each file holds one fact with a short description and a type label, and an index file called MEMORY.md lists them all, one line per memory. That index loads at the start of every session, so Claude begins each conversation already briefed on what it learned last week.
The facts fall into four rough types:
Preferences. How you like things done: Australian English, AUD figures, drafts saved as files rather than pasted into chat.
Project facts. Ongoing work and constraints, such as a client engagement that lives in a particular folder, or a deadline agreed on 14 July rather than a vague next Friday.
Feedback. Corrections you have given, plus the reason behind them, so the same mistake does not come back next month.
References. Pointers to external things: a reporting dashboard, a Notion board, a booking link.
Because everything is plain text, you can open the folder and read exactly what your assistant believes about your business. That transparency matters. There is no hidden profile you cannot inspect, and nothing stops you editing or deleting a file the moment it is wrong.
How memory gets written, and what stays out
Claude saves a memory when it learns something non-obvious that will matter beyond the current conversation. Tell it once that your BAS agent wants the GST reconciliation in a specific spreadsheet layout, and that instruction becomes a file. Correct a draft email because the tone was too formal for your trade clients, and the correction is recorded with the reason attached. Relative dates get converted to absolute ones, so a note made in July still makes sense when it resurfaces in October.
Just as important is what stays out. Cowork is designed not to persist sensitive personal information without being explicitly asked: health details, government identifiers such as TFNs, financial account numbers, home addresses. For a business handling client records under the Privacy Act and the Australian Privacy Principles, that default is the right one. Claude can work with sensitive material during a session without writing it into long-term storage.
What repeated context costs you
The value of memory is easiest to see in dollars. Take a Sydney bookkeeping practice where the principal bills at $110 an hour. Without persistent context, every session starts with re-explaining: which clients are on Xero, how the month-end checklist runs, what the letter template looks like. Call it 15 minutes of setup across three sessions a day. That is 45 minutes daily, roughly 170 hours across a 230-day working year, or about $19,000 of billable time spent repeating yourself.
With memory doing its job, that overhead drops close to zero after the first fortnight. The practice describes its quirks once, corrects a few early drafts, and from then on every session starts warm. The same effect shows up for a Brisbane builder managing supplier quotes or a Melbourne allied health clinic drafting referral letters: the assistant stops being a stranger every morning.
How to manage memory well
Memory works best when you treat it as a small business asset rather than something that just accumulates. A few habits keep it sharp:
Review it monthly. Skim MEMORY.md the way you would skim a staff handbook. Ten minutes is usually enough for a small business.
Correct out loud. If Claude acts on a stale fact, say so in the conversation and ask it to update the memory. The fix persists for every future session.
Prune, do not hoard. A finished project or a departed client should leave the memory folder. Fewer, sharper facts beat a long list of stale ones.
Seed it deliberately. In your first week, spend half an hour telling Claude the things a new employee would need: key clients, naming conventions, who approves what.
Back the folder up. It is plain text in your workspace, so your existing backup or sync arrangement covers it. Losing it costs you the on-boarding effort all over again.
One distinction saves confusion: memory is different from project instructions. A CLAUDE.md file or project instruction sheet is the rule book you author directly, and it always loads. Memory is what Claude learns along the way. Put permanent policy in the rule book, and let memory hold the living detail that changes month to month.
Set up well, memory compounds. Every correction makes the next week's work slightly better, and after a quarter the assistant carries context no contractor could match on day one. If you want help setting up Claude Cowork with sensible memory hygiene from the start, book a short call with us and we will walk through it with your team.
