Customer Support

How to run customer qbrs as Small RevOps Teams

Customer SupportFor Small RevOps Teams3 apps12 steps~24 min to set up

Your two-person team owns QBR prep for 30 reps, and every quarter it's the same grind: export pipeline from HubSpot, pull closed-won and churn data from Stripe or QuickBooks, chase CSMs for their health notes in a Notion doc nobody keeps current, reconcile expansion ARR from Apollo sequences against what actually closed, paste everything into a Google Slides template the CRO will redesign anyway, and do it all in a 72-hour window before the exec meeting. The CRM data is stale. The attribution is wrong. And half your slides are obsolete by the time the deck is shared.

Build this on Starch → See the apps used

Customer SupportFor Small RevOps Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A QBR prep app that pulls live account health, pipeline movement, and closed revenue from HubSpot, Stripe, and Apollo into a single structured view — no more manual exports

An automated meeting notes workflow that transcribes every customer QBR call, extracts decisions and action items, and stores them in searchable history tied to the account

A slide-generation flow that turns your structured QBR data into a polished deck — one prompt, no Sunday-night Slides wrestling

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 Meeting Notes Presentation Agent

Data sources & config

Wire HubSpot as a scheduled-sync provider — Starch syncs your contacts, companies, deals, and owners on a schedule. Connect Stripe as a scheduled-sync provider for charges, subscriptions, and invoices. Connect Apollo.io as a scheduled-sync provider for contact activity and sequence engagement. Connect Gmail as a scheduled-sync provider for email thread history to surface last-touch context per account. Connect Salesforce or Pipedrive from Starch's integration catalog if reps log activity there — the agent queries them live when the QBR dashboard runs. Meeting notes are captured in-app during or after calls.

Prompts to copy

Build me a QBR prep dashboard that pulls each account's closed-won and open renewal opportunities from HubSpot, their subscription revenue and recent invoices from Stripe, and outbound sequence activity from Apollo. Group accounts by renewal date, show ARR at risk, last contact date, and any open action items from previous QBR notes. Flag any account where ARR is over $50k and last contact was more than 45 days ago.

Transcribe this customer QBR call, generate a summary with key decisions and risks discussed, extract action items with owner names, and save everything under the account record for Acme Corp.

Build a 12-slide QBR deck for Acme Corp's Q2 2026 business review. Include slides for: ARR summary and growth vs. last year, product usage highlights, open support issues, renewal forecast, and three recommended next steps. Pull the numbers from the QBR prep dashboard I already built.

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

Walkthrough

Step-by-step

1 Connect HubSpot as a scheduled-sync provider. Starch syncs your deals, contacts, companies, and owners automatically — you get a live dataset without manual exports every quarter.

2 Connect Stripe as a scheduled-sync provider. Starch pulls subscription revenue, MRR, invoice history, and payout data so your renewal ARR numbers are always current and tied to the right account.

3 Connect Apollo.io as a scheduled-sync provider. Starch syncs sequence engagement and contact activity so you can see which accounts had outreach this quarter and which went dark.

4 Connect Gmail as a scheduled-sync provider. Email thread context surfaces in the QBR dashboard — you can see who last talked to an account and what was discussed without leaving Starch.

5 Start from the CRM starter app and describe your QBR prep workflow. Tell Starch the fields that matter: renewal date, ARR, health score proxy (days since last contact, open issues), expansion pipeline. It builds the view to your spec.

6 Build a QBR prep dashboard with a natural-language prompt that groups accounts by renewal cohort, surfaces ARR-at-risk flags, and pulls in last-touch date and sequence activity in one place.

7 Before each customer call, pull the account's QBR prep card. You get renewal ARR, open pipeline, last email thread summary, and any action items logged from prior meetings — all in one screen.

8 Run the customer QBR call with Meeting Notes active. It transcribes in real time, generates a post-call summary with decisions and risks, and extracts action items with owner assignments.

9 After the call, those action items and notes are stored under the account record in your QBR app. When someone asks 'what did we commit to Acme last quarter?' you search and find the exact moment.

10 After all customer calls for the cohort are done, prompt the Presentation Agent to build the internal QBR deck — slides for ARR summary, churn risk, expansion pipeline, product usage highlights, and recommended actions. It pulls from the structured data you already assembled.

11 Export the deck to PowerPoint or a shareable link for the exec review. If the CRO wants a different format or wants to add a slide, iterate with a follow-up prompt — no redesigning from scratch.

12 Post-QBR, update account statuses in the CRM app with a single prompt: 'Mark all accounts in the Q2 renewal cohort as QBR complete and log the outcome for each.' Starch updates the records without you clicking through 30 deal pages.

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 QBR — 14 Accounts

