Strategy & Planning

How to run a retrospective or post-mortem as DTC Brand Founders

Strategy & PlanningFor DTC Brand Founders3 apps11 steps~22 min to set up

Your retrospectives happen in a Slack thread that dies after two days, or a Google Doc that nobody updates after the meeting. You ran a Black Friday campaign where CAC spiked 40%, a Klaviyo flow misfired on your best segment, and a stockout cost you an estimated $30k in lost revenue — and three months later you're making the same calls because nothing was written down in a place anyone can find. The action items from your last post-mortem live in someone's head or a Notion page no one has opened since December. You're a small team moving fast and retrospectives feel like a luxury, which means you keep repeating expensive mistakes.

Build this on Starch → See the apps used

Strategy & PlanningFor DTC Brand Founders3 apps11 steps~22 min to set up

Outcome

What you'll set up

A searchable post-mortem archive that captures what happened, what it cost (pulled from your actual Shopify, ad spend, and bank data), and what you decided — so next quarter's team doesn't start from zero

Automatic action-item extraction from every retrospective meeting, assigned to the right person with a due date, tracked in your project board so nothing disappears into a Slack thread

A living knowledge base where your DTC operating playbook — launch checklists, reorder triggers, channel-specific learnings — accumulates over time instead of living in someone's head

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 Project Management

Data sources & config

Meeting Notes transcribes your retrospective call live. Starch connects directly to Notion via its scheduled-sync integration so past docs and databases are available as context. Shopify and Meta Ads data are reachable from Starch's integration catalog (the agent queries them live) so the post-mortem can reference actual revenue numbers, ROAS figures, and CAC from the period under review. Plaid syncs your bank transactions on a schedule so cash burn during the quarter is grounded in real numbers, not estimates. Everything lands in the Knowledge Management app and action items flow directly into Project Management.

Prompts to copy

Transcribe today's Q1 post-mortem, pull out every decision and action item, assign each action item to a named team member, and save the summary to our knowledge base under 'Retrospectives > Q1 2026'

Search our past retrospectives for every time we discussed Klaviyo flow issues and summarize what we decided each time

Create a project called 'Q1 Retro Follow-ups', add tasks for every action item from today's meeting, set priority levels based on revenue impact, and assign due dates within the next two sprints

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

Walkthrough

Step-by-step

1 Before the meeting, tell Starch: 'Pull our Shopify revenue, Meta Ads spend, and Plaid transactions for Q1 2026 and give me a one-page summary of what the numbers looked like — CAC by channel, gross margin, refund rate, and any weeks where revenue dropped more than 15% week-over-week.' This becomes the factual anchor for your retro, not someone's memory.

2 Start your retrospective call with Meeting Notes running. It transcribes in real time so you and your team can stay in the conversation instead of typing.

3 After the call, Meeting Notes automatically generates a summary with key decisions and highlights. Review it — takes two minutes — and correct any misattributions before the summary gets archived.

4 Tell Starch: 'Extract every action item from this meeting summary, identify the owner based on who was mentioned in context, and suggest a priority level — P1 if it's tied to a revenue problem, P2 if it's a process fix, P3 if it's nice-to-have.' Review and confirm the list.

5 Tell Starch: 'Create a project in Project Management called Q1 2026 Retro Actions, add all confirmed action items as tasks with the assigned owners and priority levels, and set due dates two weeks out unless the item is P1, which gets one week.' Now the action items are tracked, not just written down.

6 Tell Starch: 'Save the full retrospective summary — decisions, action items, and the financial context — to the Knowledge Management app under Retrospectives > Q1 2026, and tag it with the channels we discussed: Meta Ads, Klaviyo, inventory.' This is the entry that your future self will search for.

7 Tell Starch: 'Search our Knowledge Management history for every retrospective where we flagged inventory or stockout issues. Summarize the pattern — what did we decide each time and did we follow through?' This step is where the archive starts paying back. You'll often find you've had the same conversation three times.

8 Based on the pattern search, write a playbook entry. Tell Starch: 'Create a new Knowledge Management page called Inventory Reorder Playbook and draft it based on the decisions and triggers we've identified across our last four retrospectives.' Now institutional knowledge is written down and findable, not locked in someone's tenure.

9 At the two-week mark, tell Starch: 'Show me all tasks in the Q1 2026 Retro Actions project that are overdue or unstarted, and tell me who owns each one.' This is your accountability check — takes 30 seconds.

10 At the start of your next retrospective, tell Starch: 'Pull the Q1 2026 Retro Actions project and show me completion rate, what shipped and what didn't, and which action items are being carried forward.' Your retrospective now opens with honest accountability, not optimistic memory.

11 Over time, tell Starch: 'Look across all our retrospective archives and identify the three categories of problems that come up most often.' This is the meta-retrospective — you'll see whether you're actually fixing things or relitigating the same issues every quarter.

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

Q1 2026 Post-Mortem — DTC Apparel Brand, $2.1M ARR

Sample numbers from a real run

Meta Ads spend (Q1)	187,000
Shopify revenue (Q1)	524,000
Estimated stockout revenue loss (Feb)	31,000
Klaviyo segment error — revenue missed	18,500
Refund rate spike (March) — gross margin hit	14,200

