The Pricing Analyst Keys 4,000 Vendor Cost Changes Every January. Per-Seat AI Was Never Priced for That Job.

Ninety-one people on the payroll. Eleven of them ever sit in front of a keyboard for more than ten minutes at a stretch. That is the shape of a three-branch building materials dealer, and it is why every per-seat AI quote you have been handed feels wrong before you reach the number.

Count your own org chart. CDL and boom-truck drivers, yard hands, forklift operators, a yard foreman per location, one dispatcher, six inside sales reps on the counter and the phones, four outside sales reps living in their trucks, a purchasing agent, a pricing analyst, a credit manager, two AR clerks, a millwork and window specialist, three branch managers and a GM. The work a computer could genuinely take off your hands is not spread across those ninety-one people. It is piled on four or five desks, and it arrives as paper.

Eleven keyboards, four thousand cost changes

The heaviest pile is the vendor cost file. Between the first week of January and the end of February, a mid-size dealer absorbs north of four thousand item-level cost changes: the fiber cement announcement, the connector update, the shingle letter, a coordinated move from the gypsum producers, plus the mills repricing dimensional lumber every week because that is what mills do.

An open-weight model is one whose complete workings are published for anyone to download, which means a distributor can run it on a machine it owns and pay for a server and electricity instead of a monthly fee for every named user. That distinction did not matter much in 2024, when the downloadable models were visibly a step behind. It matters now, and it matters most for exactly this kind of job: enormous volume, boring work, and data you would rather not hand to anybody.

Per-seat pricing assumes an office of knowledge workers each having a conversation. Your problem is not conversational. It is four thousand rows that must be right by an effective date, and one pricing analyst.

What the price letter actually looks like when it lands

It lands three ways. Your territory rep emails a PDF on manufacturer letterhead with the effective date buried in the second paragraph. The vendor portal posts a cost sheet you have to log in and pull. And somebody sends a spreadsheet of nine hundred vendor part numbers that match none of your item numbers.

Then the sentence that eats a week: eight percent on all connectors except ZMAX and stainless, which go eleven. Somebody has to decide which of your nineteen hundred connector items are ZMAX, notice that the letter covers the hanger but not the strap, and catch that the effective date runs by ship date rather than order date — so the quote out on the Ridgeline job is fine and the one on Chestnut Street is not.

The workaround everybody in this trade pretends is fine: update the top three hundred movers before the effective date and let the tail ride. The tail is where it bleeds. You sell a case of structural screws in March at a cost you paid in October, and nobody catches it because that item moves eleven times a year. Worse, a ship-and-debit claim gets kicked back because you claimed against a cost that had already changed.

What actually changed in the open tier this year

For two years the honest answer to "can I just run one myself" was no. In 2026 that changed. Moonshot AI released Kimi K3, the largest open model in the world, built so only the slice it needs wakes up for any single question — which is why something that large can run on hardware a distributor can actually buy and rack. The rest of the downloadable tier moved up with it, and reading a manufacturer letter against your item file is careful, repetitive matching work. The open tier cleared that bar this year.

Two honest counterweights before you buy a server. Hosted models got roughly ten times cheaper than in 2025, so running your own is a choice about control, not a rescue from a bill. And the reason most dealers land on hosting is not price at all — it is that your landed cost file, your customer price matrix and your contract pricing are the three things you would least like to see leave the building.

flowchart TD
  A["Territory rep emails a price letter"] --> D["Model on the back-office server reads all three sources"]
  B["Vendor portal posts a new cost sheet"] --> D
  C["Mill sends a weekly repricing sheet"] --> D
  D --> E["Draft cost changes, item by item, with effective dates"]
  E --> F{"Pricing analyst reviews only the exceptions"}
  F -->|"Clean"| G["Load into the BisTrack cost file"]
  F -->|"Flagged"| H["Analyst calls the vendor rep to confirm"]
  H --> G

The Tuesday in January when this stops being theory

