What Actually Moves the Price - ERP Contract and License Negotiation From the Client Side

John Hannan

58 minutes ago

9 min read

Selecting an ERP this year? If you lead a multi-site or regulated company and need a full selection program - requirements, RFP, scripted demos, decision - rather than a quick answer, see how our ERP software selection program works, or talk to John.

What is actually negotiable in an ERP contract?

The discount is usually the easiest part of an ERP proposal to see. The commitment underneath it takes more work to understand.

The number of users, the length of the term, annual increases, renewal provisions, and the subscription start date all affect what the company will spend. Implementation services bring another set of assumptions about scope, staffing, travel, and the work the client will perform.

When I help a client negotiate as part of an ERP selection, I want those terms understood alongside the discount. A proposal can improve in one area while becoming more expensive or less flexible in another. The company needs to see the effect across the period it is committing to.

What one year-end package looked like

At one vendor's fiscal year-end, we negotiated a subscription package at 25 percent off list. The unit price was fixed for six years. After that, the annual uplift we had negotiated down from 10 percent to 7 and then to 5 would apply, with the increase at renewal capped at 3 to 5 percent. The first quarter was free, worth about $28,000.

These were negotiated terms, not savings the client kept. The vendor said plainly that the terms would be resubmitted after its deadline. The client's board chose to wait, the deadline passed, and the pricing went back to list. Before the board met, we had estimated the worst-case cost of waiting at close to $170,000 over the term. Deferring was the board's call to make, and it made that call with the number in front of it.

Start before the RFP goes out

A useful negotiation begins with a clear scope and a realistic decision calendar. Vendors need to know what they are pricing, which assumptions to use, and when the client expects to make a decision.

Our RFPs ask vendors to hold proposals valid for 60 days after submission. We also ask them to identify any incentive with an earlier deadline. That gives the selection team a basis for comparing offers and planning the approval process.

The request alone does not establish that the vendor has accepted the period. Review the response, resolve exceptions, and obtain the agreed validity dates in writing. If the decision will take longer, address the extension before the current offer expires.

The client's calendar needs the same attention. A committee recommendation may still require executive review, board approval, and legal review. Those steps take time even when the selection has gone well. Tell vendors early when the company can realistically complete them.

Evaluate the commitment behind the discount

A discount percentage needs a defined starting point. Establish which products and users it covers, whether it applies throughout the initial term, and what happens when the client adds capacity or renews.

Then model the proposal over a common period, as in a five-year cost comparison. If one offer has a lower first-year price but higher annual increases, the comparison should show both. If a concession requires a longer commitment, include that obligation in the decision.

There is no single discount percentage I would promise a client before understanding the product, scope, term, and competition. The relevant question is whether the complete offer is commercially sound for this business.

Match the user commitment to the rollout

A user ramp is a schedule for increasing the committed license count. It can be appropriate when it follows a real deployment plan. It can also create cost before the company is ready to use the licenses.

In one negotiation, the proposed agreement increased the user commitment over the term without a corresponding client requirement. We challenged the ramp and removed it. The reason to challenge it was the mismatch with the business plan.

I would start with the users needed for implementation and initial operations, then map later additions to the expected rollout. Where possible, negotiate the commercial treatment of those additions in advance. Avoid assuming that a future purchase will receive today's discount.

The same review applies to user types. The company needs to understand what each category permits, which people require it, and how that mix is expected to change.

Decide how much term is worth committing to

A longer agreement can offer price protection or a better rate, but it also commits the company for longer. I would compare the financial benefit with the flexibility being given up.

In one deal, we reduced a proposed five-year commitment to three years. In another situation, a longer term might be reasonable if the company has a stable requirement and the commercial protection is worthwhile.

Ask what the longer term actually protects. Is the unit price fixed? Is there an agreed annual increase? Does the protection extend to additional users, modules, and renewal? Those are different provisions and should not be described interchangeably.

Model annual increases and renewal separately

An annual increase within the committed term is different from the change allowed when that term ends. Check both.

In one negotiation, a proposed 5 percent annual increase became 3 percent. For an unchanged subscription scope with four annual increases, the year-five charge would be about 22 percent above year one at 5 percent, compared with about 13 percent at 3 percent. That is an illustration of the annual charge, not the percentage saving across the full five years.

Use the permitted increases when modeling the agreement. A salesperson's description of what the vendor typically does is useful context, but the client needs to understand what its own terms allow.

At renewal, establish the basis for the next price. A cap on an increase needs a clear reference point and scope. Ask whether it applies to the same products and quantities, how changed requirements are treated, and what notice the client must give before renewing or reducing a commitment.

Separate subscription start from payment timing

The subscription start date, the start of billing, and the invoice due date can be different. Moving a payment date does not necessarily reduce the subscription cost.

In one negotiation, payments were moved from signature to project kickoff. One program had subscription charges beginning eight months before go-live. That pre-production period needs to be understood in the business case.

Some access is needed to configure the system, migrate data, and test. The question is whether the licenses and environments being purchased during that period match the work taking place.

