Strategy & Planning

How to run a retrospective or post-mortem as Event Agency Founders

Strategy & PlanningFor Event Agency Founders3 apps10 steps~20 min to set up

After a 200-person corporate gala or a three-day conference wraps, you have six vendor email threads in Gmail, a debrief voice note you recorded in the Uber home, a Google Doc your second coordinator started but never finished, and a HoneyBook/Dubsado project that shows 'complete' but captures none of what actually went wrong. The retro either doesn't happen or happens once over a 20-minute Zoom call where everyone says 'it went great' and nobody writes anything down. Three months later you're quoting a similar event and you have no record of why the AV vendor was swapped last-minute or what the real labor hours were versus the estimate.

Build this on Starch → See the apps used

Strategy & PlanningFor Event Agency Founders3 apps10 steps~20 min to set up

Outcome

What you'll set up

A searchable retro archive where every post-mortem — vendor issues, budget variances, timeline slippage, client feedback — lives in one place and can be pulled up when you're quoting a similar event six months from now

A structured debrief workflow that captures what happened, what you'd change, and concrete tasks for the next event — automatically assigned to the right team member, not buried in a chat thread

A living knowledge base that turns repeated retro findings into standing operating procedures your team can actually find and follow, so you stop solving the same catering problem twice

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

Data sources & config

Meeting Notes captures your debrief call — connect Google Calendar so Starch syncs your scheduled events on a schedule and knows which meeting is the retro. Gmail is connected from Starch's integration catalog so the agent queries your vendor threads live during the debrief summary. Project Management and Knowledge Management are standalone Starch surfaces — no external sync needed. Google Drive can be connected from Starch's integration catalog so the agent pulls in any pre-existing debrief docs or run-of-show files live.

Prompts to copy

Transcribe and summarize our post-event debrief for the Henderson Corporate Retreat. Extract: what went well, what went wrong, vendor issues flagged, budget variance items, and action items with owners. Archive it under the Henderson project.

Create follow-up tasks from the Henderson retro: assign the AV vendor replacement research to me, due in 5 days; assign the revised day-of timeline template update to Jordan, due in 7 days; flag the catering overage for the next client proposal review.

Add a new page to our Knowledge Base under 'Vendor Lessons' summarizing what we learned about using backup AV vendors for outdoor events over 150 guests. Pull from the Henderson and the Marlowe Conference retros.

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

Walkthrough

Step-by-step

1 Within 48 hours of event close, schedule a 30-minute debrief call with your core team — your coordinator, any on-site leads. Open Meeting Notes in Starch before the call starts so it transcribes in real time.

2 Run the debrief on the call without anyone taking manual notes. Talk through the timeline: what was late, what was swapped, what the client flagged, where you went over budget. Meeting Notes captures all of it.

3 After the call ends, ask Starch to generate the post-mortem summary: 'Summarize the Henderson Corporate Retreat debrief. Separate findings into: vendor performance, budget vs. actuals, timeline execution, client feedback, and what we'd do differently.'

4 Review the summary — add any detail you remember that wasn't said on the call. This is the moment to note the real labor hours versus quoted hours, something most agency retros skip entirely.

5 Tell Starch to extract action items and create tasks: 'Pull every action item from the Henderson retro summary and create Project Management tasks. Assign anything about vendor research to me, anything about template updates to Jordan, and set due dates within two weeks.' Starch creates the tasks without you clicking through a form.

6 Pull up your Knowledge Management wiki and tell Starch to check whether this retro confirms or contradicts any existing vendor or ops documentation: 'Search our knowledge base for anything about outdoor AV vendors. Summarize what we already have and flag if the Henderson findings change any of it.'

7 If the retro surfaces a pattern you've seen before — caterers running late, clients requesting timeline changes day-of — write it into a standing SOP page: 'Add a new Knowledge Base page under Event Ops > Catering: our standard buffer policy for catering delivery windows, based on findings from the last three retros.'

8 Check the Project Management board one week after the retro to confirm action items are moving. If any are overdue, Starch surfaces them automatically — ask: 'Show me all tasks created from event retros that are past due.'

9 Before quoting your next similar event — same venue type, guest count range, or client industry — search the retro archive: 'Find all post-mortems for corporate events over 150 guests at hotel venues. Summarize the budget variance patterns and vendor issues we flagged.' Use that to pressure-test your next proposal.

10 Once a quarter, ask Starch to synthesize your retro archive into a pattern report: 'Look across all event retros from the past six months. What are the top three recurring problems and what SOPs do we already have to address them?' Turn gaps into new Knowledge Base pages before the next busy season.

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

Henderson Corporate Retreat — March 2026 Post-Mortem

Sample numbers from a real run

