Chris M. / 7 August 2026 / Reviewed 7 August 2026

Microsoft 365 Copilot or a Custom Construction AI Assistant?

The decision usually arrives as two documents on the same desk in the same fortnight. One is a renewal quote from the Microsoft partner, with a line for Microsoft 365 Copilot licences across the business. The other is a proposal from a consultancy for a bespoke assistant that will read your drawings, your contracts and your site records. Both are credible, both are expensive, and neither party is disinterested.

For most UK contractors the right first move is Microsoft 365 Copilot, because the add-on sits on a Microsoft 365 subscription the business already pays for and it reaches the mail and documents the business already runs on. A custom assistant earns its cost only where Copilot's documented boundaries actually bite, and in construction there are three that do: shared project mailboxes, drawing and programme file formats, and register-style questions that Microsoft states its tooling cannot answer.

That is a narrower claim than either sales conversation will make, and the rest of this guide is the evidence for it. Every limitation described below is quoted from Microsoft's own current documentation rather than inferred from a demonstration, because a consultancy that builds custom systems has an obvious interest in the licence looking weak, and a reader is right to discount an argument that depends on taking our word for it.

What the licence actually buys

Microsoft 365 Copilot uses organisational data and the web, and it requires an add-on licence ¹. That last point causes more confusion than anything else in the product, because there is a second thing called Microsoft 365 Copilot Chat which uses the web, allows a user to supply organisational data by hand, and does not require an additional licence ¹. A director who has been told the business already has Copilot is often describing the second one.

The paid product works by grounding. Grounding means supplying the model with source material relevant to the question rather than relying on what it learned in training, and Copilot's source material is Microsoft Graph. It uses content there to personalise responses with a user's work emails, chats and documents, and it only shows data that user has permission to access ¹.

Two consequences follow, and they pull in opposite directions. The first is that Copilot is genuinely good at the work that lives inside Microsoft 365, which in most contracting businesses is a great deal of the work: correspondence, meeting notes, monthly reports, first drafts of anything. The second is that its reach stops where Microsoft 365 stops, and a construction business keeps a surprising amount of its operational life outside those walls.

What it costs once you multiply it out

The enterprise add-on is listed at £23.10 per user per month paid yearly, excluding VAT, and a separate licence for a qualifying Microsoft 365 plan is required on top ⁵. The Business add-on, which requires a Microsoft 365 Business plan, lists at £16.10 per user per month paid yearly, excluding VAT, and is being offered at £13.80 under a discount available between 1 July 2026 and 30 September 2026 ⁴. The promotional rate requires an annual commitment and applies to the first year, so a business reading this after September should plan on the list price.

Multiply that across the people who would actually use it. As an illustration, 40 office staff on the enterprise add-on is a little over £11,000 a year before VAT ⁵, on top of the Microsoft 365 licences already being paid for, and none of that money buys a single hour of anyone's time being changed. That is the arithmetic that makes the comparison real: the licence is an annual and permanent cost, where a bespoke build is mostly a one-off, so the two have to be compared over several years rather than at the point of purchase.

Two cautions on those figures. They are UK list prices read on 7 August 2026 and this is an area where both pricing and product naming change quickly, so check before you rely on them. There are also two separately priced add-ons, one sold against Microsoft 365 Business plans ⁴ and one against the enterprise plans ⁵. What functionally distinguishes them was not established for this guide, and anyone comparing quotes should ask their partner to state it in writing.

Three boundaries that matter in construction

Most published comparisons of this kind fail because they attack the product in general terms. The useful version identifies the specific places where a contractor's ordinary working week meets a documented limit, and there are three.

Shared mailboxes. Microsoft 365 Copilot is only supported on primary mailboxes hosted on Exchange Online, and is not available on a user's archive mailbox, group mailboxes, or shared and delegate mailboxes they have access to ². Consider how a construction business actually receives information. Tender enquiries arrive at a shared tenders address. Site instructions and subcontractor queries land in a project mailbox that four people watch. Invoices go to accounts. Those shared mailboxes are frequently where the commercially important correspondence lives, and they sit outside the licence's currently supported scope. Microsoft's documentation records what is supported today rather than what could ever be reached by other means ², so it is a question to put to a partner rather than a closed door.

File formats. The supported format list runs to office and text documents, covering DOCX, PDF, PPTX, XLSX, CSV and mail formats, and contains no computer aided design, building information modelling, Industry Foundation Classes (IFC) or programme file formats ¹⁰. A contractor's most valuable documents are frequently the ones not on that list. This is not a criticism of Microsoft, which never claimed to read a DWG, but it does dispose of the idea that a licence gives a business an assistant that understands its drawings.

The shape of the question. This one is subtle and it is the most consequential of the three. Where a business extends Copilot using Copilot Studio, Microsoft documents that metadata filtering at folder or knowledge source level is not supported, that an agent cannot answer queries about what files exist in a folder or provide a count of the files in it, and that queries referencing a file or document name cannot be answered ⁷. Those same agents are limited to 25 SharePoint site URLs under generative orchestration, accept only DOC, DOCX, PPT, PPTX and PDF as SharePoint knowledge sources, and return only the first 2,048 rows of a SharePoint list ⁷.

Read that list against the vocabulary of a document controller. How many drawings are outstanding at revision C. Which requests for information have no response. Count the variations issued since March. Find me the file called AO6-STR-DR-1042. Those are the questions asked all day in a construction office, and they are close to the exact set Microsoft states its agent tooling cannot answer. The limitation is honest rather than hidden, and it exists because the tool is built to retrieve and summarise passages of text rather than to query a register.

One boundary on that boundary, because the distinction matters and is easy to blur. Those quotas describe Copilot Studio agents, not Microsoft 365 Copilot itself ⁷. Conflating the two would misrepresent both products.

