Sales & CRM

How to create a sales enablement content library as Small Customer Success Teams

Sales & CRMFor Small Customer Success Teams3 apps11 steps~22 min to set up

Your three-person team supports 250 B2B accounts, and every time a rep asks for battle cards, case studies, or onboarding guides, someone has to dig through a Google Drive folder that was last organized in 2023. New CSMs spend their first two weeks asking where things live instead of actually onboarding customers. QBR prep means copy-pasting the same product-usage talking points into a deck for the fifteenth time. The content that should be helping your team move faster — objection handlers, expansion playbooks, renewal scripts — is scattered across Notion pages, Slack threads, and someone's personal Drive. You don't have a Sales Enablement Manager. You have a CS team that's also doing that job.

Build this on Starch → See the apps used

Sales & CRMFor Small Customer Success Teams3 apps11 steps~22 min to set up

Outcome

What you'll set up

A searchable content library built on the Knowledge Management app, where onboarding guides, QBR templates, renewal scripts, and expansion playbooks are organized and surfaced by AI so any CSM can find the right asset in under 30 seconds

An automated QBR deck workflow that pulls account health signals from HubSpot and usage data so your team stops copy-pasting the same slides every quarter

A lightweight intake process that captures new content (call recordings, Slack answers, customer emails) and routes it into the library automatically, so the library actually stays current

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Knowledge Management CRM Presentation Agent

Data sources & config

Starch syncs your HubSpot data on a schedule — contacts, companies, deals, and activity history — so the CRM app and QBR deck workflow always reflect current account state. Notion is connected via scheduled sync, so existing documentation is pulled in and kept current without manual imports. Intercom and Zendesk are reachable by connecting them from Starch's integration catalog; the agent queries them live to surface common support questions that should become knowledge base entries. Gmail is synced on a schedule, so email threads with customers can be referenced when building or updating content.

Prompts to copy

Build me a customer success content library organized by lifecycle stage: onboarding, QBR, expansion, renewal, and churn risk. Each section should have a searchable index of guides, templates, and playbooks. Flag any document that hasn't been updated in 90 days.

Create a QBR deck template for a mid-market SaaS account. Pull the account's deal stage, last activity date, and open tasks from HubSpot, and leave placeholder slots for product usage metrics and NPS score. Output a 10-slide deck I can export to PowerPoint.

Build me an onboarding knowledge base that answers the 20 most common questions new customers ask in their first 60 days. Connect it to our Notion workspace so I can pull in existing docs without rewriting them.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect HubSpot to Starch — Starch syncs your contacts, companies, deals, and owner data on a schedule. This is the backbone for any account-specific content like QBR decks or renewal playbooks.

2 Connect Notion to Starch via scheduled sync. Any existing documentation — onboarding guides, playbooks, SOPs — gets pulled into Starch's knowledge layer so you're not starting from zero.

3 Connect Intercom from Starch's integration catalog. Starch queries your support ticket history live to identify the 10-20 questions customers ask most often in their first 60 days — these become your first knowledge base entries.

4 Start the Knowledge Management app and describe your library structure in plain language: 'Organize our CS content by lifecycle stage — onboarding, QBR prep, expansion plays, renewal scripts, and churn risk responses. Pull in our existing Notion docs and flag anything older than 90 days.'

5 Walk through the AI-generated index and correct any miscategorization. Add the content your team has been keeping in personal Drive folders or Slack bookmarks — describe it conversationally and Starch formats and categorizes it.

6 Set up an intake automation: 'Every Friday, pull the five most-answered Intercom tickets from this week, summarize the resolution, and add them to the onboarding FAQ section of the knowledge base if they're not already covered.'

7 Build a QBR deck workflow using the Presentation Agent. Describe: 'Build a 10-slide QBR template for a B2B SaaS account. Slide 1 is account health summary pulling from HubSpot deal stage and last activity. Slides 2-4 are usage highlights with placeholder charts. Slide 8 is the renewal or expansion ask.' The Presentation Agent is currently in beta — request access to get notified when it launches.

8 Wire the CRM app to auto-populate account context into QBR decks. When a CSM opens the QBR template for a specific account, HubSpot data fills the account health fields automatically — no copy-pasting deal stages or contact names.

9 Build an expansion playbook section: 'Show me all accounts in HubSpot with deal stage Closed-Won in the last 12 months, more than 3 active contacts, and no expansion opportunity logged. Format them as a prioritized list with last activity date and account owner.'

10 Set up a stale-content alert: 'Every month, show me every knowledge base document that hasn't been updated in 90 days, and list which CSM was last responsible for it.' This keeps the library from becoming another abandoned Google Drive.

