Cost evidence methodology
Cost-estimate confidence
How AIM calculates and reports confidence for hardware, cloud, software, labor, and lifecycle cost estimates without presenting false precision.

Note: This page is about confidence levels on the cost estimates AIM provides (hardware/cloud/SaaS). It is not related to your organization's AIM contract entitlements.
AIM provides transparent pricing estimates with explicit confidence levels. Every cost estimate includes a confidence rating so decision-makers understand the reliability of the numbers and when to seek vendor quotes.
This page explains how confidence levels are determined, what data sources inform pricing, and how to interpret the estimates in modernization reports.
1. Confidence Levels Explained
AIM uses three confidence labels. Each label describes the evidence behind a number. AIM does not publish a measured forecast-error percentage for these labels.
HIGH Confidence
The unit price comes from an organization contract, a manual verification, or a current provider price list. This describes the price source. It does not make an estimated quantity certain, and it is not a measured error band.
MEDIUM Confidence
Public list pricing or a partner estimate. Useful for planning and scoping. Confirm with a quote before a budget is locked. This is not a measured error band.
LOW Confidence
A benchmark, a manufacturer list price, incomplete data, or a line that still needs a quote. Useful for order-of-magnitude planning. A vendor quote is required before the number is used as a budget. This is not a measured error band.
2. How Confidence is Calculated
Line Item Confidence
Each pricing line item receives a confidence level based on the data source:
| Source Type | Confidence | Description |
|---|---|---|
| CONTRACT_OVERRIDE | HIGH | Organization-specific contract pricing |
| MANUAL | HIGH | Manually verified and entered prices |
| CLOUD_API | HIGH | Current provider list price for AWS, Azure, GCP, or OCI. This is unit-price evidence. The stored source name may be CLOUD_LIST. It does not rate the usage forecast. |
| PUBLIC_LIST | MED | Vendor public pricing pages |
| PUBLIC_LIST / MSRP | LOW | Manufacturer list price — baseline reference before contract discounts |
| MISSING / REQUIRES_QUOTE | LOW | No price available, vendor quote required |
Overall Report Confidence
Overall confidence is the more cautious of two separate ratings. Counting how many lines are priced is not enough, because a few uncertain lines can be most of the dollars.
- Unit-price confidence is dollar-weighted across infrastructure lines and software-license lines. Each priced line counts in proportion to its extended cost. An unpriced line with a planning range counts at the midpoint of that range. An unpriced line with no planning range is treated as large as the biggest priced line. HIGH requires every one of those lines to have a price and at least 80 percent of the weighted dollars on HIGH sources. If no priced line has a verified date, the unit-price rating drops one step, so MED becomes LOW. The rating is LOW when unpriced dollars are more than a quarter of the weighted total, when more than half the weighted dollars are LOW or unpriced, or when more than a quarter of the lines are unpriced and at least one of those lines has no planning range.
- Quantity confidence covers usage, runtime hours, and headcount. A current cloud unit price does not make a usage forecast high confidence. A cloud cost category, or a cloud provider on the line, caps quantity confidence at MED. When a per-unit license is present, each missing user count, server count, endpoint count, site count, or cloud pricing region lowers quantity confidence. One missing input caps it at MED. Two or more make it LOW.
- Overall confidence is the more cautious of the two ratings. These labels are planning guidance. They are not a validated variance percentage.
Confidence Downgrades
Confidence may be downgraded when key cost inputs are missing:
- A per-user, per-server, per-device, or per-site license is present, and any of these inputs is missing: internal user count, server count, endpoint count, site count, or cloud pricing region
- One missing input caps quantity confidence at MED. Two or more make it LOW
3. Size-Based Recommendations
Your organization size selection in the assessment directly affects which products and pricing tiers AIM recommends:
Small
50-200 users, single location
Medium
200-1,000 users, multi-department
Large
1,000+ users, enterprise/multi-agency
Why Size Matters
Selecting the correct organization size ensures you receive appropriate recommendations. A small municipality won't be recommended enterprise-class hardware designed for multi-agency deployments, and a large enterprise won't receive entry-level solutions that can't scale. If you skip the size selection, AIM defaults to Medium-tier recommendations.
4. Pricing by Category
AIM estimates costs across multiple categories, each with different data sources and typical confidence levels:
Layer 1: Physical Infrastructure
Cabling, rack installation, power, cooling, and physical buildout costs.
Hardware
Servers, networking equipment, storage arrays, endpoint devices, and other physical IT assets.
Size-Based Recommendations
Hardware recommendations are tailored to your organization size selected in the assessment:
How Hardware Prices Are Sourced
Hardware estimates use manufacturer-published list prices (MSRP) as a LOW-confidence reference baseline. Actual prices depend on your procurement vehicle and order volume:
Cloud Services
AWS, Azure, GCP compute, storage, networking, and managed services. List prices are fetched from live provider APIs into the Cloud List Prices (Auto) pricebook for multiple US and EU regions each refresh. When you specify a deployment region on the assessment, AIM uses that region's list price. When you leave it unset, AIM averages US East and US West reference prices — not a single coast — so estimates stay geographically neutral until you refine them.
Software Licensing & SaaS
Operating systems, productivity suites, identity providers, observability platforms, and other licensed software.
IT Labor & Professional Services
Implementation, migration, and ongoing operational labor costs. AIM automatically detects your organization's sector from the assessment and applies the appropriate labor rate model — so a hospital gets Healthcare IT staffing rates, not federal pay scales.
5. Approximate Pricing (~)
Some products show prices with a ~ prefix, indicating approximate pricing:
What ~ Means
Approximate prices are researched estimates based on industry knowledge, partner feedback, or publicly available ranges. While not exact vendor-published prices, they provide realistic planning figures.
~$5/user/month — Contact vendor for exact quoteApproximate pricing includes vendor contact information so you can get exact quotes:
| Price Display | Meaning | Confidence |
|---|---|---|
| $36/user/month | Vendor-published SKU price | HIGH |
| ~$5/user/month | Researched approximation | MED |
| Contact Vendor | Quote required, no estimate available | LOW |
6. Understanding “Contact Vendor”
Some products display vendor contact information instead of a price. This occurs when:
- Enterprise custom pricing — Products like MuleSoft, Databricks, or Tyler Technologies where pricing is negotiated based on usage, modules, or organization size
- Population-based licensing — Municipal software priced by city/county population
- Usage-based pricing — Products charged by API calls, data volume, or compute units where usage cannot be estimated
- Enterprise tier — When the SMALL/MEDIUM tier has published prices but LARGE tier is enterprise-only
Example Contact Information
Tyler Technologies: tylertech.com/contact or 1-800-772-2260
Oracle: oracle.com/corporate/contact or 1-800-392-2999
Salesforce: salesforce.com/government/contact
SAP: sap.com/contact or 1-800-872-1727
What to Do
Contact the vendor directly using the provided information. For municipal software (Tyler, OpenGov, etc.), pricing typically depends on population, modules selected, and contract terms.
7. How to Improve Confidence
If your report shows LOW confidence, here are steps to improve it:
Provide Cost Inputs
Ensure user count, server count, endpoint count, and site count are entered in the assessment wizard.
Add Contract Pricing
For Enterprise members, upload existing vendor contracts to create organization-specific pricebook overrides.
Request Vendor Quotes
For “Requires Quote” items, obtain budgetary quotes from vendors and enter them as manual price overrides.
Refine Environment Details
Specify cloud provider preferences, a primary deployment region (e.g. westus2, us-west-2, us-phoenix-1), and runtime modes (business hours vs 24x7) to get more accurate cloud pricing. Project state is for regional labor rates only — it does not set cloud list-price region.
8. Total Cost of Ownership (TCO) Calculator
While individual cost estimates show per-product pricing, the TCO Calculator combines every cost category into one view. You choose a 3-year or 5-year total. Year 1 includes one-time startup costs within either horizon. Open the assessment in AIM Basis after generating recommendations to use the calculator.
What the TCO Calculator Includes
The TCO Calculator sums stored prices for the recommended stack, then adds the lifecycle lines you turn on. A product with no stored price is named and left out of the total. AIM does not fill that blank with a category estimate.
Annual subscriptions, SaaS fees, perpetual licenses, and recurring renewals from your selected products
Cloud compute, storage, networking, and hardware costs from recommended deployments
Included only when a cited custom-build hour estimate is on file. AIM does not estimate implementation as a percentage of software cost.
Year 1 planning rate of $750 per user. The line states the rate. It is not a vendor training quote.
A perpetual license uses its vendor maintenance rate. The 20% line applies only to perpetual software that is not already on that vendor line. Subscription fees are not charged support again.
Cabling, terminations, pathways, firestop, and installation labor with regional adjustments (Year 1 only)
Configurable Parameters
You control the projection to match your planning scenario:
| Parameter | Options | Effect |
|---|---|---|
| Projection Period | 3 or 5 years | Sets a 3-year or 5-year total. Year 1 is always its own column inside that total. |
| User Count | Any number | Scales per-user/per-seat licensing costs |
| User Growth Rate | 0-50% per year | Compounds per-user costs year over year |
| Inflation Rate | 0-20% per year | Applies annual inflation to all recurring costs |
| Discount Rate (NPV) | Percentage | Calculates Net Present Value for investment comparison |
How Costs Are Projected
Recurring costs (annual and monthly licenses) are projected forward with compound growth and inflation. For per-user products, both user growth and inflation apply. For flat-fee products, only inflation applies.
One-time costs (perpetual licenses, training, and physical infrastructure) appear in Year 1 only. A cited custom-build estimate also carries its sustainment hours in later years. Implementation is not added as a percentage of software cost.
Billing period normalization: Monthly prices are annualized (multiplied by 12), hourly prices are annualized (multiplied by 8,760 hours/year), and one-time prices are kept as single Year 1 entries. This ensures all costs are compared on a consistent annual basis.
TCO vs. Base Estimates
Base cost estimates (shown in the Modernization Report and Vendor Brief) reflect product-level pricing only. The TCO Calculator projects stored product prices over the horizon you choose, and adds training, support, and physical infrastructure when those lines are turned on. Implementation is added only from a cited custom-build hour estimate. Use the TCO total for budget planning when every recommended product has a stored price. When the calculator lists excluded products, the total is the priced portion only.
9. Important Notes
Estimates Are Planning-Level
All AIM pricing estimates are intended for planning and scoping purposes. Final budgets should be validated with vendor quotes, contract negotiations, and procurement processes.
Prices Change
Vendor pricing changes over time. AIM pricebooks are updated periodically, but prices may differ from current vendor rates. Always verify current pricing for procurement.
Excludes Implementation
Unless explicitly stated, pricing estimates typically exclude implementation labor, training, data migration, and ongoing operational costs. These should be budgeted separately.
Questions About Pricing?
Learn more about how AIM works or get started with your first assessment.