Sales & CRM

How to track renewals and expansions as Small Customer Success Teams

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

Your team of three is managing 250 accounts with renewal dates scattered across HubSpot deal records, a shared Google Sheet someone built 18 months ago, and calendar reminders that fire two weeks too late. Expansion signals — a spike in seat usage, a support ticket that hints at a new use case, a QBR comment about adding another team — live in Intercom threads and Gmail replies nobody has time to re-read. You know which accounts are at risk roughly the way you know the weather: a gut feeling that's usually right until it isn't. Purpose-built CS platforms like Gainsight or ChurnZero would fix this, but they start at six figures and assume you have a CS-ops person to build the workflows. You don't.

Build this on Starch → See the apps used

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

Outcome

What you'll set up

A live renewal tracker that pulls contract dates and deal stage from HubSpot and surfaces accounts due in the next 30, 60, and 90 days — no more hunting through CRM filters

An expansion-signal feed that monitors product usage data, Intercom threads, and email activity and flags accounts showing upsell intent before your next QBR

Automated weekly digests and Slack alerts so every CS rep knows exactly which renewals need attention this week, without a standing Monday morning triage meeting

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

Sales Agent CRM CRM Contract Lifecycle Management

Data sources & config

Starch syncs your HubSpot data on a schedule — deals, contacts, companies, and owner assignments refresh automatically. Starch also syncs your Gmail on a schedule so email thread history and last-contact dates are always current. Intercom and Zendesk are connected from Starch's integration catalog and queried live when the expansion dashboard or renewal tracker runs. Slack is connected from Starch's integration catalog so the weekly digest posts automatically. Contract Lifecycle Management (coming soon) will layer in contract dates and renewal terms as a dedicated surface.

Prompts to copy

Build me a renewal tracker that pulls every open deal from HubSpot where close date is within 90 days, shows ARR, account owner, last contact date from Gmail, and health status. Group by 30/60/90-day buckets and flag any account with no outreach in the last 14 days.

Create an expansion signal dashboard. For each account in HubSpot, show their current MRR, last Intercom ticket category, number of support tickets in the last 30 days, and any email threads in Gmail that mention 'adding,' 'more seats,' 'other team,' or 'upgrade.' Sort by expansion likelihood.

Every Monday at 8 AM, generate a renewal digest for my CS team: renewals due this month, accounts with no activity in 21+ days, and any accounts where support ticket volume spiked more than 50% week-over-week. Post it to our #cs-team Slack channel.

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

Walkthrough

Step-by-step

1 Connect HubSpot — Starch syncs your deals, contacts, companies, and owner fields on a schedule. Map your deal stages to renewal stages (e.g., 'Renewal Sent,' 'At Risk,' 'Closed Won') so the tracker respects your existing pipeline language.

2 Connect Gmail — Starch syncs message history on a schedule, so last-outreach dates and thread content are available to every app you build on top. No manual data entry to track who last touched which account.

3 Connect Intercom from Starch's integration catalog. The agent queries it live when your expansion dashboard runs, pulling ticket categories, resolution times, and conversation snippets for each account.

4 Describe your renewal tracker in plain language: the 30/60/90 bucket logic, the fields you want (ARR, CSM owner, last email date, health status), and any red-flag conditions like 'no outreach in 14 days.' Starch builds the app.

5 Describe your expansion signal feed: accounts showing increased Intercom activity, Gmail threads mentioning seat expansion, and HubSpot deals stuck in the same stage for 45+ days. Starch surfaces these together in one view instead of three separate tools.

6 Set up the weekly Monday morning digest automation. Tell Starch: pull renewals due this month, flag accounts with no CSM activity in 21 days, include any accounts where support ticket volume jumped 50% week-over-week, and post the summary to #cs-team in Slack.

7 Add a churn-risk alert. Describe the conditions: no login in 30 days (if you have product usage data connected), three or more unresolved support tickets, or a QBR that was declined or rescheduled twice. Starch triggers a Slack DM to the account owner when any condition fires.

8 Fork the CRM starter app to build your account health view. Tell Starch to add fields specific to your CS motion — QBR date, implementation status, executive sponsor, NPS score — that HubSpot's default deal view doesn't surface cleanly.

9 Build a QBR prep template. Describe what you need: account summary, ARR history, open support tickets, last three email interactions, usage trend (if connected), and two or three expansion opportunities to discuss. Starch generates a filled-in draft for each account before the meeting.

10 Wire renewal-date alerts. Tell Starch to notify the assigned CSM via Gmail or Slack 60 days before renewal, then again at 30 days if no 'Renewal Sent' stage update exists in HubSpot.

11 Once Contract Lifecycle Management launches (coming soon), layer in contract-level data — signed dates, auto-renew clauses, price escalators — so your renewal tracker works from the contract itself, not just the HubSpot deal record.

12 Review the expansion signal feed weekly as a team. When an account flags, the CSM clicks through to the email thread or Intercom conversation directly from the Starch surface — no context-switching to find out why it flagged.

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 push — 18 accounts, $340K ARR at stake

