Commercial Contractor Software: 7 Buying Tests

Commercial contractor software is not one purchase. It is three, and you only choose one of them.

The pages ranking for this term will hand you a feature list: project management, job costing, invoicing, document management, scheduling, CRM. Deltek's explainer, which sits on page one, lists exactly those seven and stops. That list is true of every product in the category, which is another way of saying it will not help you pick one.

Here is the structure that actually decides your shortlist.

Two of those three are already partly decided by the work you take. The one everybody shops for hardest, the big all in one platform, is the third one.

What makes software "commercial" rather than residential?

Five documents, and nothing else. Not project size, not the word "commercial" on the pricing page, not whether the client is a business.

Residential software is built around a shape: estimate, deposit, progress, final invoice. Commercial work has a different shape, and it is a paperwork shape. Every draw cycle produces the same set, and each item in the set is a gate. Miss one and the money does not move.

1. The G702 and G703. G702 is the Application and Certificate for Payment, a one page cover sheet the contractor signs and the architect certifies. G703 is the continuation sheet, the line by line schedule of values carrying scheduled value, work completed this period, materials presently stored, percentage complete and retainage per line. The AIA sells G702 as a $59.99 one time use document. That price is the tell: this is not an exotic form, it is the default unit of commercial billing.

2. The lien waiver, in the right words. This is where generic invoicing software quietly fails. California Civil Code section 8132 states that a conditional waiver and release on progress payment "shall be null, void, and unenforceable unless it is in substantially the following form," and then prints the form. A waiver template your software generated because it looked like a waiver is not a waiver. Twelve states prescribe statutory forms, and the question to ask a vendor is not "do you do lien waivers" but "can I replace your template with my state's exact text."

3. Certified payroll, weekly. The Davis-Bacon Act applies to federal or federally assisted construction contracts in excess of $2,000. The Copeland Act requires a statement of the wages paid each employee for the prior week, submitted weekly, and the Department of Labor's Form WH-347 exists for that purpose. Its statement of compliance is signed subject to 18 U.S.C. 1001, carrying fines and imprisonment up to five years. A scanned or photocopied signature does not satisfy it.

4. Retainage, tracked per line and released on its own clock. On federal construction, FAR 32.103 caps retainage at 10 percent of the approved estimated amount, and it is meant to be a response to unsatisfactory progress rather than a default. On private commercial work it is simply whatever the subcontract says. Either way it is money you have earned sitting on someone else's balance sheet, and it has to be tracked per schedule of values line rather than per invoice.

5. The WIP schedule. Percentage of completion accounting, over and under billings, and the report your surety and your bank will ask for before they extend anything. This is the document that decides whether you can bond the next job.

Why does commercial software cost so much more than residential?

Because it is usually not priced per seat. It is priced against your construction volume, which means the software bill grows every time you have a good year.

This is the single largest practical difference between shopping for commercial and shopping for residential tools, and none of the listicles ranking for this term explain it. We covered the general version of this problem in why field service software costs so much, but the commercial market has its own mechanism.

Four different nouns carry the price, and which noun a vendor picked tells you who they built for.

Two honesty notes on that table, because vendor pricing pages are increasingly built to resist being read. Knowify's page shows both figures for each tier behind a yearly and monthly toggle, so $99 and $329 are the annual billing rates and $149 and $399 the month to month rates. Its Enterprise tier shows only "Talk to us." RedTeam's page is a JavaScript calculator, and the sentence quoted above is the fallback text rendered behind it: "Pricing starts at $10,000/yr for under $4M in active project value; contact sales for a detailed quote." The band boundaries are in the DOM; the rates inside each band are not.

Stack those side by side and the market splits cleanly. Under roughly $4 million in active project value, published per user and per project pricing exists and it is cheap. Above it, you enter the quote only tier, and the price stops being a subscription and starts being a percentage.

What is the ratchet in volume based pricing?

It only moves one way, and it is audited. This is the part nobody tells you in the demo.

The most detailed account I found this week is from a contractor in r/GeneralContractor running a small commercial GC. Their warning, which reads like it was earned: "They limit the number of projects they think you do based on total projected revenue. If you need 20 possible projects ask in advance before signing the contract."

Then the ratchet itself: "Estimate the project revenue you expect to put on Procore, they audit the system billings. Estimate within reason but on the low side. At your annual renewal if you exceeded they may bill you more. If you are under your estimates they offer no credit."

Read that twice. You forecast your own volume, the vendor checks your forecast against the billings you actually ran through their system, and the correction is asymmetric. A good year costs you at renewal. A bad year does not refund you.

A separate thread in r/Construction on escalating renewals puts one company at $1,000 per $1 million of annual contract value with tools being repackaged out of their tier each year. And a commenter in the small commercial GC thread adds the negotiation detail that actually saves money: "end-of-quarter timing is real. last two weeks of march, june, september, december." They also suggest pushing back on implementation fees and getting the price lock period in writing.

None of that is a reason to avoid the category. It is a reason to treat the contract as a contract rather than a subscription, which is how most contractors are used to buying software.

Do you even choose your software on commercial work?

Partly. On commercial jobs, the general contractor and the owner choose a meaningful share of your workflow for you, and no listicle accounts for this.

If the GC runs Procore, you are uploading pay apps into Procore. If the owner's program runs on Autodesk Construction Cloud or Aconex, you are in there for drawings and submittals. If the GC uses a payment network, your waivers are exchanged there. You are a guest in each of those, usually for free, and usually with no ability to get your own data out in a shape your accountant likes.

A subcontractor in r/Construction put the cost of this plainly: "As a sub, I wish everyone would just pick something. It's a pain having to figure out how to upload invoices to a bunch of different sites. None of them have change order options either. So invoices in my system never match whats on the construction software."

