Model Context Protocol · Free
14
Delivery playbooks
95
Podcast episodes
7
Field studies
2,990
Searchable passages
Works with
The idea
What’s inside
Playbooks
14 delivery playbooks
The methodology, structured Blueprint → Build → Enable → Maintain. GTM Lifecycle, Market Map, Sales Territory Design, Lead Routing, Growth Model, Quote to Cash, CPQ, Attribution, Onboarding, CRM Migration, and the two automation playbooks.
Research
8 field studies
Built from LeanScale’s own delivery logs, call transcripts and shared channels across a panel of B2B software companies — not from a survey. GTM tech stacks, AI adoption in GTM, RevOps investment ratios, and the Series B/C fundraise clocks.
Interviews
95 podcast episodes
The LeanScale Podcast, fully structured — frameworks, verbatim quotes with timestamps, practical advice broken out by role, and the numbers guests actually cited. CROs, VPs of RevOps, founders.
Case studies
75 customer case studies, anonymized
The problem a company had and how it was solved. Customer names, people, third parties and delivery provenance are stripped out at build time, and each removal is marked. What’s left is the shape of the work, which is the part that transfers.
Named versions are internal-only
The tools
diagnose_gtm
search_leanscale
Search everything at once. Returns cited excerpts.
get_playbook
A full playbook, or one named section of it.
list_playbooks
Every playbook, by category, with its section headings.
get_benchmark
Proprietary benchmark data when the question is “what’s normal”.
search_podcast
Operator opinions, frameworks and quotes with timestamps.
about_leanscale
What LeanScale is and what this server can answer.
get_case_study
Anonymized customer case studies by sector or engagement type.
Try it
Get access
Personal addresses aren’t accepted. Gmail, Outlook, iCloud and the rest are rejected — this is built for teams, and knowing the company is the point.
What we log. Your key is tied to your name, company and email. Every tool call records which tool ran and the query text. That’s deliberate: it’s how we know what people are actually trying to solve.
What we don’t do. No mailing list, no drip sequence, no reselling. If something you ask looks like a problem we could help with, someone might reach out once.
Customer work is anonymized, not exposed. Case studies are stripped of names, people and third parties before they ever reach the corpus, and the build fails if any unrecognized proper noun survives. Named versions never leave a LeanScale key.
Install
Claude Code
Claude Desktop
ChatGPT
Cursor
VS Code
Gemini CLI
Once it’s connected