Strategy & Planning

How to run a retrospective or post-mortem as Professional Services Founders

Strategy & PlanningFor Professional Services Founders3 apps12 steps~24 min to set up

After a project wraps or a client relationship goes sideways, you know you should run a retrospective — but the actual doing of it gets buried under the next proposal deadline. When you finally sit down for it, you're reconstructing the timeline from Slack threads, digging through Gmail for the client escalation email, hunting down the original SOW in Google Drive, and asking the project lead what actually happened. Nobody has notes. Action items from the last retro lived in someone's head or a doc nobody updated. Six months later you're making the same scoping mistake with a different client. The institutional memory of a 12-person firm is frighteningly thin.

Build this on Starch → See the apps used

Strategy & PlanningFor Professional Services Founders3 apps12 steps~24 min to set up

Outcome

What you'll set up

A structured post-mortem workflow that pulls meeting notes, project decisions, and Slack threads into one place before your retrospective session even starts

A searchable knowledge base where every retro's findings, process changes, and open action items live — so next quarter's onboarding or proposal actually reflects what you learned

A task tracker that turns retro action items into assigned, prioritized work items with due dates instead of letting them evaporate after the meeting

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 captures your close-out call transcript in real time. Notion is connected via Starch's scheduled sync so existing project docs and decision logs are available as context. Gmail and Google Calendar are synced on a schedule so the agent can pull the full thread history and meeting timeline for the engagement. Slack is connected from Starch's integration catalog; the agent queries it live to surface relevant channel history. Project Management is the native Starch app — no additional connection needed. Action items from the retro flow directly into the task board.

Prompts to copy

Transcribe and summarize our project close-out call for the Meridian Partners engagement. Extract key decisions, what went wrong with the original scope, what the client flagged in week 6, and any process gaps the team mentioned. Assign follow-up action items by person.

Create a retrospective entry in our knowledge base for the Meridian Partners project. Include: timeline, what worked, what didn't, root cause of the scope creep, and the three process changes we agreed to. Tag it under 'Client Delivery' and 'Scope Management' so it surfaces during future proposal prep.

From the Meridian post-mortem action items, create tasks in our project board: assign the SOW template update to Sarah (due in two weeks, P1), the utilization review process to me (due end of month, P2), and the client check-in cadence doc to Marcus (due next Friday, P2).

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

Walkthrough

Step-by-step

1 Before the retrospective session, open Meeting Notes and prompt Starch to pull together a pre-read: timeline of key milestones from Google Calendar sync, the client escalation thread from Gmail sync, and any relevant Notion docs from the project folder. This replaces 90 minutes of manual archaeology.

2 Run your retrospective meeting with Meeting Notes active. It transcribes in real time so your lead consultant isn't splitting attention between the conversation and a notes doc.

3 After the call ends, Meeting Notes generates a structured summary: what went well, what didn't, key decisions made, and a raw list of action items with names attached.

4 Review the summary and prompt Starch to draft a formal retrospective document: 'Write up the Meridian post-mortem as a structured entry — root cause of the week-6 escalation, scope decisions that backfired, three process changes we're making, and one thing the team did exceptionally well.'

5 Save that document into your Knowledge Management base under the right tags (client industry, project type, failure mode). Starch auto-categorizes it and flags if similar issues have appeared in past retros.

6 Search the knowledge base before your next comparable proposal: 'What scope or delivery problems have we had on fixed-fee strategy engagements under $80k?' Starch surfaces relevant past retros instantly.

7 Convert every action item from the retro summary into a Project Management task via a single prompt. Assign owners, set priorities (P1–P4), and attach due dates without touching a form.

8 Set a recurring check-in by prompting Starch to notify you two weeks out: 'Remind me to review whether the Meridian retro action items are closed before we start the next similar engagement.'

9 At the start of each new project kickoff, prompt the Knowledge Management app: 'What have we learned about managing client expectations on brand strategy projects?' The answer comes from your own past retros, not a generic article.

10 Quarterly, run a meta-retro: prompt Starch to surface all retrospective entries from the last 90 days, identify the two or three recurring themes, and draft a 'lessons learned' section for your team wiki.

11 When onboarding a new senior consultant, point them to the Knowledge Management base: 'Read these five post-mortems before your first client engagement.' Starch can build an onboarding path that sequences those docs automatically.

12 Track retro completion rate as a team health metric — if you're closing out projects without a retro, the task board will show it because the close-out task never gets created.

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

Meridian Partners brand strategy close-out, March 2026

