From Copilot to Coworker: How Agentic ERP Is Changing Construction Project Management

"AI coworker" is a lovely phrase, and it's vague enough to mean almost anything. That's fine on a vendor's banner. It's less fine when you're about to give one access to your project accounts.

So let's get specific about what an AI coworker in construction can do in Dynamics 365 today, and where you'd be kicking the tyres on something that isn't built yet.

Figure 1: One way a variation could move from site instruction to contract

What the word covers

Copilot answers when you ask it something. An agent gets handed a job, works through the steps and comes back with a result for someone to check. "Coworker" is the friendlier name for the second kind. Microsoft mostly says "agent" on its ERP pages and keeps the other word for Copilot Cowork. Microsoft's September 23 post says the Dynamics 365 ERP plugin for Copilot Cowork is generally available, as is the ERP MCP server that lets agents read and act on ERP data.

The plumbing is there, then, for agentic ERP in construction, on paper anyway. What you can usefully push through it is another matter.

What has actually shipped

This is how the usual jobs stack up against Microsoft's own pages, read on October 19, 2026.

JobWhat Microsoft documentsStage Microsoft statesMatching supplier invoices to purchase ordersBetter purchase order matching in the Business Central 29 Payables AgentGenerally availableTime and expense entryProject Operations agent-led time, expense and approvals, announced August 2025Notice said general availability on September 30, 2025Tracking variations (change orders)Change order management for project billing schedulesComing to public preview, no dateDaily site reportsNo packaged Dynamics 365 agent found on the pages we readNot enough information to verifyAn agent reading and acting on ERP dataERP MCP server and the Copilot Cowork pluginGenerally available

Funny thing about that table. The rows with a firm stage are all finance jobs. The ones people actually picture when they hear "site coworker", the daily report and the chase for variations, are either a roadmap line or blank. Blank doesn't mean impossible, and a partner could build something that drafts a daily summary from what crews already submit. But that's a project with a budget, not a setting.

Business Central users should know one more thing. We combed the 29 update notes for anything on jobs or job costing and found none. The agents in that release deal with payables, expenses and sales orders. If project accounting is the sore spot, find that out before a headline plans your year.

The variation problem

Say "variation" to a contractor in Australia or New Zealand and watch the face. (Searches for change order tracking use the American term, but the headache is the same.) Someone gives an instruction by email or on a site walk. The work starts. The paperwork surfaces weeks later, if it surfaces, and then somebody wants to know what was agreed.

An agent could help here, because the first job is reading and sorting, not deciding. It could take the email, draft the entry, suggest cost codes and pin the original message to it. Get it wrong and the cost is a few seconds of a person's time, provided that person reads the draft before anything moves. That's our opinion rather than a finding, and it's why we'd start with this one.

The approval stays human. Approving a variation changes the contract value and what you can bill. Nobody should delegate that to software they've known for a month.

Before anyone gets a login

Forget the model for a minute and look at the account. An agent can do whatever its login can do. Loose roles, loose agent. Microsoft's roadmap mentions agent-specific access limits for finance and operations, and we couldn't find a date for Business Central.

Then there's the awkward bit. Say it gets one wrong and the entry posts. How do you undo it? The Microsoft pages we read don't say, so the checking has to happen first.

Somebody also has to review the output, and they need time to do it. An approval step nobody has time for becomes a rubber stamp within a month. Work out the reviewer's minutes before you total the agent's savings.

And data. An agent matching invoices to purchase orders is only as good as the orders, so inconsistent job and cost codes will just be processed faster.

How we'd start

Boring, probably. Pull last month's supplier invoices from your three busiest jobs, let the agent propose matches in a sandbox, and set the results beside what accounts payable did by hand. Wherever the two disagree you'll learn whether the agent or the purchase orders were at fault. Variations come second, each one approved by a person.

How Netsmartz can help

We're a Microsoft Solutions Partner with more than 26 years of experience, and AI agents and agentic workflows are part of what we build alongside Dynamics 365. For construction businesses the useful first step is usually a short review of security roles, data quality and which process to try first, then a sandbox pilot. If that sounds like the right size of step, talk to a Netsmartz Dynamics 365 specialist. You can also read our earlier post on AI agents in Business Central, our Business Central services and the ProjectPro construction solution.

Frequently Asked Questions