Sales & CRM

How to set up your first crm as Small Customer Success Teams

Sales & CRMFor Small Customer Success Teams2 apps12 steps~24 min to set up

Your team of three covers 250 B2B accounts. Account health lives in three places: HubSpot for the deals that made it into the CRM, Gmail threads for everything else, and a mental model that disappears when someone takes PTO. You spend the first 30 minutes of every QBR prep hunting down the last touch date, the open support tickets, and whether the account actually expanded last quarter or just renewed flat. Gainsight and Catalyst would solve this, but they cost more than your entire tooling budget and need a CS-ops person to stand up. So you're running custom HubSpot filters and praying the spreadsheet stays current.

Build this on Starch → See the apps used

Sales & CRMFor Small Customer Success Teams2 apps12 steps~24 min to set up

Outcome

What you'll set up

A CRM surface built around customer success workflows — health scores, last-touch tracking, expansion signals, and renewal dates — not a sales pipeline someone else designed

Live connections to HubSpot, Gmail, and Intercom so account context is in one place instead of three browser tabs

An automated QBR prep workflow that pulls deal history, email thread summaries, and open tickets for any account on demand

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

CRM Email Agent

Data sources & config

Starch syncs your Gmail data on a schedule (messages, thread history, labels) and syncs your HubSpot contacts, companies, and deals on a schedule. Intercom is connected from Starch's integration catalog and queried live when your app needs open ticket counts or conversation history. Google Calendar is synced on a schedule to track meeting cadence per account. Slack is synced on a schedule for the weekly digest delivery.

Prompts to copy

Build me a customer success CRM for 250 B2B accounts. I need fields for: account health score (red/yellow/green), renewal date, last customer touch date, expansion ARR opportunity, open support ticket count, and current onboarding stage. Group accounts by CSM owner. I want to be able to ask 'which accounts haven't had a touch in 45 days and are renewing in the next 90?' and get a real list.

Build me a QBR prep assistant. When I give it an account name, it should pull the last 6 months of email thread summaries from Gmail, the deal history from HubSpot, any open Intercom conversations, and draft a QBR agenda with a one-paragraph account summary, a health assessment, and 3 suggested talking points.

Set up an automated weekly digest every Monday morning that lists: accounts with no touch in 30+ days, accounts with open Intercom tickets older than 7 days, and accounts whose renewal date is within 60 days. Send it to our team Slack channel.

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

Walkthrough

Step-by-step

1 Connect HubSpot — Starch syncs your contacts, companies, deals, and deal owners on a schedule. Your existing account data imports in minutes; no field remapping required unless you want to clean up the structure.

2 Connect Gmail — Starch syncs your messages and thread history on a schedule. Every email thread tied to a customer domain gets associated with the right account automatically.

3 Connect Intercom from Starch's integration catalog. The agent queries it live when your CRM surface needs open ticket counts or conversation summaries — no manual export needed.

4 Connect Google Calendar — Starch syncs events on a schedule so last-meeting date is always current per account without anyone manually logging a touch.

5 Start the Starch CRM app and describe your CS-specific schema: health score tiers, renewal date, expansion ARR field, onboarding stage, and CSM owner. Starch builds the data model from your description.

6 Tell Starch to import your existing HubSpot accounts and map the fields you care about. It will flag duplicates and incomplete records so you can clean the list before it becomes a 250-account mess.

7 Add a calculated health score rule: tell Starch 'mark an account yellow if there's been no Gmail or Calendar touch in 30 days, or if there's an open Intercom ticket older than 5 days; mark it red if both are true or if renewal is within 45 days and health is yellow.'

8 Set up the Email Agent app and point it at your Gmail. Tell it to surface any email from a customer domain and tag threads by account. This gives you per-account email history inside your CRM without manually logging calls.

9 Build the QBR prep automation: describe the account name input, and have Starch pull Gmail thread summaries, HubSpot deal history, Intercom tickets, and calendar meeting count for the last 6 months, then draft a structured QBR agenda.

10 Build the Monday morning Slack digest automation. Tell Starch the three signals you want (no touch in 30 days, old open tickets, near-term renewals) and the Slack channel to post to. Schedule it weekly.

11 Set up a saved query called 'expansion candidates' — accounts that are green health, have been a customer for 6+ months, and haven't had an expansion conversation logged in the last quarter. Run it before your weekly team sync.

12 Share the CRM surface with your two teammates. Each CSM sees their own account view by default but can switch to full portfolio view. No admin configuration, no seat licenses to negotiate.

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 renewal sweep — 14 accounts due in 60 days

Sample numbers from a real run

Meridian Logistics	48,000
Tabletop Studio	22,500
Greyfield Analytics	36,000
Coastline HR	15,000
Northpoint Ops	60,000

