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 at any moment, each run by a project manager juggling a site team, a supplier list, a budget, and a nervous client. The work is excellent. The reporting is held together with spreadsheets and the PM's memory.

The Pain

Every Monday, each PM spends the first two hours of the week assembling a status report. They pull this week's costs from the accounting system, the open issues from the site WhatsApp, the delivery dates from supplier emails, and the budget position from a master spreadsheet — and hand-paste it all into a client update. Two hours × a dozen PMs × every week. And because it's manual, it's inconsistent: when a PM is off sick, the client simply gets nothing, and nobody else can reconstruct the picture.

The Move

This is an Agent move. One step up from a connector: instead of asking a question in a chat window, you give a CLI agent — Claude Code or OpenAI's Codex — standing access to several systems and let it do the multi-step assembly on a schedule.

Brightseam sets up an agent with read access to three places: the accounting export, the shared project folder, and the supplier-email mailbox. Its weekly instruction: "For each active project, pull this week's spend, compare it to budget, list deliveries due in the next ten days, and flag anything that slipped. Write it up in our client-update format and drop a draft in the project folder by 7am Monday."

The PM arrives Monday to a drafted report per project — numbers already reconciled, slippage already flagged — and spends fifteen minutes reviewing and sending instead of two hours assembling. When a PM is off, the reports still appear. The single point of failure is gone.

Why most 80-person fit-out firms miss this

Because "automation" in construction means a £40k project-management platform that every PM quietly refuses to update, so the data inside it is always a week stale and the reports built from it are fiction.

The contrarian point: the agent route doesn't ask anyone to change how they work. The costs still live in the accounting system, the chatter still lives on WhatsApp, the deliveries still arrive by email — the agent reaches into the mess that already exists and assembles the report from it. You're not migrating to a new system; you're hiring something to read the systems you've got. That's the difference between a tool people resist and a tool that just shows up Monday morning with the work done.

The translation

The pattern — give an agent standing access to several systems and a scheduled job — fits any business where a skilled person spends hours each cycle assembling a recurring document from scattered sources:

• A 50-person agency where account leads rebuild the same campaign-performance deck every month from four ad platforms.
• A wholesaler whose finance team manually reconciles supplier invoices against delivery notes every fortnight.
• A clinic group compiling a regulator-ready compliance summary each quarter from rota, training, and incident logs that live in three different places.