I would ask the vendor to explain the implementation-period options, what access is included, and when the full production commitment begins. Agree dates or milestones that can be administered clearly, including what happens if the project schedule changes.

Establish how usage and license counts can change

Where pricing depends on transaction volume, storage, or another usage measure, start with a supportable forecast and understand how the measure is calculated.

One client agreed an initial minimum tier with a later true-up after go-live. That arrangement gave the company an opportunity to use actual operating data for the adjustment. It was a negotiated structure, not a reason for every company to buy the smallest tier.

For any such arrangement, establish the measurement period, adjustment date, overage rates, and whether adjustments can move both up and down.

User counts deserve the same treatment. Ask when licenses can be added, reduced, or moved between types, and what price applies to each change. Do not assume that additional users will be priced at list, that they will receive the original discount, or that reductions will be permitted when the business wants them. Put the agreed treatment into the commercial documents.

Check the unit economics without losing the scope

I calculate a proposal back to a per-user monthly cost where that measure is useful. It can expose a misunderstanding about quantities, products, or the period being quoted.

I have sent a proposal back because that calculation was far outside the other offers and did not make sense for the client. Clarifying the commercial basis corrected the disconnect before the proposal was treated as final.

The measure still needs context. A package with more modules, included environments, or different user rights cannot be judged by a per-user figure alone. Use it as a reason to investigate, then compare the full scope.

Negotiate services with the delivery plan in view

Implementation services can be a substantial part of the investment. The hourly rate matters, but so do the hours, the experience of the people doing the work, and what the client is expected to provide.

In two negotiations, implementation partners reduced proposed hourly rates by 20 percent and 27 percent. Each knew it was one of two finalists. Those are examples from particular deals, not a standard reduction every client should expect.

Maintaining credible competition is part of managing the partner selection. The alternatives need to be real, and the process should remain fair to the partners investing time in it.

A lower rate is valuable only if the total delivery proposal still makes sense. Check the scope, staffing, estimated effort, and exclusions after a revision. Confirm that work has not disappeared from the estimate or moved to the client's team without discussion.

A fixed fee or a not-to-exceed arrangement can provide useful protection when the scope and assumptions are clear. Where time and materials is appropriate, I would want spending visibility, a current forecast to complete, and an agreed process for approving additional work. Payment milestones and acceptance criteria should reflect the work being delivered. The areas we review before signature are in our decision check.

Travel, data migration, integrations, and support after go-live also need a place in the budget. A concession on rates does not settle those costs.

Handle deadlines through the decision process

A vendor may have a legitimate commercial reason to offer terms through a particular date. The client still needs enough time to understand the commitment and complete its approvals. I have seen deals pulled when a client could not finish its legal review in time for the vendor's financial close, so the calendar matters to both sides.

If the proposed deadline is unrealistic, explain the remaining steps and ask for an extension in writing. Identify exactly which terms would change if the date passes. That lets the client assess the cost of waiting alongside the consequences of signing before it is ready.

An estimate of that cost should show its assumptions. Compare the current offer with the documented alternative, and distinguish a confirmed price change from a possible one. The board can then decide whether the benefit of waiting justifies the financial exposure.

Keep communications coordinated. A vendor's request to meet an executive can be useful when it resolves an open issue. It should fit the selection process, with material clarifications shared where they affect other participants.

Keep the preferred vendor decision conditional

Once the committee has a preferred vendor, we identify the remaining commercial, delivery, and legal questions. I make clear that the recommendation is subject to resolving those items.

Where a credible second choice remains, keep that option available until the client is ready to commit. Do not represent a vendor as competitive if the company would not actually select it.

The preferred vendor should understand what is needed to finish. A clear list of open items is more productive than repeated requests for a better price without explaining the remaining concerns.

We help the client compare the economics and resolve the business and delivery terms with its legal advisors. Both sides should understand the commitment before work begins.

Vendors are our partners in every selection we run, and their success is ours, so none of this is about tricking anyone. It is about reading the paper the way the vendor's finance team reads it.

If you have a proposal on the desk and a deadline in the email, talk to John about your ERP program.

Frequently asked questions

How much of an ERP discount is realistic?

It depends on the product, scope, commitment, and commercial situation. Evaluate the whole agreement, including annual increases, renewal, additional capacity, implementation costs, and timing. A larger discount does not necessarily produce a lower total cost.

Should we sign before the vendor year end?

Only when the company can complete its review and approvals properly. Ask for the offer's validity period and any extension in writing. If the terms will change, compare the documented cost of waiting with the reasons the company needs more time.

Can we reduce our ERP user count later?

That depends on the agreement. Establish when reductions and changes in user type are permitted, any notice requirements, and what happens to pricing. Resolve these questions before committing to quantities.

How much can implementation rates move?

In two competitive negotiations, proposed implementation rates fell by 20 percent and 27 percent. Those results do not establish a market benchmark. Compare the revised rate with staffing, scope, hours, and the total delivery cost.

Does a price hold in the RFP protect the offer automatically?

The client should confirm that the vendor has accepted the requested validity period and resolve any exceptions or earlier incentive deadlines. A requirement in the RFP and an agreed offer are separate steps.