11 Publish the library URL to your team's Slack and set it as the first link in your new CSM onboarding checklist. Measure time-to-first-value for new hires — the target is that they can answer a customer question without asking a colleague within their first week.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Q1 2026 QBR Sprint — 12 Accounts in 4 Days

Sample numbers from a real run

Meridian Logistics	48,000
Volta Software	36,000
ClearPath HR	27,500
Irongate Capital	22,000
Sable Retail Group	19,500

Your team has 12 QBRs due in the first two weeks of Q1. Last quarter, each deck took 3-4 hours to build: pulling usage stats from one tab, copying deal notes from HubSpot in another, reformatting the same slides for each account. This quarter, the QBR workflow is live. For Meridian Logistics ($48K ARR, renewal in March), a CSM types: 'Build a QBR deck for Meridian Logistics. Pull their HubSpot deal stage, last activity date, and open tasks. Flag that their renewal is in 47 days and that their main contact, Dana Reyes, hasn't logged in since December.' Starch pulls the HubSpot data it syncs on a schedule, pre-fills the account health slide, and generates a 10-slide draft in minutes. The CSM spends 20 minutes customizing talking points instead of 3 hours building from scratch. Across 12 accounts totaling roughly $153,000 in ARR, the team completes QBR prep in 4 days instead of the usual 8 — and three decks surface expansion signals (Volta Software, $36K, is running two departments on the free tier) that get added to the expansion pipeline the same week.

Measurement

How you'll know it's working

Time-to-QBR-deck: hours per account from kickoff to final draft

New CSM time-to-first-independent-customer-answer: days from start date

Knowledge base coverage: percentage of top 20 recurring Intercom questions documented

Expansion pipeline sourced from content-identified signals: number of accounts and ARR

Renewal prep completion rate: percentage of upcoming renewals with a QBR deck filed 10+ days before the call

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Gainsight or Catalyst

Purpose-built for CS ops teams with a six-figure budget and a dedicated admin to configure it; if you're three people covering 250 accounts without a CS-ops hire, you'll spend more time configuring the tool than using it.

Notion + Google Drive (manual)

Free and flexible, but the library doesn't self-organize, nothing alerts you when docs go stale, and QBR prep is still all manual copy-paste — Starch automates the parts that eat your Friday afternoons.

Guru or Confluence

Good searchable wikis, but they don't connect to HubSpot or your support inbox to generate content automatically or pull live account context into QBR decks.

ChatGPT or Claude (standalone)

Useful for drafting individual documents, but no persistent library, no HubSpot sync, no automated intake from Intercom tickets — you're still doing all the organizing and updating manually.

On Starch RECOMMENDED

One platform — knowledge management, crm, presentation agent all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

We already have Notion. Do we have to move everything out of it?

No. Starch connects to Notion via scheduled sync and pulls your existing pages and databases into the knowledge layer. You can keep Notion as the source of truth for writing and editing while Starch makes the content searchable and surfaceable from inside your CS workflows.

Will this actually stay current, or will it become another outdated wiki in six months?

The stale-content detection in the Knowledge Management app is what prevents that. You set the threshold — for example, flag anything not updated in 90 days — and Starch surfaces those items on a schedule so someone on your team can decide whether to update or retire them. You still need a human to make the call; Starch just makes sure nothing quietly rots.

Can Starch pull usage data from our product analytics tool directly into QBR decks?

If your product analytics tool (PostHog, Mixpanel, Amplitude, etc.) is reachable from Starch's integration catalog of 3,000+ apps, the agent can query it live when the QBR workflow runs. If it's not in the catalog, Starch can automate it through your browser — no API needed. The honest answer: you'll want to verify your specific tool is reachable when you set this up. The Growth Analyst app (which connects to PostHog) is a good starting point if PostHog is your stack.

Is Starch SOC 2 Type II certified? We have enterprise customers who'll ask.

Not yet. Starch is not SOC 2 Type II certified today. If your enterprise customers have strict compliance requirements that mandate SOC 2 Type II, that's worth weighing honestly. It's on the roadmap.

The Presentation Agent sounds useful for QBR decks — is it available now?

The Presentation Agent is currently in development. You can request beta access to get notified when it launches. In the meantime, the QBR workflow can generate structured content and talking points that you paste into your existing deck template — it's not as automated as the full Presentation Agent will be, but it still cuts prep time significantly.

We use Zendesk, not Intercom. Does that work?

Yes. Connect Zendesk from Starch's integration catalog; the agent queries your ticket history live. The intake automation that surfaces recurring questions and routes them to the knowledge base works the same way regardless of whether you're on Zendesk or Intercom.