Internal Comms & Meetings

How to run a team retrospective as Small Finance Teams

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

Your Q1 retrospective lives across six Slack threads, a Google Doc nobody finished, and someone's personal notes from a Zoom call that wasn't recorded. As a 3-person finance team, you run retrospectives once a quarter at best — and when you do, half the meeting is reconstructing what actually happened in month-end close instead of talking about how to fix it. Action items from the last retro? Buried. The flux variance your controller flagged in February? Unresolved and repeating. You're not bad at retrospectives; you just have no infrastructure for them. No one took notes, no one owns the follow-up, and you're about to have the same conversation again.

Build this on Starch → See the apps used

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

Outcome

What you'll set up

A structured retrospective workflow that pulls real close-cycle data from QuickBooks and NetSuite into your retro context — so you're debating the actual numbers, not reconstructing them from memory

Automatic meeting notes with action items assigned by name, archived and searchable, so 'didn't we decide this last quarter?' has a real answer

A living follow-up tracker tied to the retro outcomes, with due dates and owners, so flux variances and process failures become tasks, not talking points

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 Google Calendar data on a schedule to detect upcoming retro meetings and surface relevant context. Notion is connected from Starch's integration catalog so the agent queries your existing docs live when building the retro knowledge base. Slack is connected from Starch's integration catalog so the agent can pull thread context from the channels where your team worked through close issues this quarter. QuickBooks and NetSuite data syncs on a schedule so your retro prep surfaces the actual close variances, not a summary someone typed up.

Prompts to copy

Transcribe our Q2 finance retrospective and generate a summary with key decisions, action items assigned to each person on the team, and a section called 'Recurring Issues' for anything we flagged last quarter too

Archive this retro in our finance team knowledge base under 'Quarterly Retrospectives > 2026'. Tag it with the close month and link it to the Q1 retro so we can compare action item completion rates

Create tasks for each action item from today's retro: assign 'Fix NetSuite department mapping for COGS' to Sarah, priority P1, due June 15; assign 'Build AR aging view for CEO' to Marcus, priority P2, due June 30; remind me to check status on both on June 10

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

Walkthrough

Step-by-step

1 One week before the retro, tell Starch: 'Pull a summary of every journal entry we flagged as unusual in QuickBooks this quarter, and any invoice or bill that required a manual override.' Starch queries your synced QuickBooks data and returns a list you can paste into the retro prep doc — no digging through reports manually.

2 Open the Knowledge Management app and search 'Q1 2026 retrospective' to find last quarter's action items. Starch surfaces the archived doc instantly, including which items were marked resolved and which were carried over.

3 Before the meeting, create a retro agenda in Starch: 'Generate a finance retro agenda for a 60-minute meeting covering month-end close timing, AP approval bottlenecks, AR reconciliation against Stripe payouts, and board deck prep time. Include a 10-minute block for reviewing last quarter's action items.'

4 Start the retro and let Meeting Notes run. The app transcribes in real time — your controller can talk through the NetSuite department mapping issue without anyone stopping to write it down.

5 After the call ends, Meeting Notes generates a structured summary with key decisions highlighted and action items extracted. Review the output: it will have caught 'Marcus will rebuild the AR aging dashboard before the next board meeting' as an action item with an owner.

6 Tell Starch to cross-reference this retro's action items against last quarter's: 'Compare today's action items against our Q1 2026 retro. Flag any items that appear in both.' This surfaces your true repeat offenders — the flux variances and process gaps that keep coming back.

7 Create tasks for each action item using Task Manager. Use the chat interface: 'Create a P1 task for Sarah: update NetSuite COGS department mapping, due June 15. Create a P2 task for Marcus: build AR aging dashboard in Starch pulling from our NetSuite sync, due June 30.' Each task is assigned, prioritized, and dated without clicking through a form.

8 Archive the full retro — transcript, summary, action items, and the repeat-issue flag — in Knowledge Management under a 'Quarterly Retrospectives' section. Tell Starch: 'Save this retro to our finance team wiki, tag it Q2 2026 and month-end close, and link it to the Q1 retro doc.'

9 Set a mid-quarter check-in automation: 'In 45 days, remind me to check Task Manager for the action items from the Q2 retro and pull their status into a Slack message to the finance channel.' Starch schedules this and runs it automatically.

10 At the next retro, the prep step takes 10 minutes instead of 45: Starch surfaces the archived Q2 retro, shows which tasks were completed, pulls the quarter's QuickBooks anomalies, and drafts the agenda — all from a single prompt.

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 Finance Retro — June 5, 2026

Sample numbers from a real run

