Six months into COVID, everyone is buying software. Remote work tools, digital signing platforms, collaboration suites, analytics dashboards. The purchasing cycles that used to take six months are happening in six days. I get it. When your entire workforce goes remote overnight, you need tools and you need them now. But the contracts being signed this year are going to cause headaches for years. Because the number on the quote is never the number you'll actually pay.
The Quote vs The Cost
Every enterprise software quote shows the same thing: licence fees, maybe a setup cost, maybe some training hours. It's clean. It fits on one page. It looks like the total cost.
It's not.
We've been on both sides of this. RIVER builds custom software for enterprise clients, and we also help those clients evaluate and integrate third-party tools. Over five years, we've watched the same pattern repeat. The quoted price accounts for 40-60% of the actual cost of ownership. The rest hides in places that only become visible after the contract is signed.
This isn't always malicious. Some vendors genuinely don't know what their product will cost in your environment because they've never seen your environment. But the effect is the same: you budget for the quote and spend double.
Where the Costs Hide
Integration
Every software vendor says integration is "straightforward." In a demo, it is. They show the API documentation, walk through a sample connection, maybe demonstrate a pre-built connector for Salesforce or Xero. Thirty minutes. Looks easy.
It's never easy.
Your systems don't match the demo environment. Your data formats have quirks that the pre-built connector doesn't handle. Your authentication setup requires custom configuration. The API documentation is three versions behind the actual API. The vendor's "integration specialist" has never seen your tech stack before.
3x
the average ratio of actual integration cost to vendor-estimated integration cost, across enterprise SaaS deployments
Source: MuleSoft Connectivity Benchmark Report, 2020
We worked with a client this year who budgeted $15,000 for integrating a new HR platform with their existing payroll system. The vendor's quote included "standard integration support." The actual integration, accounting for data mapping, testing, error handling, and the three rounds of fixes when edge cases emerged, cost $52,000. Nobody lied. The vendor quoted for the standard path. The client's environment wasn't standard.
Budget for integration as a separate line item. Get an independent estimate, not the vendor's. If the vendor says integration will take two weeks, plan for six.
Data Migration
Closely related to integration, but with its own set of hidden costs. Moving data from your existing system to the new one is rarely as simple as an export and import.
Data formats differ. Field mappings don't line up cleanly. Historical data has quality issues that the old system tolerated but the new system rejects. Relational data loses its relationships during transfer. Attachments, notes, and audit trails either come across corrupted or don't come across at all.
The vendor's migration tool handles the happy path. Your data isn't on the happy path. Nobody's data is on the happy path.
If your existing system has more than a few thousand records, budget for a dedicated migration phase. Include data cleaning time. Include validation time. Include the second migration attempt, because the first one will find problems you didn't anticipate.
Training and Adoption
The quote might include "two hours of admin training" or "access to our learning portal." That's a start, not a solution.
Enterprise software adoption requires more than knowing which buttons to click. Your team needs to understand how the new tool fits into their existing workflows. They need to know what changed and why. They need someone available to answer questions during the first few weeks, when the friction is highest and the temptation to revert to the old way is strongest.
The real training cost is productivity loss during the transition. A team that was proficient in the old system will be slower in the new one for weeks, sometimes months. That's not a line item on any vendor quote, but it's a real cost measured in hours, delayed work, and frustrated staff.
Plan for internal champions. Identify people in each team who'll learn the new system deeply and support their colleagues. Give them time to learn. This costs money. It also determines whether the tool gets adopted or abandoned.
Customisation That Voids Support
Most enterprise tools need some customisation. The vendor accommodates this, up to a point. Beyond that point, you're on your own.
The boundary between "supported configuration" and "unsupported customisation" is rarely clear in advance. A client of ours customised their CRM's workflow engine to match their approval process. Reasonable change. Well within the platform's capability. When the next major update broke the customisation, the vendor's support team told them it was outside the support agreement. Fix it yourself, or pay professional services rates.
Before customising any enterprise tool, ask the vendor explicitly: will this customisation remain supported through platform updates? Get the answer in writing. If the customisation is essential to your use case and the vendor won't guarantee support through updates, that's a significant ongoing risk.
Licence Creep
The initial quote is for your current user count. Enterprise doesn't stay at current user count.
Per-user licensing seems straightforward: $50 per user per month, 100 users, $5,000 per month. But organisations grow. New hires need access. That department that said they didn't need it starts requesting licences six months in. Contractors need temporary access. The "100 users" becomes 150, then 200.
Some contracts include volume discounts at higher tiers. Many don't. Some have minimum commitment clauses that prevent you from scaling back down if you reduce headcount. Read the scale-up pricing carefully. Ask about the scale-down terms too.
And watch for the "premium tier" trap. The basic features get you in the door. Six months later, when you need the reporting module, the API access, or the SSO integration, those are premium features at a higher per-user rate. The total cost doubles without the user count changing at all.
Exit Costs
This is the one nobody asks about at procurement. It's the one everyone wishes they'd asked about when the contract is ending.
What happens when you want to leave? Can you export your data in a standard format? All of it? Including attachments, relationships, and audit history? How long do you have to export after cancellation? Is there a fee for the export? What format does the data come in, and is it usable without the vendor's platform to interpret it?
Some contracts include explicit exit fees. Others make exit expensive through data format lock-in. If your data only makes sense inside the vendor's platform, you're paying to stay whether you want to or not.
Ask about exit terms before you sign. The ones who lock you in know they can't.
Isaac Rolfe
Managing Director
A Procurement Checklist
Before signing your next enterprise software contract, check these items. This takes an hour and can save you tens of thousands.
Integration. Get an independent estimate for connecting the new tool to your existing systems. Don't rely on the vendor's estimate.
Data migration. Ask for a detailed migration plan, not a promise. Include a pilot migration of real data before committing to the full migration.
Training. Budget for internal champions, not just vendor training sessions. Account for productivity loss during the transition period.
Customisation boundaries. Get written confirmation of what customisations remain supported through platform updates.
Licence terms at scale. Model the cost at 150% and 200% of your current user count. Check scale-down terms.
Premium features. Identify which features are in the base tier and which require upgrades. Map your roadmap against the pricing tiers.
Exit terms. Confirm data export formats, timelines, and fees. Test an export before you have to do one under pressure.
Contract length and renewal terms. Auto-renewal clauses are common. Know your notice period for cancellation. Some contracts auto-renew for a full year if you miss a 30-day window.
Buying Under Pressure
I know the current climate doesn't allow for lengthy procurement. Teams need tools now, not after a three-month evaluation. That's fair.
But "fast" doesn't have to mean "blind." Even in a crisis purchase, reading the contract's exit clauses takes fifteen minutes. Checking the per-user pricing at double your current count takes five. Asking "what format does data export in?" takes one.
The tools you're buying this year will be in your stack for years. The contract terms you accept today will define what flexibility you have tomorrow. Spend an hour on the fine print now. You'll thank yourself in 2022.