1Learn
From tool to product
Secrets and API-key hygiene. Auth. Permissions. What 'production-grade' means at a 15-person fund — boring reliability, not scale.
5
FIRM-WIDE IMPACT
Multiplier
Your tools aren't yours anymore — the firm runs on them. You think about security, other users, and enablement.
01 — Modules
2Apply
Multi-user systems
Shared infrastructure. An internal MCP server or plugin for the firm. Onboarding colleagues. Support burden as a design constraint.
3Extend
Enablement & governance
A firm AI policy people actually follow. Measuring adoption — the fluency ladder as internal metric. Running an internal workshop. Deciding build vs. buy.
02 — Tool belt
- ▸Deployment platform of choice
- ▸Secrets management
- ▸Internal MCP server / plugin
- ▸Usage analytics (even crude)
03 — Say it out loud
Terms you should be able to explain to a colleague.
- production vs. prototype
- least-privilege access
- context layer
- adoption vs. capability gap
04 — VC playbook
- 01Firm-wide sourcing / monitoring system with per-partner views
- 02Shared context layer: fund thesis, portfolio data, past memos available to every seat's Claude
- 03Internal plugin bundling the firm's skills and connectors
- 04Internal AI onboarding curriculum for new joiners (meta: this curriculum, localized)
Checkpoint challenge
Force Multiplier
Ship: (1) a system 3+ colleagues use weekly without your help, and (2) evidence you've moved one colleague up a full ladder level. Impact over code.
Sign up to work through this→