Sales & CRM

How to create a sales enablement content library as Small Marketing Teams

Sales & CRMFor Small Marketing Teams3 apps12 steps~24 min to set up

Your team of three is the content department, the demand gen engine, and the sales enablement function rolled into one. Right now your sales enablement 'library' is a Notion folder nobody updates, a Google Drive full of decks with version numbers in the file name, and a Slack channel where reps ask 'do we have a one-pager for mid-market logistics companies?' and someone has to dig for 20 minutes. Meanwhile you're rebuilding the weekly pipeline-contribution report by hand — pulling HubSpot deals, cross-referencing GA4 sessions, eyeballing Meta Ads spend — and by the time it's done the numbers are already stale. There's no process for retiring outdated collateral, no way for a rep to know which case study closed the most deals in a given segment, and no single place where campaign messaging connects to what sales actually needs in the room.

Build this on Starch → See the apps used

Sales & CRMFor Small Marketing Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A structured, searchable content library that auto-categorizes sales assets by buyer stage, segment, and use case — so reps can find what they need without pinging you

An automated pipeline-contribution dashboard that joins HubSpot deal data with your ad spend and campaign activity, updated on a schedule without you touching a spreadsheet

A content performance tracker that flags which assets are being used, which deals they're associated with, and which ones haven't been touched in 90 days and should be retired or refreshed

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 Sales Agent CRM

Data sources & config

Starch syncs your HubSpot data on a schedule (contacts, companies, deals, and owners) and syncs Gmail so content usage mentioned in email threads surfaces in the library. Connect Google Analytics 4, Meta Ads, Google Ads, and LinkedIn Ads from Starch's integration catalog — the agent queries them live when your pipeline-contribution report runs. Connect Notion from Starch's integration catalog to pull existing docs and pages into the knowledge base as the starting corpus. Any content hosted on internal portals or vendor sites that lack an API can be pulled by Starch through browser automation — no API needed.

Prompts to copy

Build me a sales content library organized by buyer stage (awareness, consideration, decision), segment (SMB, mid-market, enterprise), and content type (case study, one-pager, deck, email template). Each asset should have a last-updated date, a 'used in deal' counter pulled from HubSpot, and a status flag (active, needs refresh, retired).

Create a weekly pipeline-contribution report that pulls HubSpot deals created and closed this week, joins them against campaign activity and content engagement, and shows me which marketing touchpoints appeared in deals that moved stages. Send it to me and the VP of Sales every Monday at 8am.

Build a content request tracker for sales reps — a simple form where they can submit 'I need a case study for X industry' or 'the competitive one-pager is outdated,' which feeds a prioritized queue my team reviews weekly.

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

Walkthrough

Step-by-step

1 Connect HubSpot as a scheduled-sync provider. Starch will pull deals, contacts, companies, and owners on a recurring schedule — this becomes the backbone of your content performance attribution.

2 Connect Notion from Starch's integration catalog. The agent pulls your existing pages and databases into the knowledge base so you're not starting with an empty library.

3 Connect Gmail so Starch can cross-reference email threads with deals — when a rep sends a case study to a prospect, that touch shows up against the deal in HubSpot.

4 Connect Google Analytics 4, Meta Ads, and LinkedIn Ads from Starch's integration catalog. These feed the pipeline-contribution dashboard with campaign spend and traffic context.

5 Open the Knowledge Management app and tell Starch how you want the library structured: buyer stage, segment, content type, asset status. Starch builds the schema and auto-categorizes your imported Notion content into it.

6 For any content living on Google Drive or internal portals without an API, Starch automates retrieval through your browser — no API needed — and imports it into the library with the same categorization logic.

7 Set up the 'used in deal' counter by telling Starch: 'Track which library assets appear in HubSpot deal notes, email threads, or manual rep tags, and show the count on each asset card.' The agent wires the HubSpot sync to the library automatically.

8 Build the pipeline-contribution dashboard with a natural-language prompt. Starch joins HubSpot deal data against GA4 sessions, ad spend from Meta and LinkedIn, and content engagement — no BI tool required.

9 Set up the content-staleness automation: 'Flag any asset that hasn't been tagged in a deal or touched by a rep in 90 days. Send me a weekly digest with the flagged assets and a suggested action: refresh or retire.'

10 Build the sales content request queue — a lightweight form app where reps submit requests. Starch routes submissions into a prioritized list your team reviews in the weekly content planning meeting.

11 Schedule the weekly pipeline-contribution report to send every Monday morning to you, the VP of Sales, and anyone else who needs it — no manual export, no Google Sheets formula rebuilding.

12 Publish the content library link to your sales Slack channel and tell reps how to search it. The AI search in Knowledge Management means they can type 'case study for manufacturing mid-market' and get results instantly, instead of asking you.

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

Q2 2026 Sales Enablement Audit — April Week 2

Sample numbers from a real run

HubSpot deals created in April (synced)	34
Assets tagged in closed-won deals (trailing 90 days)	11
Assets flagged as stale (no deal touch in 90 days)	23
Content requests from reps in queue	7
Hours saved on weekly pipeline-contribution report (estimated)	3