Sample numbers from a real run

Acme Corp	84,000
Bridgeton Logistics	62,000
NovaStar Health	48,000
Fieldworks Inc.	31,000
Cascade Analytics	27,500
9 additional accounts	188,500

Your Q2 renewal cohort is 14 accounts totaling $541,000 ARR. Starch syncs HubSpot deals and Stripe subscriptions overnight, so when you open the QBR prep dashboard Monday morning you already see that Bridgeton Logistics ($62k ARR) hasn't had an email thread in 51 days and their Apollo sequence was paused in March — two red flags surfaced automatically. NovaStar Health ($48k) has an open expansion deal in HubSpot but nobody's moved it in 6 weeks. You run QBR calls for all 14 accounts over two weeks. Meeting Notes transcribes each call; Acme Corp's call produces 4 action items including a custom integration request flagged as a retention risk. After the last call, you prompt the Presentation Agent: 'Build a 14-account Q2 QBR summary deck showing renewal status, ARR at risk, and top 3 expansion opportunities by ARR.' Starch pulls from the dashboard data and generates a complete deck. The whole prep cycle that used to take 3 days of copy-paste now takes an afternoon of reviewing and a few prompts. You go into the exec meeting knowing exactly which accounts need attention — and with notes to prove you already followed up.

Measurement

How you'll know it's working

Renewal rate by cohort (% of ARR renewed on time vs. lapsed)

Days between last customer contact and QBR call (staleness flag)

ARR at risk — accounts flagged with no activity in 45+ days

Action item close rate from prior QBR (did the things you committed to actually get done)

QBR prep time per rep cohort (hours your team spent vs. accounts covered)

Comparison

What this replaces

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

Gainsight or ChurnZero

Purpose-built for CS health scoring but costs $30k+/year, requires a dedicated admin to configure, and doesn't help with QBR deck creation or meeting notes — you'd still need three other tools.

HubSpot reporting + Google Slides

Free to start, but every QBR cycle is a manual export-paste-format loop; there's no meeting notes integration and no way to auto-generate slides from live pipeline data.

Gong + Salesforce + Notion

Gong captures calls well and Salesforce is the CRM of record for many teams, but stitching them into a QBR prep view still requires someone to build and maintain the reports, and deck creation is still manual.

Notion + Google Sheets (homegrown stack)

Low cost and flexible, but you're the one maintaining the schema, the formulas, and the copy-paste pipeline from HubSpot — the 'tool' is actually your own labor.

On Starch RECOMMENDED

One platform — crm, meeting notes, 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

We use Salesforce, not HubSpot. Does this still work?

Yes. Connect Salesforce from Starch's integration catalog — the agent queries your deals, contacts, and activities live when your QBR dashboard runs. It's not a scheduled sync like HubSpot, meaning data is pulled fresh at query time rather than stored in Starch on a schedule, but for a QBR prep workflow that's typically what you want anyway.

The Presentation Agent is listed as 'currently in development' — can I use it now?

Not yet. The Presentation Agent is in development and you can request beta access to get notified when it launches. In the meantime, the QBR prep dashboard and meeting notes workflows are fully live today — the deck-generation step is the one piece you'd still do manually until beta opens.

Will Starch write back to HubSpot — can it update deal stages or log activity?

The HubSpot scheduled sync is read-only today — Starch reads your deals, contacts, and companies but doesn't push updates back to HubSpot directly. You'd use the QBR app in Starch as your prep and notes layer, then update HubSpot manually for anything that needs to live in the CRM of record.

We have 14 QBR calls in two weeks. Can Meeting Notes handle that volume?

Yes. Meeting Notes transcribes and summarizes each call independently, stores them under the account record, and makes them searchable. There's no per-call limit. The practical constraint is that you're running the calls — Starch handles the capture and organization on the back end.

Is Starch SOC 2 certified? We have customers who'll ask.

Not yet — Starch is not SOC 2 Type II certified today. If your QBR data includes sensitive customer financials or regulated data and your customers require certified vendors in the chain, that's worth knowing upfront. It's on the roadmap.

Can we pull in product usage data — like event counts from our analytics tool — to include in QBR slides?

Starch connects to 3,000+ apps through its integration catalog, plus any website through browser automation. If your product analytics tool (PostHog, Mixpanel, Amplitude, etc.) is in the catalog, connect it and the agent queries it live when your QBR app runs. The Growth Analyst starter app already uses PostHog as a connection — you can fork it or describe what you need from scratch.