Software procurement checklist. Last reviewed:
The hidden costs in business software contracts are the charges and commitments missing from the headline subscription price: unused seats, longer commitments, essential add-ons, usage overages, integration work, migration, support, storage, renewal increases and exit assistance. Before signing, ask the supplier to price each against your actual operating needs.
This top 10 is an editorial checklist, not a measured ranking of vendors or fees. A cost may be clearly disclosed yet still overlooked in the buying process. What applies depends on your quote, order form and contract. The examples below are illustrative, not CYBORIUM client results or vendor prices.
For a broader business case, see our technology total cost of ownership guide. Here, the focus is narrower: the questions to resolve before accepting a software contract.
1. Seats you cannot remove or reassign
A user count is useful only when the contract defines who counts. Ask about administrators, contractors, occasional approvers, service accounts and external collaborators. Then check minimum quantities, reassignment rules and when paid quantities can fall.
Illustrative example: a team orders 80 seats for a rollout but activates 55. Removing accounts may not reduce the committed bill.
Ask: Which users need paid access, and when can we reduce quantities? Request a role-by-role licence schedule, minimum purchase, reassignment conditions and reduction dates. The FinOps Foundation identifies true-up and true-down terms as part of software purchasing analysis.
2. An annual commitment behind a monthly invoice
Payment frequency and commitment length are separate questions. A monthly instalment does not, by itself, establish a monthly right to leave. For a concrete vendor example, Microsoft documents product-specific cancellation windows for its new commerce experience.
Illustrative example: a project ends after four months, but its software commitment continues for the agreed term.
Ask: What remains payable if the project ends early? Request the full commitment value, cancellation conditions, notice process and end-of-term options in writing. Compare those with a shorter commitment before choosing the lower advertised monthly figure.
3. The edition needed for your essential features
Build the commercial comparison around required workflows. Identify the edition and add-ons needed for identity controls, audit information, reporting, automation and administration. Do not assume that a feature demonstrated in a trial is included in the quoted package.
Illustrative example: procurement compares entry editions, then discovers the required approval workflow needs a higher edition for the whole team.
Ask: Can every mandatory requirement be delivered under these exact product codes? Request a priced requirements matrix, including minimum add-on quantities. Ask the supplier to identify any dependency that forces a wider licence upgrade.
4. Usage meters and overage rates
Record every billable unit, including transactions, messages, API calls or AI usage where relevant. AWS Marketplace documents SaaS contracts with separately priced dimensions and additional usage charges. That is a practical reason to look beyond the base commitment.
Illustrative example: an automated synchronisation repeatedly processes unchanged records and consumes the monthly allowance early.
Ask: What exactly starts a charge, and how is it measured? Request included quantities, reset periods, overage rates and sample billing records. Confirm whether alerts merely notify you or whether a spending cap can actually stop further charges.
5. Integration licences and ongoing maintenance
“Integrates with your CRM” leaves commercial questions unanswered. Price the connector, middleware, implementation and maintenance responsibilities. Microsoft, for example, distinguishes capacity, consumptive and storage add-ons in Power Automate; an automation quote needs its entitlement assumptions checked.
Illustrative example: a connector exists, but mapping custom fields and handling failed records require separate work.
Ask: What does the integration price cover from setup through operation? Request charges for each system, environment and connector, plus change rates and responsibility for repairs. Include monitoring and support for failed synchronisations in the scope.
6. Migration and data preparation outside implementation
Ask what “migration included” means in measurable terms. Record counts alone do not describe attachments, historical activity, custom fields, duplicate cleanup or reconciliation. Put the expected source data and acceptance checks beside the implementation price.
Illustrative example: the package includes importing contacts, while historical notes and document attachments require extra effort.
Ask: Which data will arrive, in what condition, and who checks it? Request a migration inventory, trial import, reconciliation method, included rework and rate for exceptions. Allocate your own staff time for cleanup and testing, even when the supplier charges a fixed implementation fee.
7. Support and training beyond the included service
Define the help your team needs in Australian working hours, including the relevant time zone and daylight saving arrangements. Ask whether the service covers product faults, configuration questions and integration problems, or treats some as separately chargeable consulting.
Illustrative example: standard support covers the application, but assistance with a customised report is billed separately.
Ask: Who owns an incident involving multiple suppliers? Request support hours, escalation contacts, response commitments, exclusions and professional services rates. Price administrator training and onboarding for future employees, and distinguish a response target from a commitment to restore service.
8. Storage, retention and recovery requirements
Estimate data growth using the records and attachments your business will retain. Ask separately about live storage, audit logs, backups, retention settings and recovery assistance. A storage allowance tells you little about how easily a deleted record can be restored.
Illustrative example: a document-heavy workflow fits the initial allowance but needs extra capacity as attachments accumulate.
Ask: What costs more as our data grows or our retention needs change? Request allowances by storage type, excess rates, charging increments and restore charges. Have the supplier explain the practical recovery process and identify any additional service your requirements need.
9. Renewal increases, currency and lost discounts
Separate the initial discount from the pricing method for later terms. For an Australian decision owner, also identify the invoicing currency, conversion basis, payment fees and whether quoted totals include GST. Ask finance to compare offers consistently.
Illustrative example: a first-term discount expires while an overseas invoice also changes in Australian dollar terms.
Ask: How will our renewal price be calculated? Request the renewal basis, any agreed increase limit, notice date and treatment of added seats. Keep a dated quote and calendar the decision point using our software licence renewal guide.
10. Leaving, exporting data and running two systems
Price the exit before the relationship starts. Specify the data, attachments and configuration you need, export formats, access period and assistance rates. Allow for a transition period when the old and replacement systems may both be needed.
Illustrative example: exporting tables is straightforward, but rebuilding relationships and checking attachments takes additional work.
Ask: What would a complete, usable handover cost? Request a sample export and an exit service schedule. Our exit and transition-out guide explains the handover questions to include in procurement.
A short checklist to send with the quote
Ask the supplier to mark each item included, separately priced or excluded. Record assumptions and identify who pays if they change.
- Required users, editions, add-ons and reduction dates.
- Usage allowances, overage rates and spending controls.
- Integration, migration, support and training scope.
- Storage growth, recovery, renewal and currency assumptions.
- Export assistance and overlapping subscription periods.
Use the CYBORIUM TCO calculator to bring the priced items into a consistent comparison.
Frequently asked questions
Are hidden software costs always unfair?
No. Additional services and capacity can have legitimate prices. The procurement problem is approving a purchase before understanding what your intended use will require. A clear, complete quote makes that decision easier.
What should we request before signing?
Request the final order form, applicable terms, product codes, usage schedule, implementation scope and renewal and exit arrangements. Resolve differences between sales explanations and the documents you will rely on.
Can every additional cost be removed?
No. Some reflect necessary work or consumption. The aim is to price them, allocate responsibility and negotiate practical controls. Choose the package that meets your needs at an understood cost.
CYBORIUM provides technology contract negotiation support for Australian businesses. Contact CYBORIUM to review a software quote before committing.