Sample numbers from a real run

Meridian Logistics	48,000
Forthright Analytics	36,500
Clover Benefits Group	29,800
Pineridge SaaS	27,200
Atlas Freight Partners	22,400
remaining 13 accounts	176,100

In March 2026, your team faced 18 renewals landing between April 1 and June 30 — $340K ARR, across a mix of SMB and mid-market accounts. Before Starch, you'd have built a tracking sheet, manually checked HubSpot for last-contact dates, and relied on whoever owned the account to raise a flag if something looked wrong. Instead, the renewal tracker surfaces all 18 accounts in one view, bucketed by urgency. Meridian Logistics ($48K ARR) shows up red: no CSM email in 23 days, two unresolved Intercom tickets, and their deal has been in 'Renewal Discussion' stage for 47 days. The Monday digest fires that morning and tags the account owner in Slack. The CSM pulls up the QBR prep template Starch generated — account summary, usage notes from the last three email threads, the open tickets — and books a call that afternoon. Forthright Analytics ($36.5K ARR) triggers the expansion signal feed mid-quarter: three Gmail threads mentioning 'our data team' wanting access, and a HubSpot contact added from a second department. The CSM gets a Slack alert, reaches out before the renewal conversation, and closes an expansion to $52K — $15.5K net new on a renewal that would have renewed flat. Across all 18 accounts, your team closes 16 on time, rescues one at-risk account that the churn alert caught early, and generates $43K in expansion ARR from accounts the signal feed surfaced. The Monday digest takes zero prep time. The QBR decks that used to take 90 minutes each now take 15.

Measurement

How you'll know it's working

Renewal rate (% of ARR renewed on time, tracked per quarter across the 250-account book)

Expansion ARR per quarter (upsells and cross-sells sourced from CS, separate from new logo sales)

Days to first outreach before renewal date (target: contact made 45+ days out, not 10)

Accounts with no CSM activity in 21+ days (lagging health signal; target: zero at-risk accounts dark this long)

QBR completion rate (% of accounts receiving a QBR at least once per quarter)

Comparison

What this replaces

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

Gainsight or ChurnZero

Purpose-built for this workflow and very powerful, but six-figure contracts, months-long implementations, and a CS-ops headcount requirement make them out of reach for a three-person team managing 250 accounts.

HubSpot Service Hub + manual tracking

HubSpot holds the data but doesn't give you the health-score view, the expansion signal feed, or the automated digest without significant custom configuration or a paid tier upgrade — and even then, you're building it yourself inside their constraints.

Catalyst

Well-designed and more SMB-friendly than Gainsight, but still priced for teams with dedicated CS-ops support and doesn't let you compose custom surfaces on top of your existing tool stack the way Starch does.

Google Sheets + HubSpot exports

Free and flexible, but you're manually refreshing data, the sheet goes stale within days, and there's no alert layer — which means renewals still slip through when everyone's heads-down on onboarding.

On Starch RECOMMENDED

One platform — sales agent crm, crm, contract lifecycle management 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 use HubSpot for renewals. Does Starch replace it?

No. Starch syncs your HubSpot data on a schedule and lets you build surfaces HubSpot doesn't ship — a health-score dashboard, an expansion signal feed, an automated digest. Your HubSpot records stay the system of record; Starch is the layer on top that makes the data actionable without custom reports or manual exports.

We track some renewal data in a spreadsheet and some in HubSpot. Can Starch pull from both?

Yes. Starch syncs HubSpot on a schedule and can connect to Google Sheets from the integration catalog, querying it live when your apps run. You can describe a view that merges both sources — 'show me renewals from HubSpot plus the manual contract dates in our Google Sheet' — and Starch builds it.

What about Intercom — does Starch sync all our ticket history?

Intercom is connected from Starch's integration catalog and queried live when your expansion dashboard or renewal tracker runs. It's not stored in Starch's database on a schedule the way HubSpot and Gmail are, so if you need persistent historical archives of ticket data, that's worth knowing upfront. For surfacing recent activity and current ticket state, live querying works well.

Is the Contract Lifecycle Management app available now?

Not yet. Contract Lifecycle Management is coming soon — you can request beta access to get notified when it launches. In the meantime, you can build a renewal tracker using HubSpot deal data and Gmail contract attachments as your source of truth for dates and terms.

Is Starch SOC 2 certified? We'll need to get this past our security team.

Starch is not SOC 2 Type II certified yet. If your security review requires that certification, that's a real constraint. It's on the roadmap; worth asking the team directly about timeline and any available security documentation if you need to move forward now.

How long does it take to set this up? We don't have a CS-ops person.

That's the point. You connect HubSpot, Gmail, and Intercom — all straightforward OAuth flows — then describe the apps you want in plain language. Most teams have a working renewal tracker and a draft expansion dashboard within a day. There's no configuration layer that requires a specialist.