Caught slipping project milestones two weeks earlier for a 40-person commercial fit-out contractor
Client snapshot
A commercial fit-out contractor with 40 people and 15 to 20 jobs running at once: offices, shops, small clinics. Project managers tracked every job in Quickbase, with dates for design sign-off, materials on site and handover, plus a start and end date for work on site.
The problem
The dates were all in Quickbase, but nobody looked at them together. The operations director pieced together the week by opening job records one by one, which took most of Monday morning. Slippage showed up late. A delayed materials delivery was noticed when the crew turned up to an empty site, and by then the handover date was already lost.
What we built
A weekly briefing and a timeline that both read from the same Quickbase tables.
Every Monday at 6am, n8n pulls each active job's milestone dates and status. It compares them with the plan and with last week. Claude writes a one-screen email to the operations director and the project managers, in five parts: the headline, what moved, what slipped, what to watch and what finished. "Watch this" lists jobs where a milestone is due within two weeks and the step before it isn't done.
Inside Quickbase we added a timeline report with four lines per job: the three milestones as points and the on-site work as a span between its start and end dates. The briefing links straight to it, so the director can open the jobs it flags.
For the first three months we tuned the briefing every month, dropping what nobody read and adding what they kept asking for.
Results, one quarter in
- Warning before a missed milestone: a couple of days → about two weeks.
- The Monday status check: around 45 minutes of clicking → a three-minute read.
- Jobs handed over late: six to eight a quarter → two or three.
- Project managers now raise delays in the Monday meeting instead of hearing about them from it.
Quote
"The email tells me which three jobs to call about. I don't open the others unless I want to." Operations director
Build snapshot
- Timeline: 5 business days
- Stack: Quickbase, n8n, Claude, Gmail
- Investment: $1,500
- Who owned it: the operations director set the thresholds; one project manager owns the milestone fields in Quickbase.
The pattern
This is the pattern we ship in the Weekly Briefing engagement. Here the source was a project database; the same build reads from a CRM, billing or analytics just as well.
This is an illustrative composite drawn from operator engagements. Names, identifying details, and exact metrics are anonymised. The workflow, stack, and approach are real.
Looks like your situation?
A 30-minute call tells us whether the same pattern fits your operation, and what it would cost to ship it.