The oversharing question, put fairly

The most common warning about Copilot in construction is that it will surface documents people were never meant to see, usually stated as though the product has a security flaw. It does not, and repeating that framing makes the rest of an argument easy to dismiss.

Copilot only accesses data an individual user is authorised to access under existing Microsoft 365 role-based access controls, and it does not access data the user does not have permission to access ³. Operating inside the Microsoft 365 service boundary does not grant tenant-wide visibility, and access is always scoped to the signed-in user ³. The permissions model is enforced.

The real problem sits underneath, and Microsoft says so plainly: by default, SharePoint sets sharing settings to the most permissive option ⁶. A decade of project sites created at speed, with folders shared to everyone in the organisation because that was the fastest way to unblock a subcontractor on a Friday, produces a tenant where a great many people are technically authorised to open a great many things. Nobody noticed, because nobody was searching. Copilot does not breach those permissions. It exercises them.

Microsoft's own guidance is to fix this before deployment, and it documents tooling for the purpose, including Restricted Content Discovery, which prevents content appearing in Copilot experiences while leaving site permissions unchanged ⁶. Whether that tooling is included in the licences you already hold is a question for your partner: the documentation does not establish that SharePoint Advanced Management comes with a base licence ⁶. That is the honest sequence: the permission and structure work comes first, whichever option you eventually choose, and it is the part of the project that returns value regardless. It is also the part nobody budgets for, and it is the substance of our SharePoint and common data environment work.

The middle option most comparisons ignore

Presenting this as licence against bespoke build is a false choice, and any consultancy that presents it that way is selling rather than advising.

Declarative agents let a business customise Microsoft 365 Copilot by supplying instructions, actions and knowledge for a specific scenario, and they can use enterprise data from SharePoint, OneDrive, Copilot connectors and uploaded files ⁹. They run on the same orchestrator and models as Copilot and inherit its data protections ⁹. In practice this means a contractor can build something genuinely tailored, a tender response assistant that knows the firm's standard positions, or an assistant that answers questions about the health and safety library, without commissioning a system.

Microsoft also documents Copilot connectors as a route for a declarative agent to use data beyond SharePoint and OneDrive ⁹. Whether connectors exist for the systems a UK contractor actually runs, the Procores and Asites and COINSes of the world, was not established for this guide and no claim is made either way. It is the first question to put to a Microsoft partner, and the answer materially changes the comparison.

Try the middle option before commissioning anything. A declarative agent that disappoints will still teach a business more about what it actually needs than a requirements workshop will.

When a custom build is genuinely justified

A bespoke assistant is worth its cost in a narrow set of circumstances, and they are recognisable.

The first is when the valuable material is structured rather than prose. If the questions being asked are register questions, counts, filters, outstanding items, everything at a given revision, then a system that queries a database will answer them and a system that retrieves passages will not, which is precisely what the documented limits above describe ⁷. The second is when the source material sits in formats or systems Microsoft 365 does not reach, which for construction means drawings, models, programmes and the specialist packages that hold them.

The third is a workflow rather than a question. Copilot answers a person who asks. A system that reads every delivery ticket as it arrives, extracts the fields, checks them against the order and raises the exceptions is doing something a licence does not do, because nobody is sitting there asking.

Where none of those three apply, a custom build is usually a more expensive route to what the licence already does, and the honest recommendation is to spend the money on adoption instead. That is a different problem with a different fix, and it is the subject of a separate piece on why Copilot licences sit unused.

Where this comparison stops working

Three limits belong on this page.

The first is time. Everything above was read on 7 August 2026, and this is a fast-moving product area: pricing carries a promotion that ends on 30 September 2026 ⁴, the documentation has recently renamed several components, and the Copilot Studio quotas page was updated three days before it was read ⁷. Treat every specific figure here as needing a check rather than as a standing fact.

The second is that neither option removes the need for human review. Microsoft states that in summarising content from various sources Copilot may include information in its response that is not present in its input sources, in other words that it may produce ungrounded results, and it describes overreliance as users accepting incorrect or incomplete outputs mainly because mistakes may be hard to detect ⁸. A custom build has the same exposure from the same cause: Microsoft's own documentation on retrieval-augmented generation, the technique most custom assistants use to ground answers in a business's own documents, states that if retrieval returns irrelevant or incomplete passages the model can still produce incomplete or inaccurate answers despite grounding, and that retrieved content should be treated as untrusted input ¹¹.

The third is that no measured comparison of the two options in a UK construction business exists, published by us or by anyone else. There is no study to cite and this guide does not pretend otherwise. What it offers is the documented capability of one option, the documented mechanism of the other, and the boundary between them, which is enough to make a decision but is not the same thing as evidence about outcomes.

What to do on Monday

Start by finding out which product you already have, because the answer is frequently Microsoft 365 Copilot Chat rather than the licensed product ¹, and a business comparing a bespoke build against a thing it has not actually bought is comparing nothing.

Then write down the 10 questions the business most wants answered. Read them against the three boundaries above. If most of them are prose questions about documents and correspondence inside Microsoft 365, buy the licence and spend the difference on adoption. If most of them are register questions, or the answers live in drawings and programmes, the licence will disappoint regardless of how well it is rolled out, and that is worth knowing before the renewal rather than a year after it.

Whichever way that lands, do the permission and structure work first. It is the only part of this that improves the business under either option, and it is the part that makes the second option cheaper if you get there.

Three related questions are worth reading before you decide. What may safely go into either option is covered in uploading construction documents to AI. Which of your processes are realistic candidates is in processes ranked by evidence. And the arithmetic for comparing the licence bill against a build sits in the return on investment guide. How we approach that comparison in practice is shown in our case studies.