Internal Comms & Meetings

How to run a team retrospective as Small Customer Success Teams

Internal Comms & MeetingsFor Small Customer Success Teams3 apps10 steps~20 min to set up

Your three-person team runs a retrospective every two weeks, and half the meeting is spent reconstructing what actually happened — digging through Intercom threads to remember which onboarding issues kept surfacing, scrolling HubSpot to find which accounts went quiet, and asking each other 'wait, did we ever follow up on that?' Action items from the last retro live in someone's notes doc that nobody opened since. You leave with a list of follow-ups, assign them verbally, and by next Thursday half of them have disappeared. Gainsight would solve this, but it costs more than your annual software budget and needs a CS-ops person to configure it. You need a retro that's grounded in real account data, not vibes.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small Customer Success Teams3 apps10 steps~20 min to set up

Outcome

What you'll set up

A recurring retro workflow that auto-pulls open tickets from Intercom, deal activity from HubSpot, and calendar events from Google Calendar so your team walks in with a shared fact base instead of competing memories

A searchable archive of every retro — decisions made, action items assigned, accounts flagged — so next quarter's retrospective can actually build on this one instead of starting from scratch

A task list where every action item from the retro is captured with an owner and due date before anyone leaves the meeting, and overdue alerts surface the ones that slipped

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

Meeting Notes Knowledge Management Task Manager

Data sources & config

Starch syncs your HubSpot data on a schedule (contacts, companies, deals, owners) and your Google Calendar on a schedule (events 12 months back, 3 months ahead), so meeting context and account activity are already in Starch when the retro starts. Intercom is connected from Starch's integration catalog; the agent queries it live to pull recent ticket and conversation data. Notion can be connected from Starch's integration catalog if your team already stores docs there; the agent queries it live. Meeting Notes handles transcription and action-item extraction; Knowledge Management stores the archive; Task Manager tracks follow-through.

Prompts to copy

Before our CS team retro: pull all Intercom conversations from the last two weeks that were escalated or marked unresolved, group them by theme, and give me a summary of the top three recurring issues so I can put them on the agenda

Transcribe today's team retrospective, extract every action item mentioned, assign each one to the person whose name was said before it, and flag any account names that came up more than twice

Save today's retro notes to our Knowledge Management wiki under 'CS Retrospectives > Q2 2026', tag it with the accounts we discussed, and link it to last month's retro entry so we can track whether the same issues are recurring

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

Walkthrough

Step-by-step

1 Three days before the retro, tell Starch: 'Pull all Intercom conversations from the last 14 days that were escalated, unresolved, or tagged as onboarding. Group by issue type and list any account names that appear more than once.' Use this as your agenda draft — it takes 2 minutes instead of 20.

2 Connect HubSpot from Starch's scheduled sync so deal stage changes, new contacts, and stalled opportunities from the past two weeks are already visible in your retro prep. Tell Starch: 'Show me every HubSpot deal that hasn't had an activity update in 14 days and is past its expected close date.'

3 Pull your Google Calendar sync — Starch already has it — to see which customer calls happened in the past two weeks. Tell Starch: 'List all external meetings from the last 14 days tagged with account names and show me which accounts had no touchpoint this period.'

4 Open Meeting Notes at the start of the retro. The app transcribes in real time. Tell your team upfront: everything said gets captured, so nobody needs to type while they talk.

5 Run the retrospective normally: what went well, what didn't, what needs to change. When someone mentions an account ('that onboarding issue with Brightfield has been every week'), Meeting Notes captures the account name and the context, not just the action item.

6 At the end of the retro — before anyone closes their laptop — tell Starch: 'From this meeting's transcript, extract every action item, who was assigned, and any account it relates to. Format as a task list with owner and a suggested due date of 7 days from today.' Review it together live and correct anything the transcript missed.

7 Push action items directly to Task Manager: 'Create tasks for each item on that list with P2 priority and due dates as specified. Assign to the named owner.' Each team member now has their items in their personal task view with due dates and overdue alerts built in.

8 Save the retro to Knowledge Management: 'Archive today's retro in the CS Retrospectives section. Include the summary, action items, accounts discussed, and a link to last month's entry. Tag it Q2 2026 and mark any accounts that came up in both this retro and the previous one.'

9 One week later, tell Starch: 'Show me all tasks from the last CS retro that are overdue or still open. For each one, tell me the assigned owner and the original account context.' Send this to your team in Slack before the next retro so the warmup is done for you.

10 At the following retro, start by querying Knowledge Management: 'Did the same issue themes come up in our last three retros? Show me a count of recurring topics across the last three entries in CS Retrospectives.' Now you're running a retro that actually learns from itself.

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

April 18, 2026 CS Team Retro — Q2 Week 3

Sample numbers from a real run

