Sales & CRM

How to run a weekly sales pipeline review as Small Customer Success Teams

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

Your three-person team owns 250 accounts, and the 'weekly pipeline review' is currently a 45-minute scramble where someone exports HubSpot deals to a spreadsheet, someone else pulls renewal dates from a separate tab, and you try to reconcile expansion signals that live in your head from last week's calls. Churn risk shows up in a usage dashboard that only updates weekly — if you remember to check it. Gainsight and ChurnZero would solve this, but they cost six figures and require a CS-ops hire to stand them up. You end up running your pipeline review out of a stale export and a shared Google Doc that nobody trusts.

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 live pipeline review app that pulls directly from HubSpot deals and your Gmail thread history, surfacing accounts by renewal date, expansion signal, and last-contact date — so your Monday standup runs off real data, not last week's export.

An automated weekly digest that flags accounts showing churn risk or expansion signals — sent to your Slack or inbox before the meeting starts, so you walk in with a prioritized list instead of building one live.

A renewal forecast view that rolls up open renewals by ARR and close probability, updated automatically from HubSpot, so your number is always current without a manual build every Friday afternoon.

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 Growth Analyst

Data sources & config

Starch syncs your HubSpot data on a schedule — contacts, companies, deals, and owners — so deal stage, ARR, renewal dates, and close probabilities are always current. Starch also syncs your Gmail on a schedule, giving the pipeline tracker access to email thread history per account. Slack is connected from Starch's integration catalog and queried live when the Monday automation fires. Intercom is reachable from Starch's integration catalog for pulling support ticket context into account health views.

Prompts to copy

Build me a CS pipeline tracker that pulls HubSpot deals where the deal stage is 'Renewal' or 'Expansion', shows account name, ARR, renewal date, close probability, and the last email thread from Gmail. Sort by renewal date ascending. Flag any account where close probability dropped more than 10 points since last week.

Every Monday at 8am, scan my HubSpot deals for renewals closing in the next 60 days, cross-reference Gmail for accounts where I haven't sent an email in 21 or more days, and send me a Slack message listing those accounts sorted by ARR descending.

Show me a renewal forecast for this quarter: group open deals by month, sum the ARR, and give me a weighted forecast using close probability. Pull from HubSpot and refresh every morning.

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

Walkthrough

Step-by-step

1 Connect HubSpot: Starch syncs your HubSpot contacts, companies, deals, and owners on a schedule. This is the backbone of your pipeline tracker — deal stages, ARR, renewal dates, and close probabilities all flow in automatically.

2 Connect Gmail: Starch syncs your Gmail on a schedule, which lets the pipeline app surface the last email thread for each account. You'll immediately see which accounts haven't heard from anyone in 21+ days.

3 Connect Slack from Starch's integration catalog: the agent queries it live when your Monday automation fires, so your pre-meeting digest lands in the right channel without any manual trigger.

4 Connect Intercom from Starch's integration catalog: the agent queries it live to pull open ticket counts or recent support activity per account — useful context when you're deciding where to spend the meeting.

5 Start with the Sales Agent CRM app from the App Store as your base, then customize: tell Starch to add a 'CS Stage' field (Onboarding / Healthy / At Risk / Expansion / Renewal), a 'Last Outreach' calculated field from Gmail, and an 'ARR' field from HubSpot deals.

6 Build the expansion signal view: prompt Starch to surface accounts where deal stage is 'Expansion' or where you've tagged an account as 'At Risk' in the past 14 days, with the last Intercom ticket date alongside it.

7 Build the renewal forecast: prompt Starch to group open renewal deals by close month, sum ARR per bucket, and calculate a weighted forecast using close probability. Pin this as a view at the top of your pipeline tracker.

8 Set the Monday automation: tell Starch to run every Monday at 8am, pull renewals closing within 60 days, cross-reference Gmail for last-contact dates, and post the sorted list to your CS Slack channel with ARR and days since last touch.

9 Add a churn-risk flag: prompt Starch to mark any account where close probability dropped more than 10 points week-over-week, and surface those accounts at the top of the weekly digest.

10 Run your first weekly review using the live pipeline tracker instead of a spreadsheet: the Monday Slack message is your agenda, the pipeline tracker is the working surface, and deal updates you make in Starch write back through HubSpot's connected data.

11 Each quarter, when it's QBR time, pull the account history from your pipeline tracker — email thread count, stage transitions, support ticket volume from Intercom — and use that data to build your deck rather than reconstructing it from memory.

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 Cohort Review — April 7

Sample numbers from a real run

Fieldstone Logistics	48,000
Meridian Benefits Group	31,200
Tallgrass Software	22,500
Kestrel Medical Partners	19,800
Northvale Retail Co.	14,400