Coming into April, your Notion content folder had 47 assets — decks, one-pagers, case studies — but there was no way to know which ones were actually moving deals. After connecting HubSpot and building the library in Starch, you can see that 11 assets have been tagged in closed-won deals over the past 90 days, and 5 of those were the same two case studies (one for logistics, one for SaaS). Twenty-three assets haven't been touched by a rep or associated with a deal in over 90 days — the auto-flagging automation surfaces these every Monday, and your team decides to retire 14 and refresh 9. The pipeline-contribution dashboard now shows that the LinkedIn Ads campaign driving the most stage-2-to-3 movement is the one tied to the logistics case study, not the brand awareness creative you thought was working. That's the brief you take to the CEO when MQL volume looks soft — you have the data to show which content-campaign combinations are actually converting, not just which ones are getting clicks. The weekly report went from 2.5 hours of manual spreadsheet work to a scheduled Starch automation that delivers to Slack at 8am Monday.

Measurement

How you'll know it's working

Content asset utilization rate: % of library assets tagged in at least one HubSpot deal in the trailing 90 days

Pipeline-influenced revenue by campaign: HubSpot closed-won deals where a tracked marketing touchpoint appeared, broken out by channel

Content request resolution time: average days from rep request submission to new or refreshed asset published in the library

Asset staleness rate: % of library flagged as not touched in 90+ days, reviewed monthly

Sales rep self-service rate: % of weeks with zero 'do we have a one-pager for X?' messages in Slack — a proxy for library discoverability

Comparison

What this replaces

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

Notion alone (your current state)

Notion stores the content but has no connection to HubSpot deal data, no staleness detection, and no way to surface which assets are actually closing business — you're still doing that analysis by hand.

Highspot or Seismic

Purpose-built sales enablement platforms with strong rep-facing UX, but they start at prices that don't make sense for a 120-person company with a 3-person marketing team, and they require dedicated admin time to configure and maintain.

HubSpot Content Hub

Stays inside the HubSpot ecosystem which is good for deal attribution, but you'd need to migrate all your content there, it doesn't pull in GA4 or ad spend natively without additional HubSpot tiers, and customizing the library structure requires HubSpot admin access your team probably doesn't own.

Google Drive + manual Sheets reporting

Free and familiar, but the weekly pipeline-contribution report still takes 2-3 hours to rebuild, there's no automated staleness flagging, and reps still have to know what to search for — discoverability doesn't improve.

Looker Studio (formerly Google Data Studio)

Good for building the pipeline-contribution dashboard if you have someone who knows it, but it doesn't give you the content library, the request queue, or the staleness automation — you'd still need separate tools for each piece.

On Starch RECOMMENDED

One platform — knowledge management, crm, sales agent crm 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

Does Starch actually store and host our content files, or just index them?

Starch indexes and organizes your content metadata — titles, tags, deal associations, status flags, last-touched dates — and pulls content from where it already lives (Notion, Google Drive via the integration catalog, or any web-accessible location via browser automation). It's a structured layer on top of your existing storage, not a replacement for it. You keep files where they are; Starch makes them findable and trackable.

Our HubSpot data is messy — deals in weird stages, inconsistent contact records. Will that break the library attribution?

It'll affect attribution quality, not break it. Starch syncs the deal and contact data as-is and builds the pipeline-contribution view from what's there. The CRM app can help you clean up deal stages and field consistency as a parallel workstream — tell Starch 'show me all deals with no close date set and no associated contact' and you get an actionable cleanup list. Better HubSpot hygiene improves the attribution picture over time.

Can reps outside our marketing team actually use the content library, or is this more of an internal marketing tool?

The library is designed to be rep-facing. The AI search in the Knowledge Management app means a rep can type a plain-English query — 'case study for a 50-person logistics company in the Midwest' — and get relevant results without needing to know how your folder structure works. The content request queue is also built for reps: they submit what they need, marketing triages it, and the rep gets notified when it's ready.

Is Starch SOC 2 certified? Our IT team will ask.

Not yet — Starch is not currently SOC 2 Type II certified. If that's a hard requirement for your procurement process, it's worth flagging upfront. It's on the roadmap but not available today.

We use Customer.io for email nurture. Can Starch pull campaign engagement data into the pipeline-contribution report?

Yes — connect Customer.io from Starch's integration catalog and the agent queries it live when your report runs. You can include email open rates, click-throughs, and sequence engagement alongside HubSpot deal data and ad spend in the same dashboard. Same approach works for Mailchimp or Klaviyo if you switch ESPs.

What happens to the library if we update a doc in Notion or Google Drive? Does Starch know?

For Notion, Starch queries your pages live from the integration catalog, so updates appear when the relevant app or dashboard refreshes. For Google Drive, the same live-query pattern applies. The staleness flagging is based on deal-touch activity and rep usage tracked inside Starch — it won't auto-detect a file edit in Drive, so your team would manually update the 'last refreshed' status on an asset when you revise it. That takes about 10 seconds and is part of the weekly content review habit the queue helps establish.