knowledge-platform-delivery-cleanup-opportunities

Cleanup Opportunities: Platform Team, Knowledge Folder, and Delivery Folder

Date: 2026-03-27
Purpose: Comprehensive audit of cleanup opportunities across knowledge/, delivery/, and platform-related areas

---

Executive Summary

Three major structural issues need attention:

Priority	Issue	Impact	Effort
🔴 Critical	knowledge/sales/ vs knowledge/sales/ overlap	836 files misplaced	High
🔴 Critical	Duplicate knowledge/standards/ folder	238 files, 4.5MB font file	Low
🟡 High	Fragmented plans/ folders (10+ locations)	Hard to find planning docs	Medium
🟡 High	Code/config files in knowledge/	Violates separation of concerns	Medium
🟢 Medium	Transcript folder naming inconsistencies	Confusing navigation	Low

---

1. Critical Issues

1.1 sales/ vs gtm/ Folder Overlap 🔴

Problem:
The README documents that GTM content should live in knowledge/sales/, but 836 files actually live in knowledge/sales/. The gtm/ folder has only 4 files.

Documented Location	Actual Location	Files
gtm/agents/	sales/agents/	836+
gtm/partnerships/	knowledge/sales/partners/ (combined partners + partnerships)	20+ partners
gtm/services/	sales/services/	Full catalog
sales/content/cc-content-system/	sales/content/cc-content-system/	3 personal KBs
gtm/second-brain/	sales/second-brain/	Full backend

Specific Examples:

• knowledge/sales/agents/AGENT_REGISTRY.md should be knowledge/sales/agents/AGENT_REGISTRY.md
• knowledge/sales/services/README.md should be knowledge/sales/services/README.md
• knowledge/sales/partnerships/ Consolidated into knowledge/sales/partners/ (framework + per-vendor).

Recommendation:

1. Option A (Align to docs): Migrate all sales/ content to gtm/ to match documented structure
2. Option B (Align to reality): Update README to reflect sales/ as canonical location
3. Suggested: Option A — the gtm/ structure is cleaner and aligns with standard business terminology

---

1.2 Duplicate standards/ Folder in knowledge/ 🔴

Problem:
knowledge/standards/ is a complete duplicate of root standards/:

knowledge/standards/           →  standards/ (root)
├── 01-onboarding/             →  01-onboarding/
├── 02-writing/                →  02-writing/
├── 03-knowledge/              →  03-knowledge/
├── 04-prompts/                →  04-prompts/
├── 05-scripts/                →  05-scripts/
├── 06-technical-planning/     →  06-technical-planning/
├── agents.md                  →  agents.md
├── README.md                  →  README.md
├── CODEOWNERS                 →  CODEOWNERS
├── STYLE-GUIDE.md             →  STYLE-GUIDE.md
└── assets/icons/              →  assets/icons/
    └── HelveticaNeue.ttc (4.5MB duplicate!)

Files to Remove: 238 files, ~5MB total (mostly the font file)

Recommendation: Delete knowledge/standards/ entirely — root standards/ is the source of truth per .cursor/rules/knowledge-standards.mdc

---

2. High Priority Issues

2.1 Fragmented plans/ Folders 🟡

Problem: Planning documents are scattered across 10+ locations:

knowledge/plans/                    # Central plans (good)
├── active/
├── planned/
└── completed/

knowledge/delivery/plans/active/         # 4 files (should be in root plans/)
knowledge/delivery/project-plans/        # 4 client Q2 plans
knowledge/platform/plans/               # 6 platform initiatives
knowledge/engineering/data-platform/plans/  # 7 data platform plans
knowledge/engineering/platform/plans/   # 1 platform delivery plan
knowledge/executive/plans/planned/      # 3 executive plans
knowledge/finance/plans/planned/        # 1 finance plan
knowledge/legal/plans/planned/          # 1 legal plan
knowledge/marketing/plans/planned/      # 1 marketing plan
knowledge/operations/plans/planned/      # 1 operations plan
knowledge/people/plans/planned/         # 1 people plan
knowledge/sales/plans/planned/          # 2 sales plans
knowledge/clients/cta/plans/            # 1 client plan
knowledge/people/hiring/plans/          # 5 hiring assessment plans

Recommendation:

• Short-term: Update knowledge/plans/README.md to document distributed structure
• Long-term: Consolidate to knowledge/plans/ with subfolders by domain:

  knowledge/plans/
  ├── active/
  ├── planned/
  ├── completed/
  ├── delivery/
  ├── platform/
  ├── engineering/
  ├── gtm/
  └── clients/{client}/
  

---

2.2 Code/Config Files in knowledge/ 🟡

Problem: Code and config files are mixed with knowledge documentation:

