Bid Season Puts 14 Estimators on Per-Seat AI and 90 Foremen on It for Six Minutes a Week. Kimi K3 Changes That Math.

Thirty-four seats in February, ninety-six in July

Pull last year's invoices for whatever AI tool your office standardized on and put the seat count next to the month. On a commercial GC of about $85 million a year, it looks roughly like this: 34 seats in January and February, 62 through the spring bid run, 96 from June through September when the summer school work and the second shift are going, and back to 58 by Thanksgiving. At $40 a seat that is 812 seat-months, or $32,480 a year, for a tool nobody in your company thinks about.

Now look at who those seats are. Six estimators and the preconstruction manager live in it four hours a day from February through May. Nine project managers use it maybe an hour a day. And then there are sixty-odd foremen and field engineers who open it for six minutes to clean up a Raken daily report, plus the warranty coordinator, the AP clerk keying sub invoices in Sage 300 CRE, and the safety director building toolbox talks. Per-seat pricing charges the same for the foreman with six minutes as for the chief estimator in the middle of a $40 million hard bid.

That mismatch is old news. What is new is that as of 2026 you have a genuine alternative, and it is worth knowing exactly where the line falls before a vendor draws it for you.

The shape of a contractor's usage is nothing like a software company's

Seat pricing was designed for offices where everybody sits at a desk all year and uses the same tool at roughly the same rate. A general contractor is the opposite in three specific ways.

Headcount swings with the season. In most of the country you staff up between April and October, and public school work compresses the whole calendar into the ten weeks between Memorial Day and Labor Day. You are paying for peak seats during the months when your field people have the least time to sit down and type.

Second, the heavy work is lumpy and it is not per-person at all. During bid season your estimating department will chew through fifty to seventy project manuals, each 1,500 to 2,000 pages, hunting for allowances, alternates, unit prices, liquidated damages language, the wage determination, and the scope splits between Division 03 and Division 05. That is volume work that wants to run overnight, not a person clicking.

Third, the biggest population of people who could use it is not on your payroll at all. You have four hundred subcontractor and supplier users touching your Procore account. You will never buy them seats.

An open-weight model is one whose maker publishes the model itself, so you can run it on hardware you rent or own and pay for the machine rather than paying by the person, by the month.

What changed: Kimi K3 and the end of "open means worse"

Through 2024 and 2025 the honest advice was that the free-to-run models were a step behind and you would feel it on hard reading. That gap closed a lot this year. Moonshot AI released Kimi K3, a 2.8-trillion-scale sparse mixture-of-experts model — the largest open model in the world, and built so that only the slice of it relevant to your question does the work, which is why it does not require a data center to answer. The rest of the open tier moved up behind it.

The practical translation for a contractor: reading a project manual and producing a scope sheet is now firmly inside what a model you host yourself can do well. So the question in front of you is no longer capability. It is buy-per-seat versus run-your-own, and that is a spreadsheet question with a real answer.

flowchart TD
  A["Invitation to bid arrives, 1,800-page project manual"] --> B["Manual loaded on the in-house machine at 6pm"]
  B --> C["Pass 1: allowances, alternates, unit prices"]
  B --> D["Pass 2: wage determination and LD clause"]
  B --> E["Pass 3: scope sheet for each bid package"]
  C --> F["Draft bid tab in the estimator's own format by 6am"]
  D --> F
  E --> F
  F --> G["Chief estimator edits it and sends the invitations"]

The overnight run per-seat pricing was never built for

Here is the job that makes the case. Wednesday, 6 p.m., three invitations to bid land from the same public owner with a June letting. Each one is a project manual, a drawing set, and an addenda folder. The estimating department has eleven working days and four other bids in front of it.

