Editable procurement file

SaaS Pricing Comparison Worksheet

Download a practical XLSX file to normalize quotes that use different billing units, included allowances, services, and renewal assumptions. The page explains the evidence, owners, review rules, and signoff standard behind the file.

PR97 working file · XLSX

Download the editable SaaS Pricing Comparison Worksheet

The file is designed for real review work, with structured fields, ownership prompts, status controls, and space for evidence.

Download XLSX

What this file is for

This saas pricing comparison worksheet helps a buying team normalize quotes that use different billing units, included allowances, services, and renewal assumptions. It is most useful when several functions need to contribute facts but one person must maintain a single decision record. The working question is which option has the best defensible cost range for the required operating scenario. Keeping that question visible prevents the team from collecting documents and comments that never change the decision.

Use the file before approval, and return to it whenever scope, quantities, data handling, delivery timing, or contract terms change. The expected coordinator is the procurement or finance analyst, with input from finance, procurement, the service owner, IT, security, implementation leads, and vendor account teams. The tool does not replace legal, security, privacy, finance, or technical judgment. It makes each judgment traceable to evidence and an accountable owner.

What the download contains

#Working areaHow to complete it
1Billable Unit And Forecast QuantityRecord the fact, its source, accountable owner, status, and the consequence if it remains unresolved.
2Edition, Module, And Included AllowanceRecord the fact, its source, accountable owner, status, and the consequence if it remains unresolved.
3Usage, Overage, And Add-On RuleRecord the fact, its source, accountable owner, status, and the consequence if it remains unresolved.
4Implementation, Migration, And Training FeeRecord the fact, its source, accountable owner, status, and the consequence if it remains unresolved.
5Internal Administration And Dependent Tool CostRecord the fact, its source, accountable owner, status, and the consequence if it remains unresolved.
6Renewal, Reduction, Export, And Exit AssumptionRecord the fact, its source, accountable owner, status, and the consequence if it remains unresolved.

The file also includes instructions, status choices, review notes, and a signoff area. Blank fields are intentional: they should be completed from the documents and tests for the actual purchase. Do not copy a previous vendor's answers unless the underlying facts are still current and apply to the same service scope.

Field-by-field review guide

Billable Unit And Forecast Quantity

Treat billable unit and forecast quantity as a decision input in the saas pricing comparison worksheet, not as a label that proves completion. The entry should show the current fact, the source that supports it, and the consequence for which option has the best defensible cost range for the required operating scenario. Ask the procurement or finance analyst to separate confirmed evidence from a planning assumption and to identify who can accept any limitation. Cross-check billable unit and forecast quantity against edition, module, and included allowance, because those two areas can reveal a hidden scope, timing, ownership, or contract conflict. Input from finance, procurement, the service owner, IT, security, implementation leads, and vendor account teams should remain attributable to the person and evidence used. A specific risk to test here is comparing monthly and annual headlines. Record the status, next action, due date, and proof needed for closure. The completed billable unit and forecast quantity record should still make sense to a renewal, incident, audit, or replacement team that did not attend the original meetings.

Edition, Module, And Included Allowance

Treat edition, module, and included allowance as a decision input in the saas pricing comparison worksheet, not as a label that proves completion. The entry should show the current fact, the source that supports it, and the consequence for which option has the best defensible cost range for the required operating scenario. Ask the procurement or finance analyst to separate confirmed evidence from a planning assumption and to identify who can accept any limitation. Cross-check edition, module, and included allowance against usage, overage, and add-on rule, because those two areas can reveal a hidden scope, timing, ownership, or contract conflict. Input from finance, procurement, the service owner, IT, security, implementation leads, and vendor account teams should remain attributable to the person and evidence used. A specific risk to test here is ignoring minimum commitments and premium support. Record the status, next action, due date, and proof needed for closure. The completed edition, module, and included allowance record should still make sense to a renewal, incident, audit, or replacement team that did not attend the original meetings.

Usage, Overage, And Add-On Rule

Treat usage, overage, and add-on rule as a decision input in the saas pricing comparison worksheet, not as a label that proves completion. The entry should show the current fact, the source that supports it, and the consequence for which option has the best defensible cost range for the required operating scenario. Ask the procurement or finance analyst to separate confirmed evidence from a planning assumption and to identify who can accept any limitation. Cross-check usage, overage, and add-on rule against implementation, migration, and training fee, because those two areas can reveal a hidden scope, timing, ownership, or contract conflict. Input from finance, procurement, the service owner, IT, security, implementation leads, and vendor account teams should remain attributable to the person and evidence used. A specific risk to test here is mixing optional modules into only one quote. Record the status, next action, due date, and proof needed for closure. The completed usage, overage, and add-on rule record should still make sense to a renewal, incident, audit, or replacement team that did not attend the original meetings.

