Back to Blog
Blog

Which numbers are needed to scope enterprise procedure pricing?

Which numbers are needed to scope enterprise procedure pricing?

The main numbers needed to scope enterprise procedure pricing are usually how many procedures need to be digitized, how long and complex they are, how…

The main numbers needed to scope enterprise procedure pricing are usually how many procedures need to be digitized, how long and complex they are, how many sites are involved and how many people will use the system, split between those who write and approve procedures and those who run them in the field. The number of integrations and the level of support needed also matter, since each of these drives a different part of the effort and cost.

Procedure count on its own can be misleading, because a library of five hundred single page checklists is a very different job from five hundred long operating procedures full of tables, diagrams and conditional steps. It helps to give a rough breakdown by type and length, along with a sense of how consistent the formatting is and how many are scanned documents rather than editable files, since those details affect how much review each procedure needs after conversion.

The split between authors and field users matters because the two groups use the system very differently, with a relatively small number of engineers and procedure owners writing, reviewing and approving content and a much larger group of operators and technicians running jobs on phones and tablets. Pricing often treats these groups differently, so knowing the rough size of each, and whether contractors will need access, avoids surprises once the proposal arrives.

Integrations and support add their own variables, such as whether the system needs to connect to a maintenance management system, a document management system or an identity provider, and whether the business expects help with change management and training on top of the software itself. A rollout across many sites over several years will also be scoped differently from a single site starting small, so it helps to share the intended pace as well as the end state.

Having rough estimates of these up front makes it much easier to get a realistic proposal, since procedure libraries vary a lot in size and complexity. If exact numbers are not available, a sample of procedures from one site is often enough to estimate the rest, especially if the sample includes a mix of the simplest and most complex documents rather than only the cleanest examples.