That last sentence is the real expense. Not the logins. The reconciliation. Your system says one number, four GC portals say four others, and somebody in your office spends a day a month making them agree.

Which changes what you should be buying. If a large share of your revenue arrives through other people's platforms, you are not shopping for a platform. You are shopping for a system of record that can feed those platforms without being retyped into them, and the integration question moves ahead of the feature question. That is closer to a custom CRM problem than a construction software problem, and it is worth separating in your head before you sit through six demos.

The 7 buying tests

Run a demo against these, in this order. They are ordered by how directly each one touches cash.

1. The pay app test. Can it produce a G702 and G703 against a locked schedule of values, with retainage held at different percentages on different lines, and carry stored materials separately from work in place? Ask to see it built, not shown as a sample.

2. The waiver test. Can you replace the vendor's lien waiver template with your state's statutory text, verbatim? If the answer is "ours is compliant," ask which states. California's statute voids anything not substantially in the prescribed form.

3. The payroll test. If you touch public work, does certified payroll come out of the same timecards your job costing uses, weekly, in WH-347 format with fringe handling? Double keyed certified payroll is how small shops end up with a compliance problem attached to a criminal statute.

4. The portal test. Count the platforms your top five customers make you use. Ask the vendor what each of those integrations actually moves. "We have an API" is not an answer to this question.

5. The pricing noun test. Ask what the price is attached to: seats, active projects, or volume. Then model the bill at 1.5x your current volume. If the answer changes your mind about the product, you found out cheaply.

6. The audit test. Ask directly: what happens at renewal if I exceed the volume I estimated, and what happens if I come in under. Ask for the rate steps between bands in writing. Ask for the price lock period in writing.

7. The WIP test. Can it produce a percentage of completion WIP schedule with over and under billings that your surety and your bank will accept without rework? If your bonding capacity depends on that report, it outranks every field feature on the list.

Tests 1, 2, 3 and 7 are the ones nobody demos unprompted, because they are the boring half of the product. They are also the half that decides whether you get paid and whether you can bond the next job.

When is Excel and Bluebeam still the right answer?

Longer than the vendors want you to believe, and experienced people say so in public.

A commenter in r/ConstructionManagers, responding to a GC doing $5 to $7 million in revenue looking to replace Buildertrend, wrote: "For $5-7M in revenue, you should be able to handle it via excel and bluebeam. Unless your average project size is $250K, in which case you should get Procore."

That qualifier is the whole point. The trigger is not revenue, it is concurrency. Five million dollars in two jobs is a spreadsheet. Five million dollars in twenty jobs is twenty open pay app cycles, twenty waiver exchanges, twenty retainage balances, and there is no version of one person holding that.

The gap in the middle is real and widely felt. Another commenter in the same thread: "there is a hole in the market for smaller GC's needing something that's not paper and Excel, but also not a full scale PM soup to nuts product like Procore and BT." That is exactly the segment Werx, Knowify and Contractor Foreman are priced into, and it is why their pricing is published while the tier above theirs is not.

If you are weighing whether the problem is a category problem or a workflow problem at all, construction management software or CRM works through that split, and subcontractor software for small builders breaks apart the sub side of it.

What does the billing layer actually save you?

Time you are currently spending, and cash you are currently financing. There is decent data on both.

Siteline's report The State of Subcontractor Billing in 2026, based on a May 2026 survey of 492 construction finance and operations professionals, found that 92 percent of subcontractors floated payroll from their own pockets in the past year while waiting to be paid, with 28 percent doing so most months. Forty-three percent said they wait more than 90 days to collect final payment and retainage, against 15 percent of general contractors, and nearly one in five waits six months or more.

The two findings that should change your shortlist are these. Respondents named pay applications submitted with errors or omissions as the biggest internal driver of their own late payments. And 67 percent spend 11 or more hours a month preparing, submitting and tracking pay applications.

Martin Press of Press Mechanical Contractors, quoted in the same report's coverage, framed the retainage half of it: "Retainage puts subcontractors in a difficult position. It keeps us from money we've already earned while we still have employees, suppliers, and vendors to pay." Siteline co-founder Claire Wilson put the systemic version more bluntly: "Subcontractors have become the construction industry's bank, and it's a role no one asked for."

Fifty-six percent of respondents also said they had missed a critical mechanic's lien deadline in the past two years. A missed deadline is not a paperwork error, it is the loss of the only leverage you have.

The checklist before you sign

Print this. Take it into the demo.

1. Build a live G703 with split retainage and stored materials. Not a sample. A new one.
2. Show the lien waiver template in edit mode and confirm the statutory text for your state can be pasted in.
3. Export a WIP schedule with over and under billings and send it to your CPA before you sign.
4. Name every GC portal your top five customers use and ask what the integration moves in each direction.
5. Ask what the price is attached to, then model it at 1.5x your volume.
6. Ask what happens at renewal on an overage and on an underage. Get both answers in writing.
7. Ask for the rate steps between volume bands and the price lock period in writing.
8. Ask for two customer references at your revenue, in your trade, in your state.
9. Ask who owns the data and how you get it out. Then ask for a sample export file.
10. Time the implementation in your calendar, not theirs, and confirm who inside your company owns it.

Item 10 is where most of these purchases actually die. A commenter in the small commercial GC thread put it well: the platform "amplifies whatever process gaps already exist." Software does not create a billing process. It scales the one you have, including the parts of it that are broken.

If you are still at the stage of deciding what to standardize before you shop, estimating software for contractors and how to get commercial contracts as a contractor cover the two ends this sits between: pricing the work, and winning the kind of work that comes with a G702 attached to it.