On Monday April 7, your Starch automation fires at 8am. The Slack message lists five accounts with renewals before June 30, totaling $135,900 in ARR. Two catch your eye immediately: Fieldstone Logistics ($48,000) has a close probability that dropped from 80% to 60% since last week, and no email has gone out to their main contact in 26 days — both flagged automatically. Meridian Benefits Group ($31,200) has three open Intercom tickets, which the tracker pulled via live query from Starch's integration catalog. You walk into the 9am standup with a prioritized list: Fieldstone is a same-day outreach, Meridian needs a call to clear the support backlog before renewal conversations start. Tallgrass, Kestrel, and Northvale all show healthy last-contact dates and stable close probabilities — you note them but don't spend meeting time on them. The whole review takes 18 minutes instead of 45, because you're triaging a pre-built list instead of building it live from a spreadsheet.

Measurement

How you'll know it's working

Renewal ARR at risk (accounts flagged with >10pt probability drop in the last 7 days)

Days since last outreach per account (sourced from Gmail sync, filtered to renewals closing within 90 days)

Weighted renewal forecast by month (close probability × ARR, grouped by close date)

Expansion pipeline value (deals in Expansion stage, by account segment)

Accounts with open support tickets at renewal date (Intercom ticket count per account from integration catalog)

Comparison

What this replaces

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

Gainsight

Purpose-built for CS health scoring and renewal tracking, but starts around $50,000/year and requires a CS-ops admin to configure and maintain health score models — not practical for a three-person team without dedicated ops support.

HubSpot Service Hub + manual exports

HubSpot holds the deal data, but you're still manually exporting to spreadsheets for the pipeline review because HubSpot's native CS views don't surface last-email-date, churn signals, and support ticket counts in one place.

ChurnZero

Good at automated health scoring for larger CS teams, but pricing and implementation complexity assume a mid-market CS operation with dedicated tooling budget — overkill and expensive for teams under 5 people.

Spreadsheet + HubSpot export

Free and familiar, but the data is stale the moment you export it, you spend 30-40 minutes rebuilding the view every week, and there's no way to automate the Monday digest or flag probability changes automatically.

On Starch RECOMMENDED

One platform — sales agent crm, crm, growth analyst 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 run our CS pipeline out of HubSpot. Does Starch replace HubSpot or sit on top of it?

Starch sits on top of HubSpot, not instead of it. Starch syncs your HubSpot deals, contacts, companies, and owners on a schedule, then lets you build views and automations your HubSpot plan doesn't ship — like a renewal tracker that cross-references Gmail last-contact dates, or a Monday Slack digest that flags probability drops. Your team keeps using HubSpot as the record system; Starch is the surface where you actually run the weekly review.

Will Starch write deal updates back to HubSpot, or is it read-only?

The HubSpot sync in Starch is currently read-only — deal stage changes you make inside Starch don't push back to HubSpot automatically. For most pipeline review workflows this works fine: you use Starch as the review surface, then update HubSpot directly for changes that need to live there. If write-back matters to your team, that's worth checking on with Starch directly before you build the workflow around it.

We also use Intercom for support tickets and Zendesk for some enterprise accounts. Can Starch pull from both?

Yes. Both Intercom and Zendesk are reachable from Starch's integration catalog — the agent queries them live when your pipeline app or automation needs the data. You can build a single account health view that shows open ticket counts from both tools alongside your HubSpot renewal data, without needing to log into each system separately during the meeting.

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

The Sales Agent CRM app from the App Store is a working starting point — you can install it, connect HubSpot and Gmail, and have a functional pipeline view in under an hour. Adding the Monday Slack automation and the churn-risk flag takes a few more prompts. There's no schema to configure, no workflow builder to learn — you describe what you want and Starch builds it. The tradeoff is that you're building something custom, so if your first version isn't exactly right, you'll iterate with a prompt rather than clicking through a settings page.

Is Starch SOC 2 certified? We handle enterprise customer data.

Starch is not SOC 2 Type II certified today. If your enterprise customers have a hard requirement for SOC 2 Type II vendor certification before you connect their account data, that's a real blocker worth knowing upfront. Starch is transparent about this — it's on the roadmap, not available today.

We pull usage data from PostHog to assess churn risk. Can that come into the pipeline tracker too?

Yes. Starch syncs PostHog data on a schedule and uses it in the Growth Analyst app today. You can describe a custom pipeline view that shows PostHog usage metrics alongside HubSpot renewal dates — for example, accounts where weekly active users dropped more than 20% in the last 30 days and renewal is within 60 days. That's a natural-language prompt, not a BI tool configuration.