7:40 a.m. Twenty-two emails overnight, six of them price letters. The machine in the back office has already read all six, pulled the two portal sheets, and produced a draft change file: 1,410 items, each with old cost, new cost, effective date, and one line of plain English saying which paragraph of which letter it came from.

The analyst does not read 1,410 rows. She reads the 63 the model flagged: nine where the letter's category wording could mean two different things in your item file, twelve where the vendor part number has no match, eighteen where the increase is bigger than anything that vendor has done in five years, and twenty-four where you have open quotes at the old cost that expire after the effective date. That last group is the money. By 10:15 the reps who own those quotes have either re-quoted or confirmed an honor-until date with the builder.

Then it loads. Same day, not the third week of February — and the C movers get updated alongside the A movers, because including them costs nothing.

What running your own actually costs — in people, not dollars

The hardware is the easy part. The real cost is that somebody has to own the thing. Here is a worked comparison for a three-branch dealer. Every figure below is an illustration, not a quote — use your own vendor's per-seat number and your own IT arrangement.

On seats alone, hosting loses. It wins only when you count the volume you would never put through a metered seat: 4,000 cost changes, 3,100 emailed material lists a year, every proof-of-delivery ticket the drivers bring back, every lien waiver and preliminary notice, every ship-and-debit claim. Add the pricing analyst getting eleven days of January back and half a point of margin leakage recovered on the tail items, and the arithmetic flips. If you cannot name that number for your own yard, do not buy the server yet.

The parts of this you should not hand to a box in the back office

Not the final load into the cost file. A model that mis-reads one category line and pushes it live at 6 a.m. has your counter quoting nineteen hundred connectors wrong before the coffee is made. Keep the analyst's approval as a hard gate, and keep a one-click rollback.

Not contract pricing on your top twenty builder accounts — those numbers were negotiated across a table and often include handshake terms that live nowhere in the system. Not rebate and ship-and-debit interpretation where the money is large: the model can assemble the claim and flag the mismatch, but the credit manager decides whether to file it, because a rejected claim costs relationship capital with the vendor.

And not anything on a day when the person who maintains the server is unreachable. That sounds trivial. It is the single most common reason self-hosted projects quietly die in this industry.

Frequently asked questions

We already pay for Microsoft 365 across the company. Isn't this included?

The assistant that reads your email is bundled in some plans. Reading nine hundred rows of vendor part numbers, matching them to your item file and handing your analyst a change file is not the same job — and on a per-seat plan you are billed for people who will never open it. Price it against the number of documents, not the number of badges.

Who fixes it when it breaks the Friday before a price change?

Whoever already fixes your ERP server. If the answer is "the GM's nephew," you are not ready to host. A managed IT provider on a monthly retainer is the normal answer at this size — get the response time in writing before you buy hardware.

Is my landed cost file safe if we use a hosted model instead?

The major vendors offer business terms that keep your data out of their training, and the 2026 governance updates added spend limits and usage dashboards so you can see what is being sent. Plenty of dealers are comfortable with that. If your ownership is not, hosting your own is now a genuine option rather than a downgrade — that is the actual news this year.

Do we need to run the biggest open model?

No. Matching vendor letters to an item file is well within a mid-size open model on one server. The largest ones matter for harder reading — a hundred-page submittal package or a full architectural set — and you can send those few jobs out and keep the daily grind in-house.

Start with one vendor and one January

Pick the vendor whose letters cause the most arguments. Give the model last January's letter and last January's actual change file and see how close it gets, before you spend a dollar on hardware. If it lands within a few percent on item matching, run it alongside your analyst for one cycle. Two-week test, not a project.

One last note on where the phone fits. Every price change generates calls: contractors asking whether a held quote is still good, builders asking the new number on a load shipping Thursday, and the ones placing an order before the increase hits. CallSphere builds AI voice and chat agents that answer the counter line and the website chat around the clock, take the caller's job name and PO, and book the callback so an inside sales rep is not choosing between a walk-in and a ringing phone. It does not touch your cost file — that is the analyst's job, and it should stay that way.