🔧 GTM Playbook
How to build a knowledge agent for your sales team
A practical guide for enablement and GTM leaders. What it is, what tools you need, who's involved, and a 10-week timeline to get it live.
What we're building
The Knowledge Agent
An internal tool your sales reps can talk to in plain language. They ask questions, and it answers using your company's actual data: your product docs, your competitive positioning, your pricing, your deal context, your messaging frameworks.
It sits on top of everything your enablement team has already built and makes it instantly accessible. Instead of a rep digging through folders, searching Slack, or pinging enablement and waiting, they ask the agent and get an answer in seconds, tailored to their deal.
What it does
Answers rep questions using your internal knowledge, product docs, competitive intel, and deal context. In seconds.
What it replaces
Searching Drive folders, pinging Slack channels, emailing enablement, reading 40-page docs to find one paragraph.
What it doesn't
Human judgment, relationship building, live coaching, navigating procurement rooms, in-person enablement.
The tools you need
Six components. Some you likely already have. Here's what each one does in the system.
Claude
The Brain
Anthropic's LLM. The reasoning engine that reads your data, understands rep questions, and generates contextual answers. Handles the thinking.
MCP
The Wiring
Model Context Protocol. An open standard from Anthropic that lets Claude connect directly to external data sources. Think of it like USB for AI. One standard, many connections.
Notion
The Knowledge Base
Where enablement maintains the curated context: messaging frameworks, competitive positioning, objection handling, vertical playbooks. The source of truth the agent draws from. This is where enablement becomes agent architect.
Google Drive
The Asset Library
Where your raw sales assets live. Battle cards, pitch decks, pricing sheets, product docs, case studies. The agent searches and reads these alongside the Notion knowledge base.
Salesforce
The Deal Context
Account info, pipeline stage, deal value, activity history, contact roles. This is what makes the agent's answers specific to the rep's deal, not generic.
Slack
The Interface
Where reps interact with the agent. They DM it or mention it in a channel. Also a data source: recent deal room discussions and team conversations the agent can reference.
How the pieces connect
💬 Rep asks question in Slack
🧠 Claude determines what info is needed
MCP calls the right data sources
Notion
Curated knowledge
Google Drive
Raw assets
Salesforce
Deal context
Slack
Team discussions
✅ Synthesized answer back in Slack, with sources
What it looks like in practice
Four real scenarios showing how the agent shows up for reps.
Competitive call prep
I have a call with Acme Corp tomorrow. They're evaluating us against Competitor X. What's our latest positioning and what objections should I be ready for?
Pulls the latest battle card from Drive, checks Notion for the current messaging framework against Competitor X, and looks at the Salesforce record to see Acme is a mid-market healthcare company in evaluation stage. Returns tailored positioning for healthcare mid-market, the three objections they'll likely hear, and how top reps handle each one.
Mid-deal feature question
Prospect just asked if we support SAML SSO for enterprise. Is that on the roadmap?
Checks the product roadmap in Drive and product updates in Notion. Returns: "SAML SSO is on the roadmap for Q3, currently in design review. Here's the approved language product marketing has sanctioned for discussing unreleased features."
New rep onboarding into a vertical
I'm new and assigned to financial services. Walk me through our value prop for finserv and what resonates with those buyers.
Pulls the finserv vertical playbook from Notion, recent case studies from Drive, and deal notes from closed-won finserv opportunities in Salesforce. Returns the core value prop, pain points that resonate, proof points from recent wins, and how the top finserv rep sequences outreach.
Lost deal feeding the coaching layer
I just lost the Initech deal at procurement. We keep losing at procurement. What are top closers doing differently at that stage?
Returns the procurement navigation guide from Notion and tips from recent deal reviews. Also flags: "You're the third rep this month to lose at procurement. Flagging this pattern to the coaching agent for team-wide analysis." Suggests connecting with a senior rep who has a strong close rate at that stage.
Who needs to be involved
Five roles across the build and ongoing operation. Not five new hires. These are people already on your team wearing a new hat for 10 weeks.
Enablement Lead
Owns the Notion knowledge base. Defines messaging and quality standards. Reviews agent usage. Identifies gaps. This is the agent architect.
Developer / Contractor
Builds MCP servers, Slack bot, manages infrastructure. 40-80 hours for setup using existing MCP implementations. Then light maintenance.
IT / Security
Reviews data access controls. Approves Salesforce integration. Defines field-level permissions. Ensures compliance. Critical from Phase 1.
Salesforce Admin
Configures API access. Defines which fields the agent can read. Sets up role-based access so reps see only their own deal context.
Sales Leadership
Champions adoption. Selects the 5-10 rep beta group. Provides feedback. Sets the expectation that this is how the team will work going forward.
The 10-week timeline
A working v1 with Notion + Google Drive + Slack can be live in 5-7 weeks. Full Salesforce integration takes it to 10. This is not a 6-month project.
1
Weeks 1-3
Build the knowledge base in Notion
Create the structured workspace: messaging frameworks, competitive intel (one page per competitor), product knowledge, top objection handling, vertical playbooks, pricing and packaging, process guides for procurement and security reviews. Start with the 80/20: competitive intel, objections, and core messaging.
Enablement lead + one ops person
2
Weeks 3-5
Connect Claude to Google Drive + Notion via MCP
Set up MCP servers for Google Drive (read access to sales content folders) and Notion (read access to knowledge base). Configure Claude API access. Test basic Q&A flows. Anthropic provides SDKs in Python and TypeScript. The community has existing implementations for both Google Drive and Notion.
Developer + enablement (to define access) + IT/security
3
Weeks 5-7
Build the Slack interface + private beta
Build a Slack bot that accepts natural language questions, routes them to Claude with the MCP connections, and returns responses with source attribution. Start with a private beta of 5-10 reps. Their questions and feedback shape the knowledge base and agent behavior.
Developer + sales leadership (selects beta group)
4
Weeks 7-10
Connect Salesforce context
Set up a Salesforce MCP server for account records, opportunity records, and activity history. This makes the agent deal-aware. Define field-level permissions and role-based access. Audit logging for compliance. This is where IT/security involvement is most critical.
Developer + SF admin + IT/security
5
Week 10+
Review, iterate, expand
Enablement's new operating rhythm. Weekly review of what reps are asking. Identify gaps. Update Notion. Track adoption. Feed patterns to coaching. Expand access. The system gets smarter because enablement keeps improving the context.
Enablement lead, 2-4 hours/week
The feedback loop that makes it smarter
1Reps ask questions through the agent
2The agent answers using Notion, Drive, and Salesforce context
3Enablement reviews what's being asked and where the agent struggles
4Enablement updates the Notion knowledge base to fill gaps
5The agent immediately reflects those improvements
6Patterns get flagged to coaching for targeted intervention
7Repeat. Every cycle, the system gets tighter.
The enablement team of the future has two jobs: manage the context that powers the agents and drive the human-to-human connection that closes deals. Everything else gets automated.
🛠️
Would you build this?
If you run enablement or GTM ops, I'd love to hear what's stopping you, or what you'd add.