The Monday That Builds Itself

The Company

Brightseam Interiors fits out offices, shops, and clinics across the north of England. Eighty people, a dozen live projects on the go at once, and each one has a project manager keeping track of a site team, a supplier list, a budget, and a client who wants to know what's happening. The actual work is solid. The reporting is held together with spreadsheets and whatever the PM can remember.

The Pain

Emma manages three projects. Every Monday she opens her laptop and spends the first couple of hours doing the exact same thing she did the Monday before: pulling costs out of the accounting system, scrolling back through the site WhatsApp to find the open issues, checking supplier emails for delivery dates, cross-referencing the budget spreadsheet, then copying it all into the client update template by hand.

Every PM on the team does this. And because it all lives in their heads and their inboxes, if Emma's off sick on Monday, her clients just don't hear anything. Nobody else can piece together her picture. It's not that she's doing something wrong — it's just that the information is scattered across three different places and only she knows where to look.

The Move

Set up a CLI agent — Claude Code or OpenAI's Codex — with read access to three places: the accounting export, the shared project folder, and the supplier email mailbox. Give it a standing instruction and a schedule.

Something like: "For each active project, pull this week's spend, compare it to budget, list deliveries due in the next ten days, flag anything that's slipped. Write it up in our client-update format and drop a draft in the project folder by 7am Monday."

Emma arrives Monday morning and there's a drafted report waiting for each of her projects — figures already pulled, slippage already flagged. She reads through it, adjusts anything that needs a human eye, and sends. That takes fifteen minutes instead of two hours. When she's off, the drafts still appear. Her clients still hear something.

The blind spot

In construction, "automation" tends to mean a £40k project management platform that gets rolled out with great fanfare and then quietly stops being updated because the PMs are too busy to log things in yet another system. Six months in, the data inside it is stale, and any report built from it is fiction.

This sidesteps all of that. It doesn't ask anyone to change how they work. The costs stay in the accounting system. The site chat stays on WhatsApp. The delivery confirmations keep arriving by email. The agent just reads all of it and does the assembling. You're not migrating to a new system — you're putting something to work on the systems you've already got.

The pattern

The same move fits any business where someone capable spends a chunk of their week pulling the same information from the same scattered places and writing it up in the same format:

• A 50-person agency where account leads rebuild the same campaign performance deck every month from four different ad platforms.
• A wholesaler whose finance team manually matches supplier invoices against delivery notes every fortnight.
• A clinic group that compiles a compliance summary each quarter from rota records, training logs, and incident reports sitting in three separate systems.