Brightfield Systems	0
Novara Health	0
Kettlebrook Logistics	0
Open Intercom escalations reviewed	11
Action items extracted from transcript	7
Accounts with no touchpoint in 14 days (HubSpot)	4

Going into the April 18 retro, your prep query pulled 11 unresolved or escalated Intercom conversations from the past two weeks. Eight of them clustered around one theme: customers couldn't figure out how to configure the CSV import during onboarding. Brightfield Systems appeared in three of those threads. HubSpot sync showed that Novara Health and Kettlebrook Logistics hadn't had an activity update in 18 days — both are in month 2 of a 12-month contract, right in the churn-risk window. Meeting Notes ran through the 45-minute call and pulled 7 action items: one for each team member on the CSV documentation gap, one to schedule a check-in call with Novara this week, and a flag to loop in the product team about the import UX. Before the retro ended, all 7 items were in Task Manager under named owners with April 25 due dates. The retro was archived in Knowledge Management under CS Retrospectives > Q2 2026, linked to the March entry — which, it turned out, also flagged CSV onboarding confusion. Two retros in a row. Now you have evidence to bring to product, not just a feeling.

Measurement

How you'll know it's working

Retro action-item completion rate (% of items from last retro closed before next retro)

Recurring issue recurrence rate (same theme appearing in 2+ consecutive retros without resolution)

Accounts flagged per retro with no recent touchpoint (leading indicator of churn risk)

Time from retro end to all action items assigned and in a task system (target: before meeting closes)

Searchable retro archive coverage (% of retros stored and retrievable vs. lost in notes docs)

Comparison

What this replaces

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

Notion + manual notes doc

Your team already uses Notion for docs, but someone still has to write the retro summary by hand, action items still get buried, and there's no automatic pull from HubSpot or Intercom to ground the conversation in real account data.

Gainsight or ChurnZero

Purpose-built for CS retrospectives and health scoring, but priced for 10+ person teams with a CS-ops admin to configure them — not a 3-person team that also owns renewal forecasting.

Otter.ai or Fireflies.ai for transcription only

Good transcription, but the output is a raw transcript — you still have to extract action items manually, nothing connects to HubSpot or Intercom, and there's no structured archive that links retros over time.

Linear or Asana for action item tracking

Solid task systems, but they don't connect to your meeting transcript — someone still has to manually copy action items out of notes and into the tool after every retro.

On Starch RECOMMENDED

One platform — meeting notes, knowledge management, task manager 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 transcribe the meeting, or do I have to paste a transcript in?

Meeting Notes transcribes in real time — you open the app at the start of the call and it captures the conversation as it happens. You don't paste anything. After the call it generates a summary, pulls out action items, and archives the meeting. If you use Zoom or Google Meet, those are reachable from Starch's integration catalog and the agent can query them live for meeting metadata.

We use HubSpot for accounts and Intercom for support tickets. Can Starch pull from both in the same retro prep?

Yes. Starch syncs your HubSpot data on a schedule — contacts, companies, deals, and owners are already in Starch when you need them. Intercom is connected from Starch's integration catalog; the agent queries it live when you run your pre-retro pull. You can write one prompt that pulls from both in a single pass.

What if our retro notes are currently in Notion? Do we have to start over?

No. Notion is connected from Starch's integration catalog — the agent can query your existing Notion pages and databases live. You can tell Starch to pull your past retro docs from Notion, cross-reference them with this week's HubSpot and Intercom data, and identify recurring themes. Knowledge Management is where new retros get archived going forward, but your Notion history stays accessible.

Is Starch SOC 2 certified? We're handling account names and support conversation content.

Starch is not SOC 2 Type II certified today. If your customers or your company's security policy requires SOC 2 Type II, that's worth knowing upfront. There's no on-premise option either — Starch runs in the cloud.

Will action items actually get followed up on, or will they just sit in another list nobody checks?

Task Manager sends overdue alerts — if a task from the retro hits its due date and nobody marked it done, the assigned owner gets flagged. More useful: at the start of your next retro, you can query Starch for all open tasks from the previous retro before the meeting starts. You walk in knowing exactly what slipped, with account context attached, instead of finding out 30 minutes in when someone asks 'wait, what happened with Brightfield?'

Can I use this for monthly or quarterly business reviews, not just weekly retros?

Yes — the same setup works for QBRs. The pre-meeting pull gets more powerful at a quarterly cadence: tell Starch to pull HubSpot deal history for the quarter, Intercom ticket volume by account, and Google Calendar touchpoint frequency per customer. For QBR decks, you'd describe what you want and Starch builds a custom surface — for example: 'Build me a QBR view for Brightfield Systems showing their Intercom ticket volume, HubSpot deal activity, and last 4 meeting dates in one dashboard.'