Per-seat pricing in construction software: the math

The price on the demo looked fine. Then you did the headcount: twelve people in the field, two in the office, and a tool priced per user. Suddenly the reasonable monthly number is a four-figure invoice, and you are deciding which of your foremen does not get a login. That decision is where field software quietly dies, and it traces straight back to one choice the vendor made: per-seat pricing.

We build SubTrade inside Quality Gypsum Services, a commercial drywall contractor in Calgary, Alberta, so we have run this math against our own crew more than once. Per-seat pricing is not a scam, it suits plenty of businesses. It just happens to be the worst possible model for a trade subcontractor, for a reason that has nothing to do with the software's quality. Here is the math, and what to look at instead.

What per-seat pricing is

Per-seat, or per-user, pricing charges you a monthly fee for every person who can log in. Ten dollars a seat, fifty dollars a seat, whatever the number, the invoice scales with headcount. The model came from office software, where everyone who touches the tool is a knowledge worker at a desk doing roughly the same kind of work, and one seat equals one full user getting full value.

That assumption is reasonable in an office. It falls apart the moment most of your users are in the field.

Why the math punishes subcontractors

A subcontractor's headcount is shaped nothing like an office. The field is the company. Most trade businesses carry a large crew and a small back office, which means most of your potential software users are foremen and tradespeople who need the tool for a handful of simple actions, not account managers living in it all day.

Per-seat pricing charges the same for both. A foreman who opens the app three times a day to clock his crew, log the day, and take a few photos costs you exactly as much as the estimator who runs the whole business through it. You are paying full desk-worker rates for people doing two minutes of work.

The result is predictable. Nobody buys enough licenses. The office decides only supervisors get seats, or only one person per job, and half the crew stays on paper. Now your expensive new system has a hole in it exactly where the data comes from, and the job costing it promised never arrives because the hours never made it in. Construction is one of the most field-weighted industries there is, as Statistics Canada's construction employment data makes plain, and a pricing model that taxes field users is a pricing model fighting your own structure.

A worked example

Picture a shop with two office staff and twelve field crew. Here is how the same tool lands under two models.

The middle row is the one that actually happens. To keep the invoice down, the company starves the field of licenses, and the whole value proposition, labour data flowing from the field into live job costing, collapses. The tool is not the problem. The pricing model forced the hole.

The hidden cost is not on the invoice

The real damage from per-seat pricing is not the monthly number, it is what the number makes you do. Every time you win a crew and want them in the system, there is a cost attached to adding them, so you hesitate. Software you hesitate to roll out fully is software you never get full value from.

Field tools only work when the whole field is on them. One foreman still doing paper timesheets breaks the costing for his entire job, because now you are reconciling two systems and trusting the gaps. Adoption is all-or-nothing in a way office software never is, and per-seat pricing puts a toll booth on the exact thing you most need to be universal: crew time tracking that every foreman actually uses.

What to look at instead

You are not looking for the lowest sticker price. You are looking for a model that lets you put your entire field on the tool without flinching, because that is the only way the data works.

Flat or company-based pricing. A single predictable price that covers your whole team means you never have to ration logins. Everyone is on it, the data is complete, and the invoice does not grow every time you hire.

Clarity on who counts as a user. If a vendor does charge per seat, ask directly whether read-only or field-only users are free or discounted. Some are. The answer changes the math completely.

What happens as you grow. Run the price at your busy-season headcount, not your winter one. A number that works with eight crew and breaks at twenty is a number that will punish you for growing.

When you compare tools, put the pricing model next to the feature list, not after it. We lay our own model out plainly on the pricing plans page, and our head-to-head breakdowns against the platforms subs most often weigh, including SubTrade vs Procore, SubTrade vs Knowify, and SubTrade vs eSUB, each put pricing structure on the table alongside what the tool does. SubTrade is a flat $299/month CAD with a 14-day free trial and no credit card required, specifically so you can put every foreman on it without doing seat arithmetic first.

The test before you sign

Before you commit to anything, run one calculation. Take your headcount at your busiest point in the year, office and field, and price the tool as if every one of those people had a login. If that number makes you want to cut field users, you have found a model that will quietly undermine the rollout. A tool is only worth what your whole crew will actually use, and the pricing has to let them.

FAQ

What is per-seat pricing in construction software?

A model that charges a recurring fee for every person who can log in. The total scales with headcount, so a business with many users pays more regardless of how lightly most of them use the tool. It originated in office software, where nearly every user is a full-time desk worker.

Why is per-seat pricing bad for subcontractors?

Because a subcontractor's headcount is mostly field crew who need the tool for a few simple actions, yet per-seat pricing charges the same for them as for heavy office users. To keep the invoice down, shops ration licenses, the field stays partly on paper, and the labour data that justified the purchase never fully arrives.

What pricing model is better for a trade business?

Flat or company-based pricing that covers the whole team for one predictable fee. It lets you put every foreman and crew member on the tool without adding cost each time, which is the only way field data comes in complete enough to drive job costing.

How do I compare construction software prices fairly?

Price each tool at your busy-season headcount with every office and field user logged in, not a trimmed-down count. Ask whether field-only or read-only users are discounted, and check how the price behaves as you grow. Compare the pricing model alongside the features, not as an afterthought.

Does cheaper per-seat pricing solve the problem?

Not really. Even a low per-seat rate still attaches a cost to every added field user, which keeps the incentive to ration logins. The issue is the structure, not only the number. A model that gets more expensive the more of your crew you include works against the universal field adoption these tools depend on.

How much should subcontractor field software cost?

Expect a monthly subscription rather than per-project fees, and favour a flat price you can extend to the whole crew. SubTrade is $299/month CAD flat. The right question is not the sticker price but whether the model lets you put every field user on the tool without hesitation.