Vendor renewal season: questions to ask before signing another three-year term

A renewal quote often arrives when leverage is already slipping away. The business owner assumes the system is staying. Procurement checks the increase. IT confirms that it still runs. The vendor offers a better rate for three years, provided the agreement is signed this month.

Before accepting, use the renewal window to ask whether the relationship still fits the business. The answer may be yes. A considered renewal is far less disruptive than a last-minute search for alternatives.

Are we paying for what people use?

Begin with a current inventory of licenses, modules, environments, support tiers, storage, transaction fees, and add-ons. Compare invoices with actual users and use.

Do not confuse login counts with adoption. A user may log in monthly because the process requires one approval. That may be legitimate. Another team may export everything to a spreadsheet because the licensed workflow does not work for them.

Ask operating owners what they rely on, what they work around, and which promised capabilities never became part of the process. Remove unused capacity where the contract allows, but avoid cutting spare licenses that support planned hiring or seasonal work without understanding the need.

If the vendor bundles products, price the bundle against the components the company would choose today. A discount on unused software is still spending.

Has the service matched the agreement?

Review meaningful incidents, support cases, implementation promises, and recurring problems. How quickly did the vendor restore service or provide a workable answer? Did your own team supply the information and escalation needed under the agreement?

Service credits may matter less than the operating consequence of an outage. Ask whether current commitments reflect when the business needs the system. A four-hour response is not a four-hour resolution. Scheduled maintenance that is harmless to one customer may interrupt your busiest shift.

Use specific history in the negotiation. “Support needs improvement” is weak. A record of unresolved cases, repeat outages, or delayed root-cause reports gives both parties something concrete to address.

What will change during the term?

Three years is a long time in the operating life of a mid-market company. Discuss known acquisitions, facilities, divestitures, product changes, customer requirements, and staffing shifts.

Then read how the agreement handles them. Can entities and locations be added or removed? What happens to price if volume declines? Can licenses move among users? Are integrations, application programming interfaces, or test environments included? Does the vendor have the right to retire a feature the business depends on?

Ask what is fixed. Some agreements lock the subscription rate but allow increases in support, usage, hosting, or third-party components. Define the total commercial model, not only the headline unit price.

What data and access are involved?

Update the security and privacy review based on actual use. The system may now hold more sensitive data or connect to more applications than it did at the last contract.

Confirm where company data is stored, who can access it, how incidents are reported, and which subcontractors provide material services. Review authentication, administrative access, logging, backup, recovery, and deletion practices at a level proportionate to the system’s importance.

For an AI-enabled feature, ask what data reaches the model or provider, whether customer content is used for training, how outputs and prompts are retained, and whether the feature can be disabled. Product labels are not enough. The contract and configuration should match the intended use.

Security questionnaires are useful only if someone reviews changes and exceptions. Focus on the few controls and service dependencies that could materially affect your company.

Can we leave without losing the business process?

The time to study exit terms is before renewal.

What data can the company export, in what format, and at what cost? Does the export include attachments, history, configuration, and audit records, or only current tables? How long will access remain after termination? What assistance is available, and at which rates? When will the vendor delete remaining copies?

Technical data is only part of exit readiness. Document the processes, integrations, reports, and customer or supplier connections that would need to move. Identify any proprietary device, file format, or interface that limits alternatives.

You do not need a full migration plan for every renewal. You do need to know whether exit is feasible and whether contract language makes it unnecessarily expensive.

Who can change the deal?

Read renewal notice periods, termination rights, assignment terms, price adjustments, and vendor rights to change online policies. Important terms should not disappear into a web page that can be revised unilaterally.

Coordinate business, legal, security, IT, finance, and procurement reviews early enough to negotiate. Counsel should interpret legal terms. The operating owner should approve the business tradeoffs. Do not ask IT to accept service or liability positions on behalf of the company.

Be realistic about leverage. A smaller customer may not win every requested change. Prioritize the clauses tied to the most plausible and consequential events. A clear escalation path or usable data export may matter more than a theoretical concession.

Make a deliberate term decision

A long term can be reasonable when the product is embedded, service is sound, pricing is predictable, and the company’s direction is stable. A shorter term or renewal option may be worth a higher annual rate when ownership is changing, a replacement is plausible, or the vendor has not resolved material issues.

Compare the discount with the cost of lost flexibility. Include implementation and change costs, but do not use sunk cost as the only reason to remain.

Create a one-page renewal recommendation that states current spend, term, expected changes, unresolved risks, negotiated improvements, and the accountable business owner’s decision. Record the next notice date immediately. Renewal management gets easier when it starts months before the quote.

EdgePoint can support a technology and operating review when a material renewal crosses several functions. For routine vendors, the questions above are often enough to turn an automatic extension into an informed choice.