AV vendor (original quote)	4,200
AV vendor (actual — emergency backup called day-of)	6,100
Catering overage (guest count revised 72 hours out)	1,350
Staff labor (actual vs. quoted)	2,800
Staff labor (quoted)	2,200
Total budget variance	3,850

The Henderson Corporate Retreat was a 175-person two-day offsite at a hotel in Austin. Projected budget was $38,000; actual came in at $41,850 — a $3,850 overrun. The debrief call ran 28 minutes. Meeting Notes transcribed the whole thing and generated a summary in under two minutes: AV vendor no-showed at 7 AM load-in and a backup vendor was called at a $1,900 premium; catering was re-quoted when the client added 15 guests at day-minus-3; on-site staffing ran 3 hours over the estimate because the venue's freight elevator was slower than projected. Starch created four tasks from the retro: research two backup AV vendors with confirmed availability guarantees (assigned to founder, due in 5 days), update the catering contract template to include a 10% guest-count buffer clause (assigned to Jordan, due in 7 days), add freight elevator access time to venue intake checklist (assigned to founder, due in 3 days), and flag the $3,850 variance in the Henderson client file for reference in future similar proposals. The AV findings were added to the 'Vendor Lessons' page in the Knowledge Base. Two months later, quoting a similar 160-person Austin offsite, the founder pulled up that page in 30 seconds and added a $1,500 AV contingency line to the proposal without having to remember why.

Measurement

How you'll know it's working

Budget variance per event (quoted vs. actual, broken down by vendor category)

Retro completion rate — percentage of closed events that have a documented post-mortem within 72 hours

Recurring issue rate — how many retro findings repeat across multiple events (tracked quarterly)

Action item close rate — percentage of retro-generated tasks completed before the next event of the same type

SOP coverage — number of known recurring issues that have a documented procedure in the knowledge base

Comparison

What this replaces

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

Google Docs retro template shared in Drive

Works fine for a single debrief but creates no searchable archive — six months later you can't find the doc or connect its findings to a new quote without manually digging through folders.

Notion for retros and SOPs

Notion is a solid wiki but the debrief capture is still manual — you're writing the summary yourself, not pulling it from a recorded call, and action items don't automatically become tasks in a tracker.

HoneyBook / Dubsado project notes

These CRMs track what happened to the client relationship, not what happened operationally — vendor issues, timeline slippage, and labor variances don't have a natural home there and usually don't get written down at all.

Otter.ai for meeting transcription

Otter transcribes the call well but doesn't connect to your task tracker, knowledge base, or next proposal — you still have to manually move every insight somewhere useful.

On Starch RECOMMENDED

One platform — meeting notes, project management, knowledge 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 don't do formal debrief calls — it's usually just me and one coordinator texting after the event. Can Starch still help?

Yes. You can type a debrief directly into Starch as a brain dump — 'Here's what happened at the Henderson event: AV was late, catering went $1,350 over, client loved the florals, we need a better load-in checklist.' Starch structures it into a post-mortem, extracts action items, and archives it. The meeting transcription feature is useful when you do have a call, but it's not required.

Does Starch connect to HoneyBook or Dubsado so the retro can reference what was actually quoted versus invoiced?

HoneyBook and Dubsado are reachable from Starch's integration catalog — the agent can query them live when your app runs. That means you can pull a project's contract value or invoice total into the retro summary. If you run into a gap with a specific field, Starch can also automate your HoneyBook account through your browser — no API needed.

What happens to the knowledge base over time — does it get stale?

The Knowledge Management app includes stale content detection, so Starch flags pages that haven't been updated in a while and prompts you to review them. For a small event agency, this matters most for vendor SOPs — the AV vendor list from 18 months ago may be outdated. You can ask Starch to surface all vendor-related pages older than 90 days and review them before your next busy season.

Is Starch SOC 2 certified? We sometimes handle client data in our retros.

Not yet — Starch is not SOC 2 Type II certified today. If your clients have strict data handling requirements and you're capturing sensitive event details in retros, that's worth knowing upfront. For most small agency use cases — vendor issues, internal process notes, budget variances — this isn't a blocker, but it's an honest limit.

We run 30+ events a year. Will the retro archive stay searchable at that volume?

Yes. The Knowledge Management app is built for exactly this — AI-powered search across all your archived content. At 30 events a year, after two years you'll have 60+ post-mortems. Searching 'outdoor events over 150 guests, vendor issues' should surface the relevant ones in seconds, which is the whole point of building the archive in the first place.

Can Starch pull in the actual vendor invoices from Gmail to compare against what we quoted in the retro?

Yes. Starch connects directly to Gmail, and the agent queries your messages live when your app runs. During a retro summary, you can ask Starch to pull the vendor invoice thread for a specific event and extract the final invoice amount — so the budget variance in your retro is based on the actual number from the email, not your memory of it.