MCP and the connected construction office
A quiet technical standard is changing what AI can do: instead of answering questions, it can now operate your tools. What MCP means in practice.
Blog
Practical, no-hype writing on automation, site reporting, data and adoption.
A quiet technical standard is changing what AI can do: instead of answering questions, it can now operate your tools. What MCP means in practice.
Zapier for speed, Make for visual complexity, n8n for self-hosting and data control, custom when the workflow is the business. An honest framework.
Orders still arrive as PDFs, emails and phone calls, and someone retypes them. How UK manufacturers automate order entry with extraction and validation.
Software does not fail in construction. Workflows do. How zero-click automation makes the systems you already own do the job you bought them for.
Five construction workflows ranked by payback speed: site capture, enquiry routing, document filing, meeting notes and the payment calendar. What each needs.
Procurement on small jobs is mostly chasing. Automating enquiries, reminders and quote logging shortens the cycle and leaves a record of who was asked what.
Construction people are professionally sceptical, and they are right to be. What actually works when introducing AI to site managers, QSs and estimators.
Pounds-saved claims invite argument. Hours are observable. How to measure automation in time returned per person, with a baseline set before you build.
A commercial manager on £70k spending 15 hours a week on automatable tasks costs roughly £26,000 a year in wasted capacity. It never shows on a line item.
Where automation genuinely pays for a UK small business, where the money gets wasted, and a first 90 days plan that starts with the process, not the platform.
Buyers now ask AI assistants instead of searching. GEO is making your business one of the sources those assistants read, trust and cite. A plain guide.
Small contractors pay an invisible tax in evening admin: diaries, timesheets, invoicing, chasing. Which jobs automate well, which never should, and why.