Internal Comms & Meetings

How to run a team retrospective as Solo Media and Creator Founders

Internal Comms & MeetingsFor Solo Media and Creator Founders3 apps11 steps~22 min to set up

You run a 1-2 person media operation, which means 'team retrospective' sounds like a corporate thing that doesn't apply to you — until you realize you've shipped 12 episodes and have no idea which sponsor performed, why your open rate dropped in February, or who was supposed to follow up with that podcast ad network. There's no shared memory. Notes from last quarter's planning call are buried in a Notion page nobody updated. Action items live in your head, your co-host's head, and maybe a Google Doc that hasn't been touched since March. Without a structured retro, every quarter feels like starting over.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Solo Media and Creator Founders3 apps11 steps~22 min to set up

Outcome

What you'll set up

A searchable archive of every retro — decisions, action items, and what actually shipped — so you stop relitigating the same conversations

A standing retro workflow that pulls your real metrics (Stripe revenue, newsletter stats, Notion editorial calendar) into the conversation before the meeting starts

A task list wired directly to retro action items so nothing falls into the void between 'we talked about it' and 'someone actually did it'

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

Meeting Notes transcribes your retro call live. Notion is connected via scheduled sync so Starch already has your editorial calendar and past docs to reference during the meeting. Stripe is connected via scheduled sync so revenue numbers are available when you're walking through what worked commercially. Google Calendar is connected via scheduled sync so Starch can surface what shipping cadence actually looked like versus what you planned. Task Manager captures action items from the retro and tracks them through to completion.

Prompts to copy

Transcribe and summarize today's Q2 retro call. Extract every action item, who owns it, and any decisions we made about sponsors, content cadence, or the YouTube strategy.

Create a retro entry in our knowledge base titled 'Q2 2026 Retrospective' — include the summary from today's meeting, link it to the Q1 retro, and tag it under 'Quarterly Reviews'.

From the Q2 retro summary, create tasks for every action item. Assign anything related to sponsorships to me as P1, content pipeline items as P2. Set due dates two weeks out unless we specified otherwise in the meeting.

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

Walkthrough

Step-by-step

1 Two days before the retro, tell Starch: 'Pull together a pre-retro brief — last quarter's Stripe revenue, our top 5 episodes by downloads if available, any open tasks from the Q1 retro that never got closed.' This gives you actual data to discuss instead of going on vibes.

2 Connect Stripe via scheduled sync (Starch syncs your charges, invoices, and subscription data automatically) so sponsor payment history is in the room without any manual prep.

3 Connect Notion via scheduled sync so Starch can see your editorial calendar — what you planned to ship versus what actually went out.

4 Connect Google Calendar via scheduled sync so Starch can count how many recording days, sponsor calls, and production days actually happened last quarter.

5 Start your retro call with Meeting Notes running. Tell Starch at the top: 'This is our Q2 2026 retro — transcribe everything and flag decisions and action items.' You and your co-host or editor talk normally; Starch handles the capture.

6 When the call ends, Starch auto-generates a summary with key decisions, highlights, and action items extracted. Review it — usually takes 5 minutes to confirm it got the right owners on each item.

7 Tell Starch: 'Save this retro to our knowledge base under Quarterly Reviews, and link it to the Q1 retro doc.' Now you have a connected history instead of orphaned notes.

8 Tell Starch: 'Turn every action item from this retro into a task in Task Manager. P1 for anything sponsor-related, P2 for content pipeline, P3 for everything else.' Tasks appear with due dates and owners — no copy-paste.

9 Two weeks later, tell Starch: 'Show me all tasks from the Q2 retro. Which ones are overdue?' You get a real status check instead of guessing whether your co-host finished the thing they said they'd do.

10 At the next retro, start with: 'Pull the Q2 retro summary and show me which action items got closed and which didn't.' This becomes the opening five minutes of every future retro — accountability built in.

11 Over time, your Knowledge Management app becomes the institutional memory of the business. New collaborators (an editor you bring on, a VA) can search it and find actual decisions instead of asking you to re-explain everything.

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 Retrospective — 3-person newsletter + podcast

Sample numbers from a real run

Sponsor revenue Q2 (Stripe)	18,400
Sponsor revenue Q1 (Stripe)	12,200
Episodes shipped vs planned	11
Episodes planned	13
Open action items carried from Q1 retro	4
Of those, actually completed	1