The machine reads all three overnight. By 6 a.m. Thursday the chief estimator has, for each bid: every allowance and alternate with its page reference, the unit price schedule, the liquidated damages number and the milestone it attaches to, the Davis-Bacon wage determination and effective date, the bond and insurance requirements, the DBE participation goal, the substantial completion date, and a first-pass scope sheet for each bid package flagging the two or three items that always fall between trades — fire caulking, wall backing, roof blocking, temporary power.

None of that is a decision. Every line of it is a lookup, and every one of those lookups is currently done by a $78-an-hour estimator with a highlighter at 9 p.m. That work has no natural seat count, which is exactly why paying by the seat prices it wrong.

What running your own actually costs, in people

This is where most articles stop being useful, so here is the honest version. You do not have an IT department. You have an IT manager who also fixes the plotter, and a managed services provider on a monthly retainer. Running your own model adds three obligations to that: somebody keeps the machine current, somebody decides who can see which job's documents, and somebody answers the phone at 7 a.m. during bid week when it will not respond.

Budget four hours a week of your IT manager and an add-on to the MSP retainer. If your answer to "who owns this" is "we will figure it out," buy seats and stop reading. A tool that is down during the second week of April costs more than it saves.

The arithmetic, including the part where it does not pay

Assumptions: 812 seat-months a year at $40, as above. Rented machine time for the overnight reading at $1,150 a month. MSP add-on $750 a month. IT manager at $56 an hour burdened, four hours a week. Twenty-eight people genuinely use it daily and keep commercial seats.

On seats alone, running your own loses. Say that out loud, because a lot of people will tell you otherwise. It only turns when you count the overnight reading, which per-seat pricing was never going to give you: 60 bids a season, six hours of estimator time each on lookups the machine can do, at $78 an hour burdened, is $28,080 of estimating capacity handed back. Against the $15,408 gap you are ahead by about $12,672 — and, more to the point, your chief estimator gets to bid four or five more jobs in a season without you hiring a second estimator at $118,000 burdened.

The lesson is not "self-host everything." It is: pay per seat for people, and run your own for volume. If you have no volume work, per-seat is the right answer and always was.

What the open model will not do, and who still has to

It will not decide scope. The two or three items that fall between trades are exactly the ones that get argued about at the bid table, and the reason they get argued about is that the documents genuinely do not say. Your chief estimator earns his money on that judgment, not on finding page 1,411.

It will not read a drawing the way a takeoff person does. On-Screen Takeoff and your quantity work are a separate discipline. What is being described here is the written word — the manual, the addenda, the front-end documents.

And it does not know your history with a subcontractor, which is half of preconstruction. The machine can tell you the DBE goal is 12 percent. It cannot tell you which of the three qualifying subs will actually staff the job in August.

Frequently asked questions

Do I have to buy servers to run an open model?

No, and most contractors should not. You can rent the machine by the month or by the hour from a hosting company, which is what the numbers above assume. Buying hardware only makes sense if you also have documents that are not allowed to leave your building.

Is this something my Procore or Sage vendor will just add?

Some of it, eventually, and priced per seat. That is fine for the daily users. The overnight reading of fifty project manuals is not on anybody's roadmap as a seat feature, because it is not a seat-shaped job.

How do I stop this becoming a project nobody owns?

Give it to one person with a name and a deadline, run it against one bid week, and compare the scope sheets against what your estimator produced by hand. If it does not hold up on three real bids, kill it. That is a four-week test, not a program.

What about the seats I am paying for in December?

Start there. Before any of this, audit the seat list against actual use for the last ninety days. Most GCs find fifteen to twenty seats belonging to people who used it twice. That audit is free and it usually pays for the experiment.

A closing note on a related cost most contractors never put on this spreadsheet: during bid season, the office line rings all day with subs asking whether an addendum dropped, whether you are bidding a job, and whether they are on the invite list — and every one of those calls lands on the person you least want interrupted. CallSphere builds AI voice and chat agents that answer the phone and website chat, take the caller's details, book meetings and pass along the lead around the clock, so the estimating room gets its afternoons back. It answers calls; it does not price your bid.