vCIO Client Knowledge Base: A Claude Project That Remembers Every Decision

What This Builds

Right now, prepping for a retainer client's quarterly review means scrolling through six months of email threads trying to remember what you recommended last time and whether it ever got done. This build gives each retainer client its own Claude project holding a running decisions log, roadmap notes, and renewal dates. You open one project before a QBR and ask it directly instead of digging through old files, and the answers stay consistent from quarter to quarter instead of relying on memory.

Prerequisites

• Claude account with Projects available. Free plans include Projects with limited storage; the Pro plan ($20/month) gives you a larger knowledge base and longer context per project
• De-identified engagement notes, past QBR summaries, and a roadmap document for at least one retainer client
• Familiarity with that client's NDA and any AI usage policy they've issued, since this project stores their information persistently

Your ongoing cost is a single Claude subscription. Every retainer client gets a separate project under that one account, so the cost doesn't multiply per client.

The Concept

A Claude project works like a labeled drawer in a filing cabinet, one drawer per client, except the assistant sitting next to that drawer has already read everything inside it before you ask a question. You write custom instructions once, telling Claude how to behave inside that drawer, and then add documents over time. Every new conversation you start inside the project loads those instructions and files automatically, so you never re-explain who the client is or re-upload last quarter's notes.

Build It Step by Step

Part 1: Create the project

Open Claude, find Projects in the sidebar, and select Create project. Name it clearly by client, using a code or short nickname rather than the client's full legal name if that itself feels like more identifying detail than you want sitting in a project title.

Part 2: Write the project's custom instructions

Paste something like this into the project's custom instructions field:

You are a working memory for one retainer client's IT consulting engagement.
Your job is to help prepare for quarterly business reviews and check-ins by
answering questions using only the files uploaded to this project.

Rules:
- Answer only from the uploaded files. If something isn't in them, say so
  instead of guessing.
- When you state a past recommendation or decision, name which uploaded file
  and roughly which date it came from.
- Never store or repeat a password, API key, or live network configuration.
  If a user tries to paste one into this project, decline and remind them
  this project is for documentation and decisions only.
- Use role titles (office manager, IT point of contact) instead of full
  names when summarizing who was involved in a decision, unless the user
  asks for a specific name.

Part 3: Seed the knowledge base

Upload documents that describe engagement history without exposing anything sensitive:

• De-identified summaries of past QBRs and check-in calls
• The client's technology roadmap document
• A renewal calendar listing product, license count, and renewal date only

Leave out admin passwords, live firewall or network configuration exports, and a full employee roster. Use generic role titles anywhere a real employee name would otherwise appear. If this client has issued its own AI usage policy as part of your engagement agreement, follow it even where it's stricter than the defaults above.

Part 4: Query it before a QBR

A few weeks before each quarterly review, open the project and ask something like: "Based on this client's history, what did we recommend last quarter that hasn't been implemented, and what's changed since then?" Claude answers from the uploaded files instead of you re-reading them yourself.

Real Example: Quarterly Review Prep for a Logistics Client

Setup: A project seeded with the last three quarters' de-identified QBR summaries, a roadmap document, and a renewal calendar for a 45-employee logistics client on a monitoring and support retainer.

Input: "What did we recommend last quarter that hasn't been implemented yet, and what should we raise at this QBR?"

Output: A short list noting that multi-factor authentication rollout for admin accounts was recommended two quarters ago and still shows as pending in the roadmap document, that a Microsoft 365 license renewal falls within the next six weeks, and a suggested opening line for the QBR tying both items together.

Time saved: Skips the search through old email threads and past decks entirely, and recommendations stay consistent quarter over quarter instead of drifting with memory.

Before You Repeat Anything to the Client

Treat everything the project surfaces as a draft of your own memory, not a finished answer you can repeat straight to the client. Before saying "we recommended X last quarter" in a QBR, open the source file Claude cited and confirm the date and detail actually match. Claude can misattribute a decision to the wrong quarter when two similar notes exist in the same project, and you're the one accountable for what gets said in the room, not the project.

What to Do When It Breaks

• Claude states something that sounds plausible but isn't actually in an uploaded file → Ask it directly which file supports the claim. If it can't point to one, treat the statement as unverified and check your own records before using it.
• The knowledge base goes stale because you forgot to add this quarter's notes → Before each QBR prep session, ask the project what the most recent dated file in it is. If that date is more than a quarter old, add the missing notes first.
• Sensitive data got pasted in by accident early on → Delete the file from the project immediately, and check Claude's data controls for how to request deletion of anything already processed, since removing a file from the project doesn't retroactively undo earlier processing.
• Two clients with similar names get confused → Keep project names and any short codes clearly distinct, and never open two similarly named projects in adjacent browser tabs during prep.

Variations

• Simpler version: Keep one shared "vCIO reference" project for templates and general talking points, separate from any per-client project, so template updates don't require touching every client's files.
• Extended version: After each QBR, add that quarter's fresh summary to the project the same day, so the knowledge base updates itself as part of your existing wrap-up routine instead of a separate task.

What to Do Next

• This week: Set this up for your one or two highest-value retainer clients first.
• This month: Roll it out to every retainer client once you've confirmed the workflow holds up in a real QBR cycle.
• Advanced: Pair this project's output with a renewal outreach process, so license and contract details surfaced here feed directly into your next renewal conversation.

Advanced guide for IT consultant professionals. These techniques use more sophisticated AI features that may require paid subscriptions.