Examples of what you can keep in the base
Examples of what you can keep in the base
Eleven examples that come from a real base and already work. They are not a limit: everyone builds their own base with their own topics. When you paste the initial prompt, Claude offers them, asks whether any of them fits you and what other topics you want to keep, and builds only what you are going to use. The rest can be added when you need it, with one sentence.
| Case | What it builds | Questions it answers |
|---|---|---|
| Suppliers and contacts | A single directory: company, what it does and who is who | “Who handles our support for X?” · “Who do I talk to about the invoice?” |
| Contracts and expiry dates | A contract register, as a table and in JSON, with dates, notice periods and renewals | “What expires in the next six months?” · “What is unsigned?” |
| Invoices | A register of invoices, in a table and in JSON, linked to its contract | “How much have we paid so far from this bank of hours?” · “What are we paying without a contract?” |
| Budget | One document per year with the budget lines, planned and actual, cross-checked with contracts and invoices | “Which lines go up, and why?” · “Which contracts have no budget line?” |
| Receipts and expenses | The monthly reconciliation of a card’s charges with their receipts, and a register of months handed in | “Which charges this month have no receipt?” · “Which subscriptions are on the wrong card?” |
| Access to services | Which service, its address and which account you sign in with. Never passwords | “Which account do we use to sign in to the X console?” |
| Domains, certificates and subscriptions | Their renewal calendar | “What renews this quarter, and on which card?” |
| Procedures | How each thing is done, step by step | “How do we set up a new user?” |
| Projects and decisions | Who each one is for and who pays, status, milestones, why each thing was decided and what you deliver, with versions | “Why did we rule out that option?” · “Which version did we send them, and when?” |
| Inventories | Equipment, licenses or software, always dated | “How many licenses do we have, and when was this last checked?” |
| Articles and communication | A guide to how you write —your tone, what you never use, what has already been corrected—, a register of what you have published and each article with its drafts | “Write me a draft in my style” · “Which figures did I use in my last article, and where did they come from?” |
💡 The real payoff is cross-checking them. Each case works on its own, but the value appears when they come together: an invoice that doesn’t match any contract, a contract with no line in the budget, or a supplier who bills you and isn’t in the directory. That only shows up when the information is in the same place.
Back to the home page · Cowork guide · Claude Code guide