Internal Comms & Meetings

How to run a monthly business review as Small Customer Success Teams

Internal Comms & MeetingsFor Small Customer Success Teams3 apps11 steps~22 min to set up

Your three-person team covers 250 accounts and every Monthly Business Review is assembled by hand. You pull usage data from your product analytics tool, open tickets from Intercom or Zendesk, deal stage updates from HubSpot, and email threads from Gmail — then spend half a day stitching them into a slide deck or a shared doc that's already stale by the time leadership reads it. The tools built for this workflow — Gainsight, Catalyst, ChurnZero — start at six figures and assume a dedicated CS-ops person who doesn't exist on your team. So the MBR either doesn't happen, or it happens late, or it's a screenshot dump that nobody acts on.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small Customer Success Teams3 apps11 steps~22 min to set up

Outcome

What you'll set up

A live account health dashboard that pulls HubSpot deal data, Intercom support volume, and Gmail thread history into one surface — so your MBR starts with current numbers, not last week's export

An automated MBR narrative generator that writes the account-by-account summary, flags churn risk signals, and highlights expansion opportunities based on the data it already has

A recurring delivery workflow that packages the review into a shareable format — slides, doc, or Slack summary — and sends it to the right internal stakeholders on whatever cadence you set

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 Investor Reporting Presentation Agent

Data sources & config

Starch syncs your HubSpot data on a schedule (contacts, companies, deals, owners). Connect Intercom from Starch's integration catalog — the agent queries it live when the health dashboard runs. Starch syncs your Gmail data on a schedule for account thread history. Connect Slack from Starch's integration catalog for the automated Slack delivery. The Presentation Agent builds the deck from the data Starch has already pulled — no separate export needed.

Prompts to copy

Build me a monthly account health summary app. Pull deal stages, last activity date, and owner from HubSpot. Pull open ticket count and average first-response time from Intercom for each account. Pull the last three email threads per account from Gmail. Flag any account with no activity in 30 days, more than 3 open tickets, or a deal that hasn't moved in 45 days as 'at risk.' Show me a sortable table grouped by risk level.

Every first Monday of the month, generate a written MBR narrative. For each at-risk account, write two sentences: what the signal is and what we should do this week. For each expansion-ready account — deals in 'Negotiation' or 'Closed Won' with upsell tags in HubSpot — write one sentence on the opportunity. Format it as a Slack message I can paste into #cs-team.

Build me a 10-slide Monthly Business Review deck. Slide 1: total accounts, at-risk count, expansion pipeline value from HubSpot. Slides 2-8: one slide per at-risk account with the risk signal, open ticket count, and recommended action. Slide 9: expansion opportunities with deal value. Slide 10: renewal forecast for next 60 days.

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. This is the spine of your account health view; every account in your MBR traces back to a HubSpot record.

2 Connect Intercom from Starch's integration catalog. The agent queries it live when your health dashboard runs, pulling open ticket count and response-time metrics per account.

3 Connect Gmail — Starch syncs your messages on a schedule. Tell Starch to match threads to HubSpot company domains so you can see the last communication date per account without leaving the app.

4 Start from the CRM app in the Starch App Store and customize it: add columns for open Intercom tickets, days since last email, and HubSpot deal stage. Tell Starch your risk thresholds — 30 days no activity, 3+ open tickets, 45 days no deal movement.

5 Describe the health score logic in plain language: 'Flag an account red if it hits any two risk signals. Flag it yellow if it hits one. Green otherwise.' Starch builds the scoring rule and applies it to all 250 accounts.

6 Set up an automation that runs on the first Monday of each month. It queries HubSpot, Intercom, and Gmail, calculates health scores, and writes the account-by-account narrative in whatever format you specify — Slack message, Google Doc, or email.

7 For accounts flagged as expansion-ready, tell Starch: 'Pull all HubSpot deals tagged with upsell or expansion that are in Negotiation or Closed Won. For each, write one sentence on the opportunity and the estimated deal value.' This becomes your expansion section.

8 Use the Presentation Agent to turn the narrative output into slides. Describe the deck: '10 slides, one per at-risk account plus an exec summary and renewal forecast. Use our brand colors.' Export to PDF or a shareable link.

9 Wire the delivery: 'Post the Slack summary to #cs-leadership every first Monday at 8am. Email the PDF to [names] with subject line Monthly CS Review — [Month].' Starch handles the send — you don't touch it unless something breaks.

10 After your first live MBR, tell Starch what you want to change: 'Add a column for days until renewal. Split the at-risk table into churn risk and disengaged.' The app updates without rebuilding from scratch.

11 Archive each month's MBR narrative in Notion — connect Notion from Starch's integration catalog and tell Starch: 'After each monthly run, write the summary to a new page in my CS Reviews database.' Now you have a searchable history when someone asks 'what was the situation with Acme in Q1?'

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

March 2026 MBR — 250-account CS team

Sample numbers from a real run