Sample numbers from a real run

Original project fee	62,000
Unplanned scope additions (absorbed)	14,500
Senior consultant hours over estimate	8,200
Retro action: SOW template revision (estimated save on next project)	12,000

The Meridian engagement closed nominally at $62k but the team absorbed $14,500 in scope creep and burned $8,200 in unbillable senior hours on a second round of executive interviews that weren't in the SOW. The close-out call happened but no structured retro did — the project lead left notes in a personal doc that nobody else ever read. Running the post-mortem in Starch six weeks later, the team pulled the full Gmail thread showing Meridian's CFO flagged the scope ambiguity in week 3 (an email that got buried), the Google Calendar log showing the engagement ran 11 weeks against a 7-week plan, and the original Notion brief where the deliverable list was vague on 'stakeholder alignment workshops.' Meeting Notes captured the 40-minute retro call. Starch identified the root cause in two minutes: the SOW used 'workshops as needed' language on a fixed-fee project, a pattern that also appeared in a 2025 retro for a different client. The Knowledge Management entry now tags both under 'scope — fixed-fee ambiguity.' Three Project Management tasks were created from the retro: update the SOW template (Sarah, P1, 2 weeks), add a week-3 check-in milestone to all fixed-fee projects (founder, P2, end of month), draft a change-order policy doc (Marcus, P2, 10 days). If those changes hold, the estimate on the next comparable engagement is that $12k in absorbed scope gets billed or prevented.

Measurement

How you'll know it's working

Retro completion rate — percentage of closed projects that have a documented post-mortem in the knowledge base

Recurring issue rate — how many retros surface the same root cause category (scope ambiguity, estimate error, stakeholder misalignment) quarter over quarter

Action item close rate — percentage of retro tasks completed before the next comparable project kicks off

Time to retro — days between project close and completed post-mortem entry (target: under 10 business days)

Knowledge base retrieval usage — how often the team searches past retros before writing a proposal or SOW

Comparison

What this replaces

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

Notion doc + Slack DM follow-up

Most consultancies already do this; the retro document gets written once and never searched again, and Slack action items disappear within a week.

Confluence + Jira

Works well for 50-person product teams; at 12 people the configuration overhead eats the time savings and you still need someone manually linking retro findings to process tickets.

Miro retrospective templates

Great for the facilitated session itself but produces a board image, not a searchable document — nothing flows downstream into task assignment or future proposal prep.

Otter.ai or Fireflies for transcription only

Captures the meeting but the summary sits in a separate tool; you still manually move action items into whatever task system you use, and the institutional knowledge goes nowhere.

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

We already use Notion for project docs. Do we have to migrate everything into Starch?

No. Starch syncs your Notion data on a schedule so the agent can read your existing pages and databases as context when building a retrospective summary or searching past projects. Your Notion stays where it is; Starch reads across it.

Our retros happen on Zoom — can Starch capture those?

Meeting Notes works for calls you run through your browser. For recorded Zoom calls, you can paste in a transcript or upload the recording and prompt Starch to summarize and extract action items from it. Live transcription works best for calls initiated from within the Starch environment.

What if a project lead did take notes — can Starch work with a doc they already wrote?

Yes. Paste the doc into the Starch chat or link the Notion page and prompt: 'Turn this project debrief into a structured retrospective entry with root cause, process changes, and action items.' Starch reformats and stores it in the knowledge base so it's actually searchable next time.

Is the knowledge base searchable by client or project type, or is it just keyword search?

The Knowledge Management app uses AI-powered search, so you can ask it questions in plain language — 'what went wrong on our last two SaaS client engagements' — and it surfaces relevant entries even if the exact words don't match. It also auto-categorizes new entries and can flag when similar issues appear across multiple retros.

We're not SOC 2 certified as a firm — does Starch have a compliance issue we should know about?

Starch is not SOC 2 Type II certified today. If your clients require you to store project documentation only in SOC 2-certified infrastructure, flag that before storing sensitive client deliverables or PII in Starch. For most 12-person consultancies running internal retros and process docs, this isn't a blocker — but it's worth naming honestly.

Will action items actually get done, or will they sit in the task board the same way they sat in the Notion doc?

The task board won't force anyone to do work. What it does: assigns a named owner, sets a priority level (P1–P4), and surfaces overdue items. You can prompt Starch to send a Slack message to the assignee as a reminder — Slack is connected from Starch's integration catalog. The accountability is still yours to manage, but the visibility gap ('I forgot that was assigned to me') gets closed.