Claude Projects for Knowledge Management
Most 20 to 200 person businesses lose 30 percent of their institutional knowledge every two years through role changes, departures, and the founder\'s overflowing inbox. Claude Projects turns the leadership team\'s collective brain into a shared knowledge base every senior leader can query.
No new system. No IT project. Just the leadership team committing to put their thinking somewhere others can read it. We have built Project trees for Australian leadership teams across SaaS, professional services, manufacturing, healthcare, and equipment-plus-service businesses. We map the architecture, sit with each leader to populate their Projects, train the team, and set up a quarterly maintenance cadence so the knowledge base stays current.
Realistic ROI
Why Claude Projects (Not Notion AI, Not SharePoint Copilot, Not a Wiki)
Four properties of Claude Projects make this a leadership-team knowledge tool, not an org-wide documentation rebuild.
1M tokens means a Project's worth of documents fits in one prompt
A wiki retrieves snippets. Claude with a Project loaded reasons over the entire body of context at once. Ask "why did we pick that vendor in 2022 and what was the alternative" and Claude answers from the whole knowledge base, not the three chunks the search index returned.
The leadership team controls the Project (not IT, not the docs team)
No platform migration. No information-architecture committee. The CEO, COO, and chief of staff load the material themselves over a few sessions. They are the people whose knowledge is being captured. They are the right curators.
Conservative posture means gaps surface
When Claude does not have the answer in the Project, it says so. It does not invent. That is the feature you want. Each "I cannot find this in the Project" is a gap in the institutional memory you can now plug.
Excellent at unstructured-to-structured
A 30-minute CEO voice memo, a meeting transcript, a long email thread, a series of Slack messages: feed any of them in, ask Claude to produce a structured Project entry, and add it. The leadership team's thinking goes from ephemeral to queryable in minutes.
The Recommended Project Tree
For a 20 to 200 person business, this is the structure we build with leadership teams. Nine Projects, named maintainers, clear contents. Adapt for your context.
Leadership-Team Knowledge Base
9 Projects, each with a named maintainer
CEO Brain
What lives here
Vision, decisions log, key relationships, stakeholder map, board cycle, founder commentary.
Who maintains it
CEO + chief of staff
Leadership Team
What lives here
OKRs, retros, all-hands content, weekly leadership notes, leadership offsite outputs.
Who maintains it
Chief of staff or COO
Sales
What lives here
ICP definition, value props, battle cards, top-account briefs, pricing playbook.
Who maintains it
Head of sales
Customer Success
What lives here
Top-account profiles, QBR templates, escalation patterns, renewal commentary.
Who maintains it
Head of CS
Operations
What lives here
SOPs, vendor decisions and contacts, incident playbooks, operational risks register.
Who maintains it
COO or head of ops
Finance
What lives here
Chart of accounts, accounting policies, key board financial narratives, audit trail commentary.
Who maintains it
CFO or finance manager
People
What lives here
EVP, policies, lifecycle templates, leadership-development library, culture canon.
Who maintains it
Head of people
Brand & Marketing
What lives here
Tone of voice, brand library, key messaging, campaign archive, customer language.
Who maintains it
Head of marketing
Board
What lives here
Board charter, prior minutes, director skills matrix, prior board pack archive, succession plan.
Who maintains it
Chair + company secretary
Access controls per Project. CEO Brain and Board Projects are restricted. Sales and CS Projects are visible to those teams. The architecture is designed in the discovery workshop.
The Tribal-Knowledge Killer Matrix
Common knowledge gaps in a 20 to 200 person business, what they cost when they bite, and how the Project tree captures them.
| Symptom | Cost when it bites | Which Project captures it | How to populate |
|---|---|---|---|
| The founder is the only one who knows why we picked this vendor in 2022 | Founder gets pulled into vendor dispute meetings six months after stepping back | Operations or CEO Brain | 30-min interview, transcribed, summarised by Claude into a structured decision entry, parked in the Project. |
| Sarah from accounts has the spreadsheet that runs month-end | Sarah goes on leave, month-end is a scramble; Sarah leaves, month-end breaks | Finance | Working session with Sarah; Claude turns the spreadsheet logic + her process notes into a structured SOP in the Finance Project. |
| The HR policy is in three people's email and the head of people's memory | New manager applies the wrong policy, Fair Work risk, costs more in dispute than getting it right | People | Email export to PDF + Claude consolidation into a single policy library, version-controlled in the People Project. |
| The customer history lives in Sales' head; the CSM cannot answer "why did they pick us" | CSM walks into renewal call cold; expansion opportunities missed because no one knows the buying history | Customer Success | 20 min with the original sales rep per top account; Claude turns the conversation into a customer-history brief in the CS Project. |
Each gap above costs more in interruption, error, and re-discovery than the 30-minute capture session that prevents it.
Eight High-Leverage Knowledge-Management Use Cases
Drawn from real Australian leadership-team rollouts. Times shown are typical.
| Task | Traditional | With Claude | Notes |
|---|---|---|---|
| New senior-leader onboarding | 3 to 6 months to full effectiveness | 4 to 8 weeks | New leader queries the Project tree on day one. "What is our position on X? Why did we pick Y? Who decided Z?" Founder dependency drops fast. |
| Decision archaeology (why did we pick X?) | "Ask the founder", interrupts whoever is busy | 60 seconds in the Project | Claude reads the decisions log and supporting context. Leader gets the why, the alternatives considered, and what changed since. |
| Vendor history reconstruction | Half a day of email and contract archaeology | 15 minutes | Operations Project holds vendor decisions, contracts, key contacts, incidents. New leader handling a vendor dispute is up to speed in one query. |
| Customer history reconstruction | Sales tribal knowledge or none at all | 10 minutes per top customer | CS Project holds the why-they-chose-us, key relationships, prior issues, expansion potential. Survives the CSM leaving. |
| Founder brain dump (capture before they leave) | Rarely happens, lost when founder exits | 6 to 8 hours of recorded sessions over 2 weeks | Founder voice-records, transcripts go into Claude, structured entries land in the CEO Brain Project. Survives the founder transition. |
| Strategy decision log | Slide decks no one re-reads | 5 min per decision to log + queryable forever | After every leadership decision, a 5-minute Claude prompt produces the entry: decision, rationale, alternatives, owner, review date. Goes into the Leadership Project. |
| All-hands content reuse | Each leader writes from scratch | 15 to 30 minutes per all-hands | Claude reads prior all-hands, draft messaging, and the OKR Project, then drafts the next all-hands. Tone of voice consistent. |
| Board succession knowledge transfer | Months of overlap with departing director | Days, supported by the Board Project | Incoming director queries the Board Project for prior minutes, charter, decisions, and director skills matrix. Self-onboards. |
Risk and Governance for the Knowledge Base
Six areas your leadership-team AI policy must cover. We draft the 1-pager as part of the engagement.
Project access controls
Claude Team and Enterprise plans support member-level access to Projects. Set this up at the start. CEO Brain and Board Projects are not visible to the broader org. Sales and CS Projects are visible to those teams. Get the permission model right before you load sensitive material.
Confidentiality for board and CEO-only material
Board minutes, M&A discussions, executive comp, founder reflections: these belong in restricted Projects with named members only. Claude Enterprise gives admin audit logs so you can see who accessed what.
Data classification for commercially sensitive material
Vendor contracts with confidentiality clauses, customer data, employment files, and board material should be in Enterprise tier with full audit logs. Less sensitive operational knowledge can sit in Team tier.
Project ownership (someone has to be the maintainer)
Every Project needs a named maintainer. Without one, the Project goes stale within a quarter. We assign maintainers in the rollout and review staleness every 90 days.
Exit risk when senior leaders depart
When a senior leader leaves, their Projects must be reassigned, not deleted. Build the handover into your departure checklist. The whole point of this exercise is to prevent the loss-on-exit problem.
AI use disclosure to the board and possibly to staff
The board should know the leadership team is using Claude on the institutional knowledge base. Most boards welcome it. Where staff data is involved, a 1-line disclosure in your AI usage policy covers expectations. We provide sample wording.
How Yes AI Helps the Leadership Team Build the Knowledge Base
Four pillars of every knowledge-management engagement.
Project architecture workshop
Half a day with the leadership team to map the Project tree to your business: which Projects exist, who maintains each, who has access, what lives where. The output is a one-page architecture diagram and a population plan.
Leader-by-leader Project build
Each senior leader gets a 60 to 90 minute working session. We sit with them, surface what is in their head and their drives, and produce structured Project entries together. By the end of the engagement, every leader has at least one populated Project.
Maintenance routine
Quarterly Project review cadence built into your leadership-team rhythm. 30 minutes per Project, every 90 days. Add new decisions, retire stale entries, surface gaps. The knowledge base stays current because the routine is in the diary.
Onboarding integration
Every new senior hire gets a "first 90 days with the Project tree" induction. Day one access to the relevant Projects, a guided tour, and a list of starter queries. Onboarding time drops by 50 to 70 percent.
Our 5-Step Knowledge-Base Rollout Process
Most leadership teams complete the rollout in 5 to 8 weeks.
Discovery + knowledge-gap audit with CEO + leadership
Half day with the CEO, COO or chief of staff, and 2 to 3 senior leaders. Identify the top 10 to 15 knowledge gaps that have cost the business in the last 12 months. Map them to the Project tree.
Procure Claude Team or Enterprise + set up Project tree
Set up Claude Team or Enterprise with SSO. Create the 9-Project structure with member-level access controls. Naming conventions, Project descriptions, and starter prompts in place.
Leader-by-leader Project population sessions
Working sessions with each senior leader (60 to 90 minutes per leader). We bring real material into the room (drives, emails, prior decks, transcripts) and produce structured Project entries together.
Train all senior leaders + chief of staff
Live 90-minute training session for the full leadership team. We use their actual Projects and walk through the queries they will use weekly. Recorded for new joiners and the chief of staff.
Quarterly Project review + maintenance
Every 90 days, we facilitate a 2-hour leadership-team session: each Project owner reviews their Project, adds new decisions, retires stale entries, and flags gaps. Continuous, not set-and-forget.
Knowledge-Management Claude FAQ
Book a Leadership-Team Briefing
45-minute working session for the CEO, COO or chief of staff, and 1 to 2 senior leaders. We will run a Project-tree mapping exercise on your real business, address confidentiality and access concerns, and propose a productized engagement scope.
All discussions held in confidence. Australian-based consultants.