Total accounts reviewed	250
Accounts flagged at-risk (red)	18
Accounts flagged disengaged (yellow)	34
Accounts with 3+ open Intercom tickets	11
HubSpot deals in expansion pipeline	7
Estimated expansion pipeline value	142,000
Renewals due in next 60 days	22
Hours spent building the MBR vs. prior month	1

On the first Monday of March, Starch ran automatically at 8am. It synced HubSpot deal stages, queried Intercom for open ticket counts across all 250 accounts, and checked Gmail thread history to find the last inbound or outbound message per account domain. Eighteen accounts hit two or more risk signals: Meridian Logistics had 6 open Intercom tickets and no email from your team in 47 days. Coastal Beverage Co. had a deal stuck in 'Renewal Sent' for 52 days with no response. Starch flagged both red and wrote the one-paragraph situation summary your AE would normally draft by hand. The expansion section surfaced 7 accounts with upsell tags in HubSpot sitting in Negotiation, totaling $142,000 in pipeline — two of which your team hadn't touched in the current quarter. The Presentation Agent turned all of this into a 10-slide deck in four minutes. Your CS lead posted the Slack summary to #cs-leadership at 8:03am and joined the Monday standup with actual data instead of gut feel. Total time spent on MBR prep: about an hour reviewing the output and editing two account narratives where the context was off. The prior month, this took most of a Thursday.

Measurement

How you'll know it's working

At-risk account count and percentage of total book — tracked monthly, broken down by risk signal (no activity, ticket volume, deal stall)

Expansion pipeline value from HubSpot — deals tagged upsell or expansion, segmented by stage

Renewal forecast: accounts renewing in 30 / 60 / 90 days and their current health score

Average days since last meaningful touchpoint per account — your early-warning number for churn before it shows up in product usage

MBR prep time — a meta-KPI your team should track because reclaiming four hours a month per rep is the point

Comparison

What this replaces

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

Gainsight / Catalyst / ChurnZero

Purpose-built CS platforms with sophisticated health scoring and playbooks, but they start at $40–100k/year, require a CS-ops person to configure, and take months to go live — none of which works for a three-person team.

HubSpot reports + manual deck

Free if you're already paying for HubSpot, but you're assembling four data sources by hand every month and the output is a static snapshot that's stale before anyone reads it.

Google Sheets with Intercom/HubSpot exports

Works for the first 50 accounts, breaks at 250 when the exports don't match and nobody has time to reconcile them before the Monday meeting.

Notion CS dashboard (manually maintained)

Readable and customizable, but every update is a manual paste-in — meaning it reflects whoever had time to update it last, not what's actually happening in your accounts.

On Starch RECOMMENDED

One platform — crm, investor reporting, 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

Does Starch actually connect to Intercom, or do I have to export data manually?

Intercom is reachable from Starch's integration catalog — you connect it once and the agent queries it live when your health dashboard or MBR automation runs. No CSV exports, no copy-paste. The same is true for Zendesk if your team uses that instead.

We track some accounts in HubSpot and some in a spreadsheet. Can Starch handle that?

Yes. Connect HubSpot through Starch's scheduled sync for the accounts that live there. For the spreadsheet, connect Google Sheets from Starch's integration catalog and tell Starch how the two datasets relate — for example, 'match on company name or domain.' You can build a unified view even when the data is split.

Will this replace our CS platform if we ever buy one?

No, and it's not designed to. If you grow to a point where Gainsight makes sense — dedicated CS-ops, enterprise contracts, complex playbook automation — that's the right move. Starch is for the window before that, when you need real visibility and a repeatable MBR process without a six-figure tool and a six-month implementation.

What are the honest limitations I should know about?

A few worth naming. Starch is not SOC 2 Type II certified yet, so if your enterprise accounts have strict vendor security requirements, check with your IT team first. Data from Intercom and other catalog-connected apps is queried live rather than stored historically in Starch — so if you want a 12-month trend of ticket volume per account, you'll need to log that data somewhere (Notion or Google Sheets) as each monthly run completes. HubSpot deal and contact data does sync on a schedule, so that history lives in Starch. And Starch has no on-prem option, which matters if your customers restrict cloud vendors.

How long does the initial setup actually take?

Connecting HubSpot and Gmail takes a few minutes each — OAuth flows, then Starch starts syncing. Connecting Intercom from the integration catalog is similar. Building the health dashboard app by describing it in natural language takes 15–30 minutes of back-and-forth with the agent to get the risk flags and columns right. First full MBR run, including the Presentation Agent output, is realistically a half-day of setup — most of that is you deciding what you actually want the MBR to say, not technical configuration.

Can I use this if we're on Zendesk instead of Intercom?

Yes. Zendesk is reachable from Starch's integration catalog. Tell Starch to query Zendesk for open ticket counts and CSAT scores per account instead of Intercom. The rest of the workflow — HubSpot for deal data, Gmail for thread history — stays the same.