It's April 7th. You have 14 renewals due before June 30 totaling $318,000 in ARR. In the old world, you'd spend a morning building a spreadsheet from HubSpot exports, Gmail searches, and Intercom's reporting tab. Instead, you run the 'renewal sweep' query in your Starch CRM: accounts renewing before July 1, sorted by health score. Northpoint Ops ($60,000) shows red — no touch in 52 days, two open Intercom tickets. You click into the account and see the last three Gmail threads: a billing question in February, an onboarding ask in March, no response to either. You run the QBR prep prompt for Northpoint and get a draft agenda in 40 seconds — the account summary notes the unanswered threads, the health assessment flags the ticket age, and the talking points suggest leading with the billing resolution before pitching the expansion seat package. Meridian Logistics ($48,000) shows green — your teammate had a call two weeks ago, one open ticket just closed, and Calendar shows a QBR already scheduled for May 12. You skip it and move to Tabletop Studio ($22,500), which is yellow: no meeting in 35 days but no open tickets. The Monday digest already flagged it. You send a check-in email directly from the Starch surface, logged against the account automatically.

Measurement

How you'll know it's working

Days since last customer touch per account (target: no account goes 30+ days without contact)

Renewal ARR at risk — total ARR of red and yellow accounts due in next 90 days

QBR completion rate — percentage of quarterly accounts with a completed QBR deck before the call

Expansion pipeline coverage — number of identified expansion opportunities vs. accounts in the portfolio

Average open Intercom ticket age across the book of business

Comparison

What this replaces

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

Gainsight or Catalyst

Full CS platforms with health scoring, playbooks, and timeline views, but they start at $40,000–$80,000/year and typically require a CS-ops implementation; your three-person team would spend months configuring it before seeing value.

HubSpot Service Hub

Extends your existing HubSpot investment into CS workflows, but health scores, renewal tracking, and QBR automation require the Enterprise tier and significant manual setup — you're still stitching it to Gmail and Intercom yourself.

Spreadsheet + HubSpot exports

Zero cost and you already know how, but the spreadsheet is stale the moment you close it, there's no automated touch-date tracking, and QBR prep still takes 45 minutes per account.

ChurnZero

Purpose-built for churn prevention with solid health score automation, but it's similarly priced to Gainsight and requires dedicated admin time — not built for a team that also handles renewals, onboarding, and support.

On Starch RECOMMENDED

One platform — crm, email 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 HubSpot. Does this replace it or sit on top of it?

Starch sits on top of HubSpot, not instead of it. Starch syncs your HubSpot contacts, companies, and deals on a schedule, so your existing data stays in HubSpot and your team keeps using whatever HubSpot workflows they already have. What Starch adds is the surfaces HubSpot doesn't ship for CS: the health score view, the QBR generator, the touch-date tracker. You're not migrating your CRM — you're building the CS layer on top of it.

Can Starch read our Intercom conversations to flag at-risk accounts?

Yes. Connect Intercom from Starch's integration catalog and the agent queries it live when your app needs ticket counts, conversation age, or open issue summaries. You can build a rule that marks an account yellow when there's an unresolved ticket older than 5 days, or ask 'which accounts have more than 2 open Intercom threads right now' and get a real list.

Is Starch SOC 2 certified? We have customers who ask about data security.

Starch is not currently SOC 2 Type II certified. It also has no on-premise or self-hosted option. If your customers require SOC 2 compliance from your internal tooling vendors, that's worth factoring in. For teams where that bar isn't required for internal CS tooling, Starch's data handling is otherwise standard SaaS.

Our Gmail threads have years of history. Will Starch sync all of it?

Gmail sync is capped at 30 messages per page to avoid errors on long HTML threads. For most CS workflows — tracking recent touches, drafting QBR summaries, surfacing unanswered threads — the recent history is what matters. If you need deep historical archives for compliance or audit purposes, Starch isn't built for that use case.

We track usage data from our product analytics tool. Can that feed the health score?

If your product analytics tool is reachable through Starch's integration catalog (tools like PostHog have a pre-built Starch connection), the agent can query it live when your health score app runs. If your tool isn't in the catalog, Starch can often automate pulling data through your browser — no API required. Tell Starch what you want included in the health score formula and it will build the data connections to support it.

How long does it actually take to go from zero to a working CS CRM?

Most teams are looking at a working first version in under a day. Connecting HubSpot and Gmail takes minutes. Describing your schema — health score tiers, renewal date, expansion fields — takes one prompt. The first import and field cleanup might take an hour if your HubSpot data has duplicates or gaps. The QBR automation and the weekly Slack digest are each one prompt to build and a few minutes to test. You're not configuring workflows in a UI — you're describing what you want in plain language and Starch builds it.