ERP Pricing, Licensing & 3–5 Year TCO: How to Compare Quotes

Normalise every quote to the same scope

Create one buyer-owned commercial scope sheet.

Send the same sheet to every shortlisted vendor.

At minimum, define:

When every vendor prices this same baseline, the quotations start becoming comparable.

Do not assume every “user” means the same thing

ERP vendors can license access in different ways.

Depending on the product, pricing may distinguish among concepts such as:

Not every ERP uses all of those models. That is exactly why the buyer should ask.

A vendor quoting 100 named users and another quoting 30 concurrent users may be pricing very different access models.

For each user category in a quote, establish:

1. Who needs it?
2. What can that user actually do?
3. Is access tied to a named individual or to simultaneous usage?
4. Can the licence be reassigned?
5. Is a minimum quantity required?
6. What happens when headcount increases?
7. Are temporary or seasonal users treated differently?
8. Are mobile users included?
9. Are system/API/integration users separately licensed?

The commercially important question is not just:

That distinction can materially change the economics.

Define the implementation boundary

A software price is not an implementation price.

Ask exactly what the implementation quotation includes.

Possible work may include:

• discovery/workshops;
• process mapping;
• configuration;
• master setup;
• reports;
• data migration;
• integrations;
• custom development;
• testing support;
• user acceptance testing support;
• training;
• cutover;
• go-live support;
• post-go-live stabilisation.

Do not assume all are included simply because the proposal says:

“ERP implementation.”

Ask what is explicitly excluded

If the answer is:

“We will decide during implementation”

then the buyer has discovered a cost uncertainty that belongs in the commercial evaluation.

Fixed price, estimate or time-and-material?

These are different risk allocations.

None of these models is automatically superior.

Build the TCO year by year

Do not put every cost into one total and lose the timing.

A simple model can look like this:

A three-year horizon can be useful for shorter commercial decisions.

A five-year view often reveals lifecycle differences more clearly.

The important thing is that every vendor is compared over the same horizon.

Compare perpetual and subscription over the same period

A perpetual licence can appear expensive in Year 1 because more software cost may be upfront.

A subscription can appear cheaper in Year 1 because cost is spread over time.

Neither observation tells you which has lower TCO.

Use the same period.

For example:

Then compare the totals and, more importantly, the rights and responsibilities behind them.

Model growth before you sign

Do not calculate TCO only for today’s organisation.

Create at least one realistic growth scenario.

Ask:

You do not need to predict the future perfectly.

You need to understand the pricing mechanics when the future arrives.

Challenge renewal and escalation assumptions

A multi-year cost model is only as good as its assumptions.

For every recurring commercial line, ask:

• Is the price fixed for the contract term?
• Can it increase annually?
• What determines the increase?
• Is renewal automatic?
• What notice is required?
• Is there a minimum commitment?
• Does reducing user count reduce the charge?
• What happens if modules are removed?
• Is support mandatory?
• What happens if support lapses and is later restarted?
• Are additional users priced at today’s rate or the future rate?

Do not assume.

Put the commercial rules into the model.

Keep taxes and currency treatment consistent

Two quotations can look different because one includes taxes and another does not.

Decide with Finance whether the comparison should use:

• pre-tax amounts;
• tax-inclusive amounts;
• recoverable versus non-recoverable taxes.

Apply the same basis to every vendor.

Likewise, if quotes contain different currencies, decide which exchange-rate assumption the business case will use.

Do not let formatting differences become commercial differences.

Include internal business cost

ERP implementations consume buyer-side capacity.

Typical internal contributors may include:

• project sponsor;
• finance;
• IT;
• operations;
• accounts;
• plant/warehouse users;
• power users;
• master-data owners.

Even where there is no incremental payroll expense, that time has an opportunity cost.

This matters particularly when comparing two systems where:

• one requires materially more internal configuration;
• one requires greater data preparation;
• one requires more testing;
• one creates a larger ongoing administration burden.

Do not ignore internal effort simply because no vendor invoices it.

ERP commercial red flags

A practical ERP quote-normalisation sheet

Before comparing final prices, make every vendor answer the same table.

Only once this table is coherent should procurement spend time arguing over the bottom line.

How exactllyERP fits into this comparison

ERP commercial comparison checklist

Before approving the commercial decision, confirm the following.