Implementation, Migration, And Training Fee

Treat implementation, migration, and training fee as a decision input in the saas pricing comparison worksheet, not as a label that proves completion. The entry should show the current fact, the source that supports it, and the consequence for which option has the best defensible cost range for the required operating scenario. Ask the procurement or finance analyst to separate confirmed evidence from a planning assumption and to identify who can accept any limitation. Cross-check implementation, migration, and training fee against internal administration and dependent tool cost, because those two areas can reveal a hidden scope, timing, ownership, or contract conflict. Input from finance, procurement, the service owner, IT, security, implementation leads, and vendor account teams should remain attributable to the person and evidence used. A specific risk to test here is presenting first-year discounts as recurring economics. Record the status, next action, due date, and proof needed for closure. The completed implementation, migration, and training fee record should still make sense to a renewal, incident, audit, or replacement team that did not attend the original meetings.

Internal Administration And Dependent Tool Cost

Treat internal administration and dependent tool cost as a decision input in the saas pricing comparison worksheet, not as a label that proves completion. The entry should show the current fact, the source that supports it, and the consequence for which option has the best defensible cost range for the required operating scenario. Ask the procurement or finance analyst to separate confirmed evidence from a planning assumption and to identify who can accept any limitation. Cross-check internal administration and dependent tool cost against renewal, reduction, export, and exit assumption, because those two areas can reveal a hidden scope, timing, ownership, or contract conflict. Input from finance, procurement, the service owner, IT, security, implementation leads, and vendor account teams should remain attributable to the person and evidence used. A specific risk to test here is comparing monthly and annual headlines. Record the status, next action, due date, and proof needed for closure. The completed internal administration and dependent tool cost record should still make sense to a renewal, incident, audit, or replacement team that did not attend the original meetings.

Renewal, Reduction, Export, And Exit Assumption

Treat renewal, reduction, export, and exit assumption as a decision input in the saas pricing comparison worksheet, not as a label that proves completion. The entry should show the current fact, the source that supports it, and the consequence for which option has the best defensible cost range for the required operating scenario. Ask the procurement or finance analyst to separate confirmed evidence from a planning assumption and to identify who can accept any limitation. Cross-check renewal, reduction, export, and exit assumption against billable unit and forecast quantity, because those two areas can reveal a hidden scope, timing, ownership, or contract conflict. Input from finance, procurement, the service owner, IT, security, implementation leads, and vendor account teams should remain attributable to the person and evidence used. A specific risk to test here is ignoring minimum commitments and premium support. Record the status, next action, due date, and proof needed for closure. The completed renewal, reduction, export, and exit assumption record should still make sense to a renewal, incident, audit, or replacement team that did not attend the original meetings.

Decision rules

  • Use the same quantity forecast and contract term for every option.
  • Separate vendor charges from internal labor and dependent products.
  • Show expected and stress cases beside the base case.
  • Mark unknown amounts visibly instead of treating them as zero.

Common failure modes

  • Avoid comparing monthly and annual headlines.
  • Avoid ignoring minimum commitments and premium support.
  • Avoid mixing optional modules into only one quote.
  • Avoid presenting first-year discounts as recurring economics.

Evidence and signoff standard

A defensible file should let a later reviewer reconstruct the decision without relying on memory. For every material item, capture the source document or test, the date reviewed, the person responsible, and the next action. If evidence is restricted, record its approved location and a short conclusion rather than attaching it to an uncontrolled copy. If a vendor answer changes, preserve the final accepted version and note what superseded the earlier response.

Before signoff, verify that the record covers billable unit and forecast quantity, edition, module, and included allowance, usage, overage, and add-on rule, implementation, migration, and training fee, internal administration and dependent tool cost, and renewal, reduction, export, and exit assumption. Resolve critical gaps or document a time-limited exception. The final approver should understand both the desired outcome and the residual risk. Store the signed or approved copy with the contract, quote, implementation decision, or service inventory entry that it supports.

Questions to ask before approval

  • What evidence supports the entry for billable unit and forecast quantity?
  • What evidence supports the entry for edition, module, and included allowance?
  • What evidence supports the entry for usage, overage, and add-on rule?
  • What evidence supports the entry for implementation, migration, and training fee?
  • What evidence supports the entry for internal administration and dependent tool cost?
  • What evidence supports the entry for renewal, reduction, export, and exit assumption?

Authoritative references

The following public resources provide context for the control and acquisition principles used in this file. They do not answer vendor-specific questions; use the current vendor documents and your organization's policies for the actual decision.