The upgrade is the riskiest moment with a client

What I saw

For almost two years I worked in support at Ivalua, a procurement software company. The hardest problems almost never came from daily use. They came during upgrades: moving a client from one version of the software to the next.

The account I took over in the middle of an upgrade is a good example. When I arrived, the client could not go live.

Why upgrades are so hard here

Large clients set up a procurement platform to fit their own way of buying. Over the years, that setup grows. Each upgrade then has to work with all of it, so it stops being a simple update and becomes a project of its own.

This is not true of every SaaS product. A simple tool updates itself and nobody notices. But for big, configurable enterprise platforms like procurement suites, every client is a little different, and the upgrade is where those differences show.

Why it matters

An upgrade is the moment a client judges its vendor most closely. If it goes wrong, trust drops fast. If it goes well, the relationship gets stronger. On my own accounts, all three clients that came up for renewal renewed.

So the people who handle upgrades are not just fixing tickets. They are protecting revenue.

Renewals are won or lost during upgrades, not in sales meetings.

The point of this note

Key takeaways

1. In procurement software, the hardest problems show up during upgrades, not daily use.
2. Big clients customise the platform heavily, so each upgrade becomes its own project.
3. Handle upgrades well and you protect the renewal.