Contractor software gets compared on the monthly subscription, because that is the number vendors publish. It is also the least important number. The costs that decide whether a system is worth it show up later, and they are rarely on the price page.
Start with implementation. Across the field-service category, getting a system live typically costs 20 to 50 percent of the annual subscription, paid upfront, and the biggest wave of churn happens in the first 6 to 12 months, largely because migrating and cleaning the old data is painful. For the larger construction ERPs, a full migration is a 6-to-12-month, six-figure project. That is the real switching cost, and it is why contractors stay on systems they complain about.
Then there is the cost of getting your own data out. One mid-market ERP that contractors respect gates its API behind a paid developer license reported at around $2,500 a year — a number that does not appear on any public pricing page and cannot be self-served. There are free, sanctioned workarounds (scheduled report delivery, middleware on someone else’s license), but a buyer comparing “has an API” across vendors would never know one of those APIs carries a separate annual toll.
The largest hidden cost is the one with no line item at all: integration maintenance. The connection between the field system and the accounting system is the single most fragile part of a contractor’s stack. It breaks on both sides’ updates, and keeping it working is ongoing labor. When contractors migrate off legacy systems, the reason they give is usually “better software,” but the deeper driver is that the legacy APIs make that integration even more expensive to maintain.
None of this is an argument against buying good software. It is an argument for costing it honestly: subscription plus implementation plus data-access plus the standing cost of keeping the integrations alive. On that basis, the cheapest sticker is frequently the most expensive system, and a well-integrated stack is worth paying for.
Drawn from our hands-on work getting data out of contractor systems and from operator interviews. Product observations are our own experience, framed analytically. See the full software index.