Strategy & Planning

How to run a retrospective or post-mortem as Construction and Contractor Founders

Strategy & PlanningFor Construction and Contractor Founders3 apps10 steps~20 min to set up

After a job closes — or goes sideways — you know you should sit down and figure out what went wrong. But 'running a retro' on a $280k bathroom remodel or a commercial fit-out that blew 40% of its labor budget means digging through QuickBooks for actual cost vs. estimate, scrolling through a Buildertrend job log you half-filled out, and trying to remember what you told the super on the phone in week three. The lessons never get written down. The same sub who caused the tile delay on the Elmwood job gets bid again six months later because nobody recorded why that job bled $18k. The knowledge lives in your head, or it's gone.

Build this on Starch → See the apps used

Strategy & PlanningFor Construction and Contractor Founders3 apps10 steps~20 min to set up

Outcome

What you'll set up

A structured post-mortem workspace per job that pulls actual costs from QuickBooks, meeting notes and field decisions from your call logs, and open punch items into one place — so you stop doing retros from memory

A searchable knowledge base of job lessons, sub performance flags, and bid assumptions that was correct vs. wrong — so your next estimate reflects what actually happened on the last five jobs

An action-item tracker tied to each retro so 'fix our drywall allowance' or 'require COI renewal 60 days out' becomes a real task with an owner and due date, not a sticky note

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

Knowledge Management Meeting Notes Task Manager

Data sources & config

Starch syncs your QuickBooks data on a schedule — invoices, bills, vendor payments, and job-level cost entries feed directly into your retro documents. Buildertrend and CoConstruct are browser-reachable via automation — no API required — so Starch can pull job logs, change orders, and schedule data directly from your field software. Notion, if you use it for job notes, connects through Starch's integration catalog and the agent queries it live when you open a retro.

Prompts to copy

Create a post-mortem document for the Hartwell Kitchen job: contract value $190,000, final cost $214,000, reasons I know about — tile sub delay added 9 days, demo scope was underestimated by $12k. Summarize what we'd change on the next bid and flag this sub for review.

Transcribe and summarize today's post-mortem call with Jake and the foreman on the River Road job. Pull out every decision we made, any blame-pointing at subs, and anything I said I'd do before the next bid cycle.

Create a task: update our framing labor rate in the estimating template, due in 7 days, P1. Reason: River Road retro showed we're $4.20/sqft under market.

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

Walkthrough

Step-by-step

1 Connect QuickBooks as a scheduled-sync provider so Starch always has current job costs, vendor bills, and payment records without manual exports.

2 Point Starch at Buildertrend or CoConstruct through browser automation — Starch logs in, pulls the job log, change order history, and schedule data for the job you're reviewing, no API needed.

3 Open the Knowledge Management app and tell Starch: 'Create a post-mortem page for [Job Name] — pull the final cost from QuickBooks and the change order log from Buildertrend, then give me a cost vs. contract summary broken down by trade.' Starch assembles it.

4 Run your retro call — with your foreman, your PM, or just yourself on a voice memo. The Meeting Notes app transcribes in real time, then generates a summary with key decisions, what went wrong, and what you committed to fixing.

5 Starch extracts action items from the meeting automatically — 'update drywall allowance,' 'blacklist ABC Tile,' 'add a 10-day weather buffer to exterior jobs' — and pushes them to Task Manager with priorities and due dates.

6 In Knowledge Management, prompt Starch: 'Flag this subcontractor for performance review based on the River Road retro notes, and add a note to their vendor profile.' Now that information survives the next person you hire.

7 Ask Starch to identify patterns across the last four retros: 'Which cost categories overran by more than 10% on the jobs we've documented so far? Which subs show up in more than one post-mortem?' The knowledge base answers this without you re-reading everything.

8 Use the retro output to update your estimating assumptions — prompt Starch: 'Draft a one-page estimating note for tile work that reflects the Hartwell and River Road overruns. Include revised allowance per sqft and COI requirement language.'

9 Archive the completed retro in Knowledge Management with job type, size, trade mix, and outcome tags so future searches for 'kitchen remodel over $150k' or 'tile sub issues' surface relevant history immediately.

10 Schedule a recurring reminder: 'Every time a job closes in QuickBooks — final invoice paid — create a post-mortem task for me, P2, due 10 business days later.' Starch triggers off your QuickBooks sync so no job slips through without a debrief.

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

River Road Commercial Fit-Out — April 2026 Post-Mortem

Sample numbers from a real run

Contract value	340,000
Final job cost (QuickBooks actuals)	391,500
Labor overrun — framing + drywall	28,400
Change orders collected	19,000
Change orders NOT collected (unsigned)	14,200
Demo scope underestimate	9,100

