Inspection software quotes are hard to compare because vendors price against different units: users, sites, assets, modules, or some combination. None of these models is wrong. Each one shifts cost and risk differently, and understanding the mechanics matters more than the sticker number.
The three common models
- Per-user pricing. You pay for each named user per month, usually billed annually, often in tiers that gate features. This model scales with your team, not your plant. It is the easiest to start with and the easiest to forecast, but costs grow as adoption grows, which can create a perverse incentive to under-license the field. Watch for how the vendor defines a user: a read-only planner and a full-time inspector should not cost the same.
- Per-site pricing. A flat annual fee per site or plant, sometimes banded by asset count. This decouples cost from headcount, which is healthy for adoption: everyone who should be in the system can be. The risk is paying for capacity you do not use at small sites, and the bands can jump sharply when an asset count crosses a threshold.
- Facility or enterprise licensing. A negotiated agreement covering a facility or fleet, typically including implementation, migration, and support commitments. This is where large operators usually land, because it converts a per-seat variable cost into a budgetable line item and bundles the services that actually determine success.
What actually drives the price
The license is rarely the whole cost. When comparing quotes, force every vendor to itemize:
- Implementation and configuration. Equipment hierarchy setup, CML definitions, workflow configuration. Fixed bid or time and materials, and who does the work.
- Data migration. Often quoted separately, and often the largest single services number. A suspiciously low migration line means the scope was not understood.
- Training. Included sessions, formats, and whether refresher training after go-live costs extra.
- Integrations. Connections to your CMMS or historian. Ask whether the connector is productized or a custom services project.
- Support tiers. Response times, named contacts, and whether field-season support differs from office-hours support.
Two quotes with the same license number can differ by a factor of two once these lines are real.
Questions that expose the model's edges
- What happens at renewal? Ask for the escalation cap in writing.
- What happens if we shrink? Can unused seats be dropped at renewal, or is the count locked?
- Are modules gated? If risk-based inspection or turnaround planning costs extra, get that number now, not in year two.
- Is offline field capture included, or a mobile add-on?
- What does the trial convert to? A trial that requires a services engagement to become useful is a demo, not a trial.
Where intelliSPEC sits
For transparency: intelliSPEC publishes per-user plans from $19 to $89 per user per month, billed annually, with a 30-day trial, and offers facility licensing through sales for site-wide deployments. We publish the range because we think buyers compare better when at least one number on the spreadsheet is public.
How to run the comparison
Normalize every quote to a three-year total cost for a realistic user count and site scope, including services, integrations, and a defensible renewal escalation. Then weight it against the evaluation criteria that matter more than price: migration quality, field adoption, and audit readiness. The cheapest system that the field refuses to use is the most expensive option on the table.
Pricing models are just risk allocation. Pick the one whose risks you would rather own, and get the edges in writing.