File	Current Location	Should Be In
package.json, tsconfig.json	knowledge/platform/integrations/hubspot/api-service/	apps/ or tools/
package-lock.json	knowledge/integrations/hubspot/api-service/	Remove (duplicate)
*.js files	knowledge/resources/uncategorized_transcripts/	tools/scripts/
.env.example	knowledge/sales/second-brain/backend/	apps/ or remove
*.mcp.json, settings.json	knowledge/sales/content/cc-content-system/*/	User home or .cursor/
uv.lock	knowledge/sales/second-brain/backend/	apps/

Recommendation:

1. Move HubSpot API service to tools/hubspot-api-service/ or apps/hubspot-integration/
2. Move JS scripts to tools/scripts/
3. Move personal configs to appropriate user directories
4. Update .gitignore to prevent future commits of personal config files

---

3. Medium Priority Issues

3.1 Transcript Folder Naming Inconsistencies 🟢

Problem: Confusing naming for transcript storage:

knowledge/resources/transcript/              # Only has lenny/ (Lenny's Newsletter)
knowledge/resources/uncategorized_transcripts/   # Has actual transcripts/
knowledge/meeting/                           # Internal meeting transcripts
knowledge/clients/{client}/transcripts/       # Client transcripts

Issues:

• transcript/ (singular) vs transcripts/ (plural)
• uncategorized_transcripts/ is a confusing name
• lenny/ content should be under resources/lenny/ (already exists separately)

Recommendation:

1. Rename resources/transcript/ → resources/lenny-newsletter/ (it’s only Lenny content)
2. Rename resources/uncategorized_transcripts/ → resources/transcripts/
3. Move internal non-client transcripts from resources/transcripts/ to meeting/

---

3.2 Missing/Misnamed Folders per README 🟢

README Says	Actual	Action
company/	Does not exist	Create or remove from docs
ops/	operations/	Rename or update docs
research/	Does not exist	Create or remove from docs
gtm/pricing/	Only in sales/	Move when consolidating GTM

---

3.3 Personal Knowledge Base Fragmentation 🟢

Problem: Personal KBs scattered across multiple structures:

knowledge/sales/content/cc-content-system/
├── robert-gpt/              # Has quick-start/, memory/, patterns/
├── luke-gpt/                # Has quick-start/, memory/, patterns/, sections/
└── uttam-gpt/               # (not in gtm/, only in sales/)

knowledge/sales/content/cc-content-system/
├── robert-gpt/              # (also here!)
├── luke-gpt/                # (also here!)
└── uttam-gpt/               # Only here

Recommendation:

• Consolidate all personal KBs to one location (suggest knowledge/people/personal-kbs/ or keep in sales/content/cc-content-system/)
• Remove duplicates between sales/ and gtm/

---

4. Platform Team Specific Issues

4.1 Platform Plans Fragmentation

Current State:

knowledge/platform/plans/                    # 6 files (good)
knowledge/engineering/platform/plans/        # 1 file (delivery-skills-platform-plan.md)
knowledge/platform/research/                 # Agent-powered data environment
knowledge/engineering/data-platform/plans/   # 7 files (overlaps with platform/)

Recommendation:

• Move engineering/platform/plans/ content to platform/plans/
• Clarify boundary between platform/ (product/platform initiatives) and engineering/platform/ (technical implementation)

4.2 HubSpot Integration Duplication

Problem: Two HubSpot integration folders:

knowledge/platform/integrations/hubspot/     # Main documentation
knowledge/integrations/hubspot/                # Duplicate (only has package-lock.json)

Recommendation: Remove knowledge/integrations/ — it’s a partial duplicate

---

5. Delivery Folder Opportunities

5.1 Actually Well-Organized ✅

The knowledge/delivery/ folder is the best-organized section:

delivery/
├── README.md
├── INDEX.md
├── 00-head-of-delivery/
├── 01-roles-and-responsibilities/
├── 02-meetings-and-cadence/
├── 03-project-lifecycle/
├── 04-standards-and-sops/
├── 05-tools-and-skills/
└── 06-reference/

Minor Improvements:

• delivery/plans/ and delivery/project-plans/ could be consolidated
• Some content in delivery/03-project-lifecycle/ duplicates standards/ templates

---

6. Recommended Action Plan

Phase 1: Quick Wins (Low Effort, High Impact)

1. Delete knowledge/standards/ — 238 files, saves ~5MB
2. Delete knowledge/integrations/ — empty duplicate
3. Update knowledge/README.md to reflect actual structure

Phase 2: Consolidation (Medium Effort)

4. Migrate sales/ → gtm/ — Move 836 files to align with documented structure
5. Move code files — Relocate HubSpot API service to tools/
6. Consolidate transcripts — Rename folders for clarity

Phase 3: Structural Improvements (Higher Effort)

7. Consolidate plans/ — Create unified structure in knowledge/plans/
8. Create missing folders — company/, research/ (or update docs)
9. Consolidate personal KBs — Single location for all personal content

---

7. File Count Summary

Folder	Files	Notes
knowledge/sales/	836	Should move to gtm/
knowledge/sales/	4	Should receive sales/ content
knowledge/standards/	238	Delete (duplicate)
knowledge/clients/	500+	Well organized
knowledge/delivery/	50+	Well organized
knowledge/platform/	65	Minor consolidation needed
knowledge/people/	26	Well organized
knowledge/operations/	25	Well organized
knowledge/resources/	320	Needs naming cleanup

Total Knowledge Files: ~2,000+
Potential Files to Move/Delete: ~1,100 (mostly the sales/ → gtm/ migration)

---

Generated via audit on 2026-03-27