Before the Q1 retro, the founder asked Starch to pull Plaid transactions, Shopify revenue, and Meta Ads spend (queried live from Starch's integration catalog) for January through March. The summary came back showing CAC had climbed from $38 in January to $61 in March, a stockout on the brand's top SKU in February had cost an estimated $31k in lost sales based on prior-week velocity, and a misfired Klaviyo welcome sequence had skipped 2,200 new subscribers — accounting for roughly $18,500 in missed first-purchase revenue based on average order value. With those numbers on the table at the start of the meeting, the conversation was 45 minutes instead of 90 — no one had to argue about what actually happened. Meeting Notes captured the call. Action items came out clearly: the inventory reorder formula needed a buffer trigger at 3 weeks of supply instead of 2; the Klaviyo segment needed an audit before the next campaign launch; Meta creative testing needed a weekly review cadence instead of monthly. All three tasks landed in Project Management with owners and due dates before anyone closed their laptop. Two weeks later, two of three were done. The third — the Klaviyo audit — had slipped, and the task view made that visible immediately so it could get reassigned. By Q2 kickoff, the Knowledge Management app had four retrospective entries, a draft Inventory Reorder Playbook, and a Klaviyo QA checklist. The Q2 retro opened with Starch pulling the Q1 action completion rate: 8 of 11 items closed, 3 carried forward with explanations. That's a different conversation than starting from scratch every time.

Measurement

How you'll know it's working

Action item completion rate from each retrospective (target: >75% closed before next retro)

Time from retrospective meeting to archived summary with assigned tasks (target: same day)

Repeat issue rate — how often the same category of problem appears across consecutive retrospectives

CAC by channel for the quarter under review (Meta, TikTok, email), grounded in actual ad spend vs Shopify revenue

Gross margin impact of operational failures identified in retro (stockouts, refund spikes, misfired flows)

Comparison

What this replaces

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

Notion + Loom + manual action items in Slack

Works if someone on your team is disciplined enough to write everything up after every meeting — most DTC teams aren't, and the Notion pages go stale within a month because nobody owns the upkeep.

Fathom or Otter.ai for transcription only

Good at capturing what was said, but the transcript doesn't turn into tasks, doesn't connect to your Shopify or ad data for financial context, and the archive isn't searchable across meetings in a way that surfaces patterns.

Linear or Asana for action tracking only

Solid task tracking, but you're still manually copying action items from a separate doc or tool — the retro summary, the financial context, and the task list live in three different places and never talk to each other.

A consultant or agency-run quarterly review

Someone else synthesizes the data and runs the meeting, but it costs $3–10k per quarter, happens on their timeline, and the institutional knowledge goes into their deck, not your searchable internal archive.

On Starch RECOMMENDED

One platform — meeting notes, knowledge management, project management 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 pull actual revenue and ad spend numbers into the retrospective, or do I have to enter them manually?

You don't enter them manually. Before your retro, tell Starch what period to cover and what numbers you want — Shopify revenue, Meta Ads spend, Plaid bank transactions, refund totals — and it pulls them. Shopify and Meta Ads are queried live from Starch's integration catalog. Plaid syncs your bank data on a schedule so cash figures are already there. You get a financial summary grounded in real numbers before the meeting starts.

What if my team uses Google Docs or Notion for notes today — does Starch replace that or work with it?

Starch connects directly to Notion via its scheduled-sync integration, so your existing Notion pages and databases are available as context when Starch searches your history or drafts new playbook entries. If your team prefers to keep Notion as the archive, you can save retrospective summaries there through Starch. The Knowledge Management app inside Starch is an alternative if you want everything in one place — not a requirement.

Our retrospectives cover a lot of ground — product, ops, marketing, finance. Will Meeting Notes handle all of that or just surface the obvious stuff?

Meeting Notes transcribes everything and generates a summary with key decisions and highlights across all topics. The action item extraction works across domains — it doesn't filter by category. You review and confirm the list before it becomes tasks, so if the AI missed nuance or misattributed something, you catch it in the two-minute review step.

Is Starch SOC 2 certified? We're sharing financial data and call transcripts.

Not yet. Starch is not currently SOC 2 Type II certified. If your company has a compliance requirement that makes SOC 2 a hard gate, that's worth knowing upfront. It's on the roadmap.

What happens to the action items if someone leaves the team or changes roles?

Tasks in Project Management stay in the board regardless of personnel changes — they don't disappear when someone's name changes. You can reassign open tasks in bulk by telling Starch: 'Reassign all open tasks owned by [name] to [new owner].' The retrospective archives in Knowledge Management are tied to the content, not the person, so institutional memory doesn't walk out the door.

We only do formal retrospectives once a quarter. Is Starch worth it for that cadence?

The meeting transcription and action tracking pays back on a per-meeting basis — one $30k stockout insight that gets captured and acted on instead of forgotten is worth more than a year of the tool. But the compounding value is the knowledge archive: by the time you've run four quarterly retros, you have a searchable history of what you decided and whether it worked. That's the thing that most DTC teams don't have.