Brainforge Vault: Agent Scaling Guide
Vision: 20-30 specialized AI agents running your business operations Current State: Foundation in place with personal βSecond Brainβ templates Path Forward: Systematic knowledge capture β Agent specialization β Orchestration
π― Current State Assessment
What You Have Now
1. Personal AI Second Brains (sales/content/cc-content-system/)
- robert-gpt/ - Your personal knowledge base
- Luke/ - Team memberβs knowledge base
- Structure: Memory (semantic) + Experiences (episodic) + Brain Health (metrics)
- Workflow:
/plan β /work β /review β /learncycle
2. Organizational Knowledge (Top-level directories)
company/- Company-wide context (planning, initiatives)engineering/- Technical knowledge (meetings, transcripts)gtm/- Go-to-market (sales, marketing, partnerships)ops/- Operations (SOPs, processes)people/- People ops (hiring, onboarding, roles)research/- Research and vendor assessments
3. Project-Specific Knowledge (lmnt/)
- Client project documentation
- Meeting notes and transcripts
- Discovery artifacts
4. Agent Foundation
- Agent definitions in
.claude/agents/(chief-of-staff, email-agent, etc.) - Skills system in
.codex/skills/ - Orchestration pattern (chief-of-staff routes to specialists)
π How to Use the Vault Today
Phase 1: Personal Knowledge Capture (Week 1-2)
For You (robert-gpt/):
-
Fill Core Context (2 hours)
memory/personal/ βββ services.md β What Brainforge offers βββ positioning.md β Market positioning βββ expertise.md β Your expertise areas βββ differentiators.md β What makes you unique -
Document Company Context (3 hours)
memory/company/ βββ products.md β Brainforge services βββ positioning.md β Company positioning βββ differentiators.md β Competitive advantages -
Capture Customer Intelligence (2 hours)
memory/customers/ βββ ideal-customer-profile.md βββ pain-points.md βββ objections.md -
Add Examples (ongoing)
memory/examples/ βββ proposals/ β Winning SOWs (like hedra-sow.md) βββ emails/ β Effective email templates βββ linkedin/ β Thought leadership content
Action Items:
- Migrate content from
knowledge/sales/(SOWs) βmemory/examples/proposals/ - Extract patterns from
lmnt/project βmemory/patterns/ - Document company values β
memory/values-beliefs/
Phase 2: Organizational Knowledge Structure (Week 3-4)
Create Shared Memory Structure:
knowledge/
βββ memory/ # NEW: Shared organizational memory
β βββ company/
β β βββ services.md # All Brainforge services
β β βββ positioning.md # Company positioning
β β βββ team.md # Team structure, roles
β β βββ processes.md # Core business processes
β βββ customers/
β β βββ icp.md # Ideal customer profiles
β β βββ pain-points.md # Common pain points
β β βββ case-studies.md # Client success stories
β βββ operations/
β β βββ sales-process.md # Sales methodology
β β βββ project-delivery.md
β β βββ quality-standards.md
β βββ patterns/
β β βββ sales-patterns.md # What works in sales
β β βββ delivery-patterns.md
β β βββ communication-patterns.md
β βββ examples/
β βββ proposals/ # Winning proposals
β βββ contracts/ # Contract templates
β βββ deliverables/ # Example deliverables
Action Items:
- Create
memory/directory at vault root - Migrate
company/content βmemory/company/ - Extract patterns from
lmnt/βmemory/patterns/ - Document processes from
ops/βmemory/operations/
Phase 3: Agent Specialization (Week 5-8)
Start with 5 Core Agents:
-
Sales Agent (
agents/sales-agent.md)- Knowledge:
memory/customers/,memory/patterns/sales-patterns.md - Capabilities: Draft proposals, handle objections, qualify leads
- Tools: Read, Write, CRM integration
- Knowledge:
-
Project Manager Agent (
agents/pm-agent.md)- Knowledge:
memory/operations/project-delivery.md,lmnt/projects - Capabilities: Create project plans, track deliverables, manage timelines
- Tools: Read, Write, Task management integration
- Knowledge:
-
Content Agent (
agents/content-agent.md)- Knowledge:
memory/examples/,memory/style-voice/ - Capabilities: Write proposals, emails, thought leadership
- Tools: Read, Write
- Knowledge:
-
Research Agent (
agents/research-agent.md)- Knowledge:
research/,memory/company/ - Capabilities: Vendor research, competitive analysis, market research
- Tools: Read, Web search, Write
- Knowledge:
-
Operations Agent (
agents/ops-agent.md)- Knowledge:
ops/,memory/operations/ - Capabilities: Create SOPs, document processes, quality checks
- Tools: Read, Write
- Knowledge:
Action Items:
- Create agent definitions in
.claude/agents/at vault root - Each agent references specific
memory/directories - Test each agent with real tasks
- Document agent capabilities in
AGENTS.md
π― Path to 20-30 Agents
Agent Taxonomy (How to Think About Agents)
By Function:
- Sales: Sales agent, Proposal agent, CRM agent
- Delivery: PM agent, Technical lead agent, QA agent
- Marketing: Content agent, SEO agent, Social media agent
- Operations: Ops agent, Finance agent, Legal agent
- People: Hiring agent, Onboarding agent, Culture agent
- Research: Research agent, Competitive intel agent, Vendor agent
By Knowledge Domain:
- Client-facing: Sales, proposals, account management
- Internal: Operations, finance, people ops
- Technical: Engineering, data, infrastructure
- Strategic: Research, planning, analysis
Scaling Strategy
Stage 1: Foundation (5 agents) - Month 1-2
Goal: Prove the concept with core business functions
- Sales Agent
- PM Agent
- Content Agent
- Research Agent
- Ops Agent
Success Criteria:
- Each agent can handle 80% of tasks in their domain
- Knowledge base is searchable and accurate
- Agents can reference each otherβs work
Stage 2: Expansion (10 agents) - Month 3-4
Goal: Cover all major business functions
Add:
- Proposal Agent (specialized from Sales)
- Technical Lead Agent
- Hiring Agent
- Finance Agent
- Customer Success Agent
Success Criteria:
- Agents handle 90% of routine tasks
- Clear agent boundaries and handoffs
- Quality metrics improve
Stage 3: Specialization (20 agents) - Month 5-6
Goal: Deep specialization within functions
Add:
- Email Agent (already exists)
- CRM Agent (already exists)
- Data Agent (already exists)
- SEO Agent
- Social Media Agent
- Legal Agent
- Vendor Management Agent
- Competitive Intel Agent
- Account Management Agent
- Quality Assurance Agent
Success Criteria:
- Agents can handle complex, multi-step workflows
- Agent-to-agent communication works smoothly
- Business runs 50%+ on agent automation
Stage 4: Optimization (30 agents) - Month 7-12
Goal: Fine-tuned specialization and automation
Add:
- Contract Review Agent
- Invoice Agent
- Meeting Prep Agent
- Follow-up Agent
- Documentation Agent
- Training Agent
- Analytics Agent
- Forecasting Agent
- Risk Assessment Agent
- Innovation Agent
Success Criteria:
- 80%+ of routine work automated
- Agents proactively suggest improvements
- Business runs smoothly with minimal human intervention
π Knowledge Capture Strategy
What to Capture (Priority Order)
1. High-Value, Frequently Used Knowledge
- Customer profiles and pain points
- Sales processes and objections
- Service offerings and positioning
- Winning proposals and contracts
2. Patterns That Compound
- What works in sales conversations
- Effective proposal structures
- Successful project delivery patterns
- Communication that lands
3. Examples of Excellence
- Best-in-class proposals
- Effective email templates
- Thought leadership content
- Project deliverables
4. Processes and Standards
- Sales methodology
- Project delivery process
- Quality standards
- Onboarding procedures
5. Context and History
- Past projects (experiences/)
- Client relationships
- Market research
- Competitive intelligence
How to Capture (Daily Practice)
After Every Client Interaction:
- Save email/meeting notes β
experiences/[client-name]/ - Extract patterns β
/learncommand - Update customer profile if new insights
After Every Project:
- Document in
experiences/[project-name]/ - Extract deliverables β
memory/examples/ - Extract patterns β
memory/patterns/ - Update process docs if improved
Weekly Knowledge Maintenance:
- Review
brain-health/growth-log.md - Update low-confidence patterns
- Add new examples to
memory/examples/ - Clean up outdated information
Monthly Strategic Review:
- Assess agent performance
- Identify knowledge gaps
- Plan new agent specializations
- Update company positioning if needed
ποΈ Infrastructure Needed
1. Knowledge Management System
Current: Markdown files in directories Needed:
- β Keep markdown structure (works great)
- β Add semantic search (already have MCP memory integration)
- β οΈ Consider vector database for large-scale search
- β οΈ Add knowledge graph for relationships
Action: Current structure is sufficient for 20-30 agents. Consider enhancement at 30+ agents.
2. Agent Orchestration
Current: Chief-of-staff pattern (manual routing) Needed:
- β Keep chief-of-staff pattern
- β οΈ Add agent-to-agent communication protocol
- β οΈ Add workflow automation (agent chains)
- β οΈ Add agent performance monitoring
Action: Build agent communication protocol. Document in AGENTS.md.
3. Quality Assurance
Current: /review command with 6-agent review
Needed:
- β Keep review system
- β οΈ Add quality metrics per agent
- β οΈ Add automated quality checks
- β οΈ Add feedback loops (learn from mistakes)
Action: Extend review system to track agent-specific quality.
4. Access Control
Current: All agents can read all memory Needed:
- β οΈ Define agent access scopes
- β οΈ Personal vs. organizational memory separation
- β οΈ Client-specific knowledge isolation
Action: Create access control matrix for agents.
5. Monitoring and Analytics
Current: Brain health metrics (basic) Needed:
- β οΈ Agent usage metrics
- β οΈ Task completion rates
- β οΈ Quality trends per agent
- β οΈ Knowledge freshness tracking
Action: Build monitoring dashboard (can start simple with markdown logs).
π Best Practices
Knowledge Capture
- Be Specific: βWe won the LMNT deal byβ¦β not βWe sometimes win dealsβ¦β
- Include Context: Why something worked, not just what worked
- Update Regularly: Outdated knowledge is worse than no knowledge
- Cross-Reference: Link related knowledge (use markdown links)
Agent Design
- Single Responsibility: Each agent does one thing well
- Clear Boundaries: Know when to hand off to another agent
- Knowledge Scoping: Each agent has specific memory directories
- Tool Limitations: Agents only get tools they need
Orchestration
- Chief-of-Staff First: Always route through orchestrator for complex tasks
- Agent Chains: Document common workflows (e.g., Sales β Proposal β Legal)
- Error Handling: What happens when an agent fails?
- Human Escalation: When to involve humans
Quality
- Review Everything: Use
/reviewbefore important outputs - Learn from Mistakes: Update memory when agents make errors
- Pattern Confidence: Track which patterns are HIGH/MEDIUM/LOW confidence
- Continuous Improvement: Regular agent performance reviews
π― Success Metrics
Knowledge Quality
- Coverage: 80%+ of business functions documented
- Freshness: Knowledge updated within 30 days of change
- Pattern Confidence: 50%+ patterns at HIGH confidence
Agent Performance
- Task Completion: 80%+ of routine tasks handled by agents
- Quality Score: Average 8+ on
/reviewscores - Time Savings: 10+ hours/week saved per team member
Business Impact
- Sales: Faster proposal generation, higher win rates
- Delivery: Consistent quality, fewer errors
- Operations: Reduced manual work, better documentation
π¨ Common Pitfalls to Avoid
- Over-Engineering Early: Start simple, add complexity as needed
- Under-Documenting: Capture knowledge as you go, donβt wait
- Agent Scope Creep: Keep agents focused, create new ones for new functions
- Ignoring Quality: Review agent outputs, update knowledge from mistakes
- Siloed Knowledge: Share organizational memory, not just personal
- No Feedback Loops: Learn from agent performance, update patterns
π Current Focus & Next Steps
Current Sprint (2 Weeks): GTM agents ONLY
- See
GTM_AGENT_SPRINT.mdfor 2-week sprint plan - Focus: BDR tactics, outreach, qualification agents
After GTM Sprint:
- Expand to other domains (PM, content, ops) based on priority
- Scale systematically using learnings from GTM agents
- Build 20-30 agents over time, not all at once
π Learnings from Real-World Implementation
See: VERCEL_LEAD_AGENT_LEARNINGS.md for detailed learnings from Vercelβs $2M lead agent.
Key Takeaways:
-
Start Small, Prove Value Fast
- Build MVP in 1-2 days (weekend projects work!)
- Budget 3-5x more time for buy-in than building
- Use shadow mode in production to prove value
-
Two Types of Agents
- Efficiency Agents: Replace tedious work (keep human in loop)
- βShouldβ Agents: Do stuff that isnβt getting done (can fire by default)
-
Find Opportunities Using Drewβs Framework
Repetitive Task (100+ times/week) + High Business Impact + Tedious/Unfulfilling + Historical Data Available = Perfect Agent Opportunity -
Shadow Your Best People
- Watch what they actually do (revealed preference)
- Not what they say they do (stated preference)
- Document their tricks/optimizations
- Replicate the best behavior in agents
-
Prompt Structure Matters
- Put reasoning FIRST, decision LAST
- Forces βSystem 2β thinking (analytical) vs βSystem 1β (snap judgment)
- Improves accuracy significantly
Read the full learnings document for implementation details and code examples.
Remember: The goal isnβt to have 30 agents immediately. Itβs to systematically capture knowledge, build specialized agents, and compound your business intelligence over time. Every piece of knowledge you capture today makes tomorrowβs agents smarter.
Start Small, Think Big, Scale Systematically.