Going into the Q2 retro, Starch pulls the pre-retro brief: $18,400 in sponsor revenue versus $12,200 in Q1 — solid growth — but only 11 of 13 planned episodes shipped, and 4 out of 5 Q1 action items were never closed. The meeting now has a real agenda: what caused the two missed episodes, and why is almost nothing from last quarter's retro getting done? During the call, Meeting Notes captures the conversation. The team decides to drop from two sponsors per issue to one for Q3 to reduce admin load, and assigns a task to reprice the single-sponsor slot to $2,800 per issue (up from $1,800) to make the math work. Starch extracts that as a P1 task assigned to the founder with a two-week due date. It also flags that the YouTube repurposing workflow was discussed in the Q1 retro and never actioned — creating a P2 task with a concrete deliverable: 'define a 3-step clip workflow by July 15.' The full retro summary gets saved to the knowledge base, linked to Q1, and tagged. Six weeks later, a new part-time editor searches the knowledge base for 'sponsor process' and finds the decision log without having to ask.

Measurement

How you'll know it's working

Action item close rate quarter-over-quarter (what percentage of retro commitments actually shipped)

Sponsor revenue per issue, tracked against what was decided in retro

Episodes shipped vs. planned each quarter

Time from retro to first task closed (measures whether retros are producing momentum or just talk)

Number of retro decisions searchable in the knowledge base (institutional memory depth)

Comparison

What this replaces

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

Notion + manual meeting notes

Works fine for writing things down, but there's no action-item extraction, no connection to your Stripe or Calendar data, and no way to query across past retros — you're still doing all the synthesis yourself.

Loom async retro

Good for solo reflection but produces a video nobody watches a second time and no structured action items — there's nothing to close or track.

Otter.ai for transcription

Accurate transcription, but stops there — you still manually extract decisions, copy action items somewhere else, and do your own follow-up tracking across separate tools.

Linear or Asana for action items

Solid task trackers but they don't sit inside your retro workflow — you still manually copy items from notes into tasks, and they have no connection to your Stripe or Notion data for context.

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

I'm a solo founder with one part-time editor. Is a 'team retrospective' workflow actually relevant to me?

Yes — the value isn't headcount, it's continuity. Without a structured retro, every quarter you're making decisions based on memory and vibes instead of what your Stripe revenue actually did, how many episodes you actually shipped, and which commitments from last quarter never got done. This workflow gives your 2-person operation the same institutional memory a 10-person team has.

What data can Starch actually pull in before the retro?

Starch syncs your Stripe data on a schedule (charges, invoices, payouts), your Google Calendar (what was scheduled last quarter), and your Notion (editorial calendar, past docs). Before the retro, you can ask Starch to summarize revenue trends, flag unclosed tasks from the prior retro, and show you the gap between planned and shipped content — all without any manual spreadsheet prep.

Does Starch transcribe the call itself, or do I need a separate tool?

Meeting Notes handles transcription, summary, and action-item extraction in one step. You don't need Otter.ai, a separate Notion template, or manual notes. After the call, Starch generates the summary and you review it — usually faster than copying notes would have been.

What happens to action items after the retro? Will they actually get tracked?

Task Manager captures action items from the retro summary and tracks them by priority and due date. You can ask Starch 'show me all open tasks from the Q2 retro' at any point and get an honest status. Task Manager is currently in development — request beta access if you want early access.

Is my data stored securely? Are you SOC 2 certified?

Starch is not currently SOC 2 Type II certified. That's worth knowing if you're connecting financially sensitive accounts. Stripe and Plaid data is synced into Starch's database on a schedule — if that's a concern for your business, it's the honest answer rather than something buried in a footnote.

What if my tools aren't in the list — like Beehiiv or Riverside?

Beehiiv and Riverside don't have dedicated scheduled-sync connections today, but if you can log into them through a browser, Starch can automate them through browser automation — no API needed. For analytics that live on a web dashboard, Starch can navigate there and pull what you need. It's not as clean as a native sync, but it works.

Can the knowledge base store more than just retros?

Yes. Knowledge Management is a full team wiki — you can store SOPs, sponsor rate cards, show format docs, editorial guidelines, and past retros all in one searchable place. The value compounds: once you have 4-6 quarters of retros in there, you can ask Starch questions like 'when did we last discuss raising sponsor rates?' and get an actual answer.