The River Road job closed at $391,500 against a $340,000 contract — a $51,500 overrun. Starch pulled the final cost breakdown from QuickBooks in about 30 seconds and matched it against the original bid line items. The retro call with the foreman and Jake ran 40 minutes; Meeting Notes captured it and surfaced three things nobody had written down: (1) the framing sub invoiced at $4.20/sqft above the bid rate and the crew foreman verbally approved it without a written CO, (2) demo in the back office hit a double-layer subfloor that cost nine days and $9,100, and (3) $14,200 in approved-but-unsigned change orders were still outstanding because the GC's owner 'was traveling.' Starch created tasks for each: chase the $14,200 with a deadline, update the framing labor rate in the estimating template, and add a subfloor inspection line to all commercial demo scopes. The Knowledge Management app now has a page tagged 'commercial fit-out / demo risk / unsigned COs' — the next time you're bidding a similar job, that $9,100 subfloor lesson is one search away instead of buried in a job folder nobody opens.

Measurement

How you'll know it's working

Cost overrun by trade category (labor vs. materials vs. sub invoices) as a percentage of bid, per job

Unsigned or uncollected change order dollars at job close

Number of post-mortems completed within 10 business days of final invoice

Repeat sub issues flagged across jobs (same sub appearing in 2+ retros)

Estimating accuracy improvement over rolling 6 jobs — are your bid-to-actual gaps shrinking?

Comparison

What this replaces

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

QuickBooks job costing reports alone

Shows you the numbers but captures none of the narrative — why the tile sub cost you two weeks, what the foreman said, or what you'd do differently. You leave the meeting and the context is gone.

Buildertrend or CoConstruct built-in reports

Good for schedule and change order history, but siloed from your actual financials in QuickBooks; combining the two into a retro still requires manual work and exports.

Google Docs retro template

Free and flexible, but it's a document graveyard — nothing is searchable across jobs, action items don't go anywhere, and new employees can't find what you've learned.

Procore

Built for this kind of structured job documentation, but priced for 50+ person commercial shops; overkill and expensive for a GC running 6-10 jobs at a time under 20 crew.

Notion + manual setup

Starch connects to Notion from its integration catalog and can query your existing pages live — you don't have to abandon your Notion setup, but Starch adds the AI search, auto-categorization, and action-item extraction on top of it.

On Starch RECOMMENDED

One platform — knowledge management, meeting notes, 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

My job notes are split between Buildertrend, a shared Dropbox folder, and some texts I sent the foreman. Can Starch actually pull from all of that?

Buildertrend and Dropbox are both browser-reachable, so Starch can automate through them — no formal API integration required. Text messages are the one thing it can't reach directly; the practical fix is to paste or dictate the key decisions from those threads into your retro document at the start of the call, and Meeting Notes will capture everything from there.

Does Starch connect to QuickBooks deeply enough to pull job-level cost breakdowns, or just high-level totals?

Starch syncs your QuickBooks data on a schedule and pulls invoices, bills, vendor payments, and journal entries at the entity level — so you can ask for cost by vendor, by trade category, or by date range for a specific job. Note: QuickBooks report views like the built-in P&L are temporarily unavailable pending a connector fix, but the underlying entity data — every bill and invoice — syncs normally and Starch builds the summary from that.

I don't run my retros on a call — I usually just think through the job alone and write notes. Does Meeting Notes still help?

Yes. You can talk through the retro as a voice note or just type your thoughts directly into the Meeting Notes app; it doesn't require a live call with multiple people. The output is the same — a structured summary, decisions captured, and action items extracted — whether you're talking to a room or talking to yourself.

What if I want to search across retros from the last two years? Will Starch find patterns?

That's exactly what the Knowledge Management app is built for. Once your retros are archived there, you can ask things like 'which jobs had tile sub issues in the last 18 months' or 'show me every job where demo scope overran by more than 8%' and the AI searches across all your documents instantly. The more retros you log, the more useful the pattern-finding becomes.

Is my financial data secure? I'm connecting QuickBooks and Plaid.

Worth asking directly: Starch is not SOC 2 Type II certified today. If your contracts or insurance require SOC 2 Type II on any tool that touches financial data, that's a real constraint to know about. For most small GCs under 20 crew, it's not a blocker — but you should make the call with full information.

Can Starch automatically kick off a post-mortem when a job closes, or do I have to remember to start it?

Yes — tell Starch: 'When a final invoice is marked paid in QuickBooks, create a post-mortem task for me, P2, due 10 business days out.' Since Starch syncs your QuickBooks data on a schedule, it sees the invoice status change and triggers the task automatically. You stop relying on yourself to remember.