A Variance Purchase Order Gets Keyed Four Times Before It Reaches Job Cost. MCP Ends Three of Those Keystrokes.

Four keystrokes for one $1,850 tile change

A buyer at lot 22 wants the master shower tiled to the ceiling instead of stopping at the standard height. Small change. Here is what actually happens to it. The super texts a photo and a note to the project manager. The project manager types a variance purchase order into Buildertrend against the tile budget line. The purchasing agent re-types it into the accounting system so the tile contractor's invoice has something to land against. The bookkeeper re-types it into QuickBooks, because your job-cost file and your general ledger have never been the same file. The sales counselor writes a change order addendum to the purchase agreement so the buyer gets billed the $1,850 at closing.

That is four re-keyings of one number that never changed. Each one takes five or six minutes and each one is a chance for the tile budget line to say something different from what the buyer signed. And the failure mode is not that somebody types 1,580 instead of 1,850. The failure mode is that step five never happens at all — the addendum never gets written, the closing coordinator never sees it, and you eat $1,850 of tile you installed for free.

Every builder in America has a version of this. The change is real, the work gets done, and the paperwork chain has four links in it, so it breaks at whichever link belongs to whoever was on a job site that afternoon.

Your system of record is one file. Everything else is a photocopy of it.

For most builders doing 25 to 300 homes a year, the system of record is Buildertrend or CoConstruct, or ECI MarkSystems or Constellation's NEWSTAR if you run production plans, sitting next to Sage 100 Contractor or QuickBooks for the money. Whichever it is, there is exactly one place where the truth about lot 22's tile budget lives, and there are three or four other places where a copy of that truth lives, staying accurate for as long as somebody keeps typing.

Until 2026 an AI assistant made this worse, not better. It lived in its own tab. You pasted things into it, it gave you a nicely worded paragraph back, and then you typed that paragraph into Buildertrend yourself. You had added a fifth place for the number to live.

The Model Context Protocol — MCP — is a common plug that lets an assistant read and write inside the software you already pay for, so the answer it gives you and the record in your job-cost file are the same thing rather than two versions of it. It stopped being a curiosity in 2026 because the big vendors built on it: Oracle shipped AI Agent Studio for its Fusion applications, Microsoft shipped Sales Agent and Service Agent that work inside the customer record instead of beside it, and Salesforce wired the same idea through Slack. That is the shape now spreading down into the software builders actually run.

Tuesday, 2:40 p.m., a photo of a header that is the wrong size

The super is standing in a garage looking at a 2x10 header over an opening the plans call out as a 2x12. He photographs it and sends it to the agent the same way he would send it to the PM. The agent reads the plan sheet, sees the call-out, and knows this is a framing fix and not a buyer selection. It drafts the variance purchase order against the framing labor cost code in Buildertrend, attaches the photo, pulls the framer's unit price from the awarded scope, and puts it in front of the PM on his phone as one line with an Approve button.

flowchart TD
  A["Super texts photo: header undersized at lot 22"] --> H["Agent drafts the variance PO in Buildertrend"]
  B["Framer's awarded unit price for the fix"] --> H
  C["Selection sheet: is this buyer-chosen or a defect?"] --> H
  H --> I{"Over $1,000 or billable to the buyer?"}
  I -->|Yes| J["PM approves on his phone"]
  I -->|No| K["Posts straight to the cost code"]
  J --> L["Writes job cost, sales addendum, waiver request to the framer"]
  K --> L

Because it can write into the system of record, the approval does four things at once instead of starting a relay. The variance PO posts to the framing cost code. If it is buyer-billable, a change order addendum drafts itself against the purchase agreement with the correct amount and the lot number, and lands in the sales counselor's queue to send. The accounting side gets the same amount against the same cost code without anybody re-typing it. And the lien waiver request for that additional amount goes on the framer's list so it does not go missing at draw time.

The double entry that disappears is not the first entry. It is the second, third and fourth. Somebody still decides. Nobody re-types.

The margin arithmetic on variance orders nobody billed back

Builders rarely lose money on the variances they price wrong. They lose it on the ones that never became a bill. Here is an illustration, with the assumptions on the table so you can substitute your own.

If your leakage rate is 5 percent instead of 12, the number is $13,800 and it is still larger than what the agent costs to run. And the 72 hours is the least interesting line in the table, because those hours are spread as six-minute interruptions across a purchasing agent and a bookkeeper who were in the middle of something else.

To measure it, do this: take twenty closed homes, pull every variance purchase order posted to job cost, and match each one against the signed addenda in the buyer file. The gap is your leakage rate. Most builders who run this exercise for the first time do not enjoy the afternoon.

What you must not let it write

Do not give it the purchase agreement. Drafting an addendum for a person to review is fine; sending a binding document to a buyer without a human reading it is not, and that is true no matter how good the drafting gets. The same goes for anything that hits the buyer's price, the closing statement, or a trade partner's contract.

Set a dollar threshold and hold to it. Under a few hundred dollars, on a defect fix with an awarded unit price, letting it post to the cost code is reasonable. Above that, a PM approves. And keep it out of retainage, backcharges and any dispute with a trade partner — the moment there is an argument about who broke the tub, you want a person who knows that framer's history handling it, not a tidy record of both positions.

One more honest limit: not every builder platform has a native connection yet. Buildertrend, MarkSystems and NEWSTAR are at different stages, and if yours has nothing, an agent can still drive the screens the way a person does, which works but is slower and more fragile. Ask your vendor a direct question — can an assistant read and write in my data on my behalf, and what does it log? — and take a vague answer as a no.

Frequently asked questions

Does this mean my project manager loses control of what gets approved?

The opposite, if you set it up right. Today a variance gets approved by text message and reconstructed later from memory. With the agent, every variance arrives in the same shape — cost code, amount, photo, buyer-billable or not — and the PM taps approve or sends it back. He is approving more consistently, not less.

We use QuickBooks, not Sage. Does that matter?

Not much for this. The important connection is to whichever system holds job cost by lot and cost code, because that is where the truth is. QuickBooks with the contractor edition and a decent cost-code list works fine. What matters more is that your cost codes are consistent across jobs, because an agent posting to a made-up code is worse than a bookkeeper who knows better.

What happens when a buyer changes their mind twice on the same selection?

You get two variance orders, which is what should happen — the first one is real work already ordered. The agent's advantage is that it will notice the tile order already went to the supplier and flag the restocking exposure rather than quietly writing a second order as if the first never existed. That flag is the thing your process misses today.

Is our buyer and job data safe going through this?

Ask about logging and spend controls, and expect real answers. The enterprise governance update in July 2026 added usage dashboards, spend limits at the company and person level, and alerts at 75 and 90 percent of budget, which is the kind of control an owner should insist on before this touches contracts and buyer names.

The Monday version of this

Pick one document: the variance purchase order. Not selections, not draws, not warranty. For two weeks, have the agent draft every variance in Buildertrend and stop there, with the PM approving each one by hand and the purchasing agent still re-typing into accounting as usual. Count how many drafts came back correct on the first read. When that number is above nine in ten, turn off the re-typing step and let the write go through. Then, and only then, look at the sales addendum.

The variance you never billed back has a cousin: the buyer who called the sales office at 6:15 p.m. to ask about that shower tile and got voicemail, then called the tile store instead. CallSphere builds AI voice and chat agents that answer the sales trailer line and the website chat after hours, capture which lot the caller is asking about, and book the follow-up with the counselor — so the conversation that starts a change order actually gets recorded somewhere the day it happens.