LeanScale GTM Knowledge

Working · 2.8 s

team.leanscale/gtm-knowledgev0.1.0 Domain verified

GTM operations knowledge: delivery playbooks, field studies, benchmarks and operator interviews.

Sales & CRM

Source Website Registry entry

Maintain this server? Claim it

Try it

Call this server's tools from your browser. Nothing to install.

https://mcp.leanscale.team/mcp

Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.

Tool list from our last check. Connect live to refresh it.

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.

This tool takes no arguments.

This tool isn't marked read-only, so it may change something on the server or in an account you connected.

I understand, run it anyway

Tools (8)

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.

No arguments.

Input schema (JSON)

{
  "type": "object",
  "properties": {}
}

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?'

Argument	Type	Description
situation*	string	The situation, in as much detail as you have. Symptoms, stack, team size, stage — all useful.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "situation"
  ],
  "properties": {
    "situation": {
      "type": "string",
      "description": "The situation, in as much detail as you have. Symptoms, stack, team size, stage — all useful."
    }
  }
}

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.

Argument	Type	Description
topic*	string	The metric or area, e.g. 'RevOps headcount ratio', 'CRM adoption', 'time to Series B'.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "topic"
  ],
  "properties": {
    "topic": {
      "type": "string",
      "description": "The metric or area, e.g. 'RevOps headcount ratio', 'CRM adoption', 'time to Series B'."
    }
  }
}

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.

Argument	Type	Description
limit	integer	Default 3.
query*	string	Sector, type of engagement, or systems involved — e.g. 'fintech Salesforce migration', 'CPQ replacement', 'two CRMs after an acquisition'.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1,
      "description": "Default 3."
    },
    "query": {
      "type": "string",
      "description": "Sector, type of engagement, or systems involved — e.g. 'fintech Salesforce migration', 'CPQ replacement', 'two CRMs after an acquisition'."
    }
  }
}

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.

Argument	Type	Description
name*	string	Playbook name, e.g. 'Attribution', 'CPQ', 'Sales Territory Design'.
section	string	Optional section, e.g. 'Blueprint'. Omit for the whole playbook.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Playbook name, e.g. 'Attribution', 'CPQ', 'Sales Territory Design'."
    },
    "section": {
      "type": "string",
      "description": "Optional section, e.g. 'Blueprint'. Omit for the whole playbook."
    }
  }
}

list_playbooks

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

No arguments.

Input schema (JSON)

{
  "type": "object",
  "properties": {}
}

search_leanscale

Search everything LeanScale knows: 14 GTM delivery playbooks, 7 proprietary field studies, 143 podcast episodes with operators and executives, 75 customer case studies (anonymized on public keys, named on internal ones), and 117 RevOps docs from www.leanscale.team/knowledge/docs/. 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, marketing-ops, CRM, pipeline, attribution, territory, CPQ, or GTM-tooling question. Returns cited excerpts with source URLs. Also holds the materials from LeanScale's talks, which people ask for by event name: Updata CEO Summit materials: the deck with speaker notes (The Context Graph & Semantic Layer); Updata CEO Summit materials: GTM agents (11 Claude Code plugins for your CRM); Updata CEO Summit materials: metric definitions worksheet (40 GTM definitions); Updata CEO Summit materials — The Context Graph & Semantic Layer. Pass source:"resource" to search only those.

Argument	Type	Description
limit	integer	How many excerpts to return (default 6).
query*	string	What you want to know. Natural language works better than keywords.
source	string	Restrict to one kind of source. Defaults to searching everything.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "How many excerpts to return (default 6)."
    },
    "query": {
      "type": "string",
      "description": "What you want to know. Natural language works better than keywords."
    },
    "source": {
      "enum": [
        "playbook",
        "study",
        "podcast",
        "case_study",
        "doc",
        "resource",
        "any"
      ],
      "type": "string",
      "description": "Restrict to one kind of source. Defaults to searching everything."
    }
  }
}

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 — including the episode on YouTube when there is a video. Use when someone wants an operator's opinion, a real story, or a quotable line rather than a methodology.

Argument	Type	Description
limit	integer	Default 6.
query*	string	Topic, guest name, company, or idea.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "Default 6."
    },
    "query": {
      "type": "string",
      "description": "Topic, guest name, company, or idea."
    }
  }
}