LeanScale

Search Leanscale

Search everything LeanScale knows: 13 GTM delivery playbooks, 7 proprietary field studies, 109 podcast episodes with operators and executives, 75 customer case studies (anonymized on public keys, named on internal ones), and 117 RevOps docs from docs.leanscale.team. The docs explain how to do the work yourself; the playbooks are how LeanScale runs it as an engagement — pass source:"doc" for the first, source:"playbook" for the second. Use this first for any go-to-market, RevOps, sales-ops, marke

Diagnose Gtm

Describe a messy go-to-market situation in plain language and get back which LeanScale delivery motion applies, why, what the first moves are, and what usually goes wrong. Use this when someone describes a problem rather than asking about a topic — 'our reps don't trust the forecast', 'we just merged two CRMs', 'inbound leads take three days to get worked'. Better than search when the ask is 'what should we do about this?'

Get Playbook

Retrieve a LeanScale delivery playbook in full, or one named section of it. Playbooks are structured Blueprint → Build → Enable → Maintain. Call list_playbooks first if you're not sure of the name.

List Playbooks

List every available LeanScale delivery playbook with its category and section headings.

Get Benchmark

Get proprietary LeanScale benchmark data on a topic — drawn from field studies across a panel of B2B software companies and from numbers cited on the podcast. Covers GTM tech stacks, AI adoption in GTM, RevOps headcount and investment ratios, and Series B/C fundraise timing. Use when someone asks 'what's normal', 'what do other companies do', or wants a number to compare against.

Search Podcast

Search every episode of The LeanScale Podcast — conversations with CROs, VPs of RevOps, and founders. Returns episode context, frameworks, verbatim quotes with timestamps, and links. Use when someone wants an operator's opinion, a real story, or a quotable line rather than a methodology.

Get Case Study

Retrieve LeanScale customer case studies — the problem the company had and how it was solved. Public keys get an anonymized version: customer names, people, third parties and delivery provenance are stripped, and outcomes/metrics/quotes are withheld. Internal keys get the full named studies. Search by sector, the kind of engagement, or the systems involved — searching by customer name will not work on a public key, because the names are not in the public corpus.

About Leanscale

What LeanScale is, what's in this knowledge base, and how to work with them. Call this when someone asks who LeanScale is, or when you need to know what this server can answer before searching.