Playbooks — what the platform does for each team
One AI brain, four front doors (web, HubSpot card, Roam, Claude Code skills), over FCR’s full data. These playbooks frame the capabilities by who you are and what you’re trying to do — not by the tech.
Origin: the v1 “AI Advisor — one brain, two front doors” deck (April 2026, for Sales/AMs/CS/Campaign Managers). We’ve since shipped the HubSpot card, precomputed deal briefs, the maps/LRC stack, deal-pattern mining, and more — these playbooks fold the v1 patterns together with everything added since.
By team
Section titled “By team”| Team | Playbook | The headline use |
|---|---|---|
| Account Managers | account-managers/ | Instant account context, QBR/renewal prep, performance with caveats |
| Sales | sales/ | Cold-to-close prospecting — rank check, competitor ID, market intel, proposals — plus customer experience, retention & voice |
| Marketing, Product & GTM | marketing-product-gtm/ | Keyword KB, category intel, product portfolio, AI grounding, the listings GTM engine |
| Business Planning | business-planning/ | Revenue bridge, MRR/forecast, win-rate, portfolio economics |
| Operations | operations/ | Data syncs, deploys, monitoring, reconciliation |
The shared foundation (read once)
Section titled “The shared foundation (read once)”- How it all works:
../fcr-dashboard-architecture-overview.md - The four surfaces (incl. Claude Code skills): same doc, §2
- The AI advisor + gold-pattern prompts:
../AI_ADVISOR_GUIDE.md
These are first cuts — refine the framing per team as you use them.
Ask the docsRAG over this site
Ask anything about the FCR Dashboard platform — architecture, BigQuery, the worker routes, billing rules, the LRC stack, scoring… Answers are grounded in this documentation, with source links.
How does the deal-brief refresh work? Which routes are Worker vs n8n? How is account health scored?