01
Verify the economic object
Identify the application, contract, accounting account, legal vendor, internal owner, and purpose. Do not start from a merchant match alone.
Software economics
A software audit starts after the merchant match
Contractor software costs are a contract and workflow question. An invoice cannot tell you whether a system is used, which plan unit drives price, whether a user is billable, or whether a downgrade will break a field or finance workflow.
A software cost control is not a cancellation list. It is an evidence-labeled software renewal register with owner, commercial unit, term, workflow dependency, available action, and later proof.
Level field observation
A cadence-only software audit overstated the review pool by 54.2 times
79.6%
of 206 apparent recurring-cost findings did not survive account, structural-spend, and person/vendor controls. Only 42 remained software-subject review candidates.
98.2%
of the apparent annualized dollars did not survive those controls. The raw detector produced $10.68 million, while the controlled review population was $197,066. Neither number is savings.
One read-only detector-control run, published as a Level field observation rather than a market benchmark. Payroll, tax, benefits, pass-through cash, people, inventory, insurance, and transfers can all look recurring. Read the complete study and method →
The five controls
02
Map the commercial unit
Record whether the bill is per user, crew, location, job, transaction, module, payroll subject, usage tier, or fixed minimum. A per-seat comparison can compare unlike products.
03
Make renewal explicit
Capture purchased quantity, active quantity, commitment date, cancellation notice, downgrade rule, credits, and the named decision owner.
04
Price the operating tail
Include implementation, migration, integration work, training, internal administration, parallel systems, payment economics, reporting repair, and exit effort.
05
Verify after the change
A canceled seat or downgraded plan becomes a result only when a later statement or credit proves the charge changed without breaking the workflow.
The renewal register
Five fields prevent most bad software decisions
| Field | Question it answers | Failure it prevents |
|---|---|---|
| Product and legal vendor | What is actually purchased and who contracts for it? | Merchant-text false positives and duplicate vendor rows |
| Commercial unit | Is it users, technicians, jobs, locations, modules, payroll people, or a fixed tier? | A fake apples-to-apples price comparison |
| Workflow owner | Which team uses it, and what fails if it is removed? | Finance cuts something the field or billing team still needs |
| Term and exit | When does it renew, how much notice is required, and how can data be exported? | A cancellation deadline missed because nobody owned it |
| Invoice evidence | What later statement or credit proves the change? | A claimed saving that never reaches the bill |
Attach the signed proposal, the current statement, owner confirmation, and relevant usage evidence. The register should show uncertainty instead of filling gaps with a guessed rate. For example, if an implementation fee is not stated in the signed proposal, label it unknown. Unknown is more useful than a false total cost of ownership.
A useful public benchmark
Not every contractor platform discloses the same price.
Our current public-source catalog finds 5 field-service vendors with a numeric public price and 5 that require a quote, out of 10 field-service records. That is an observation about disclosure, not total cost or product quality. The commercial unit can still be a plan, user, technician, job volume, module, or custom scope.
Read the source-linked pricing database →The contrarian view
Annual pricing can lower the monthly bill and increase total cost when headcount, feature needs, job volume, or a parallel system changes. Compare the commitment with the value of flexibility, not only with a month-to-month list price.
The 90-day renewal process
Decide before the vendor's deadline decides for you
- Days 90 to 60: inventory every contract, auto-renewal, owner, commercial unit, and data dependency. Request current order forms and usage exports.
- Days 60 to 45: ask the field, dispatch, finance, and sales owners which workflows are essential, duplicated, planned for retirement, or missing.
- Days 45 to 30: normalize competing proposals into first-year, steady-state, renewal, and exit columns. Put every unknown in its own field.
- Days 30 to 0: issue the decision, preserve notice proof, assign migration work if needed, and record the expected future invoice effect.
- Next statement: reconcile the bill, any credit, active users, modules, and operational outcome. Reopen the item if the charge or workflow differs.
Questions owners ask
Is a recurring charge automatically software spend?
No. Cadence and merchant names collide with payroll, insurance, financing, reimbursements, inventory, and other activity. Verify account, counterparty, contract, owner, and purpose.
Does removing a user reduce cost?
Not necessarily. User activity, account status, license assignment, purchased quantity, term commitment, and the later invoice can all differ.
How should a contractor compare quote-based software?
Normalize every proposal into first-year, steady-state, renewal, and exit economics. Separate implementation, migration, integrations, modules, support, transaction fees, and user rules.
For feature and product-fit research, see Level's contractor software comparison. This guide owns the renewal and cost-control decision, not a vendor feature ranking.
Grow without losing control of the numbers
Drop your info and we’ll show your real margin after callbacks and rework, which crews and jobs are worth the time, and how much cash is sitting in work you have already finished.
2,200+ service businesses benchmarked·$13.25B in revenue analyzed·Weekly action cadence
No commitment. Real numbers, not generic advice.