Time spent reconstructing close issues in meeting	45
Time spent with Starch retro prep (QuickBooks query + last retro pull)	8
Action items from Q1 retro carried into Q2 unresolved	4
Action items from Q2 retro with named owners and due dates in Task Manager	7
Repeat issues flagged by Starch cross-reference (appeared in both retros)	2

Going into the June 5 retro, Sarah pulled QuickBooks data via Starch and surfaced three recurring manual overrides in COGS — all traced to a department mapping issue in NetSuite that was flagged in the Q1 retro but never assigned to anyone. The meeting opened with that context already on the table instead of spending 20 minutes figuring out why gross margin looked wrong again. Meeting Notes ran through the 60-minute call and extracted 7 action items, including 'Marcus rebuilds AR aging dashboard pulling from NetSuite sync in Starch, due June 30' and 'Sarah corrects department mapping in NetSuite and validates against June close, due June 15.' The cross-reference with the Q1 retro flagged 2 of the 7 items as repeats — the COGS mapping issue and a recurring AP approval lag over $10K that nobody had built a process for. Both got P1 priority in Task Manager. By end of day, the full retro was archived in Knowledge Management, linked to Q1, and a mid-quarter check-in was scheduled for July 18. The next retro prep will take a prompt, not a morning.

Measurement

How you'll know it's working

Action item completion rate quarter-over-quarter (retros that actually change behavior vs. ones that produce a doc nobody reads)

Repeat issue rate — how many items appear in two or more consecutive retros without resolution

Time from close end to retro debrief (finance teams that debrief faster catch process failures before they compound)

Days saved on retro prep by pulling QuickBooks and NetSuite data directly vs. manual reconstruction

Number of process gaps that became permanent documented fixes vs. one-time patches

Comparison

What this replaces

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

Google Docs + Zoom recording

You already own this stack and it costs nothing, but action items stay in a document nobody watches, there's no link to your actual close data, and next quarter's retro will start by searching for this quarter's doc.

Notion + Loom

Notion is great for archiving and Loom captures the conversation, but neither extracts action items automatically or cross-references repeat issues — you're still doing that manually, and Notion pages go stale without someone actively maintaining them.

Confluence + Jira

Powerful for engineering orgs with a dedicated admin to configure workflows, but expensive and over-engineered for a 3-person finance team that runs one retro a quarter and doesn't want to become a Jira admin.

Otter.ai + manual task entry

Otter transcribes accurately, but the transcript is raw — extracting action items, assigning owners, and linking back to last quarter's retro is still manual work you're doing after every meeting.

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

Can Starch actually pull our QuickBooks data into retro prep, or do I have to export it first?

Starch syncs your QuickBooks data on a schedule — invoices, bills, journal entries, vendors, payments. You don't export anything. Before the retro, you describe what you want ('show me journal entries flagged as manual overrides in Q2') and the agent queries the synced data directly. One honest limit: QuickBooks report views like the P&L summary are temporarily disabled pending a connector fix, but entity-level data — the line items your retro actually needs — syncs normally.

What about NetSuite? Our COGS lives there and that's usually what we're debating in retros.

NetSuite is a scheduled-sync connection — Starch syncs your invoices, expenses, journal entries, balance sheets, and income statements on a schedule. So when you're reconstructing why gross margin moved 200 basis points in April, you can ask Starch directly instead of rebuilding it from an export.

Does Meeting Notes work if we run the retro on Zoom or Google Meet?

Meeting Notes captures the meeting and transcribes it in real time. Zoom and Google Meet are both reachable through Starch's integration catalog. If your setup is unusual, Starch can also automate meeting-related actions through your browser — no API required.

Is this SOC 2 certified? We're going to push meeting recordings and financial context through this.

Starch is not SOC 2 Type II certified today. That's worth knowing if you're subject to strict data controls. If you're a lean internal finance team at a private company where the CFO is making the call, most teams are comfortable with the tradeoff given the time savings — but we're not going to pretend the certification exists when it doesn't.

What if we want to track whether this quarter's action items actually got done before next retro?

Task Manager is where the action items live after the retro — assigned by name, prioritized P1–P4, with due dates. You can set a mid-quarter check-in automation that pulls task status and sends a summary to your Slack channel. At the next retro, Starch can compare this quarter's action items against their Task Manager status and flag anything overdue or unresolved, so the repeat-issue problem becomes visible instead of invisible.

We use Slack for almost all async finance discussion. Can Starch pull that context into the retro?

Yes. Slack is connected from Starch's integration catalog — the agent queries channels and users live when your app runs. You can tell Starch to pull relevant threads from your finance or close channels as retro context. It won't replace your memory of the conversation, but it will surface the threads where the issues actually played out.