TCO Worked Examples and Selection Checklists

How to compare ERP quotes: an RFP and normalisation method for MSMEs

Write a short ERP request for proposal, normalise vendor quotes to the same users, modules and years, and score price against fit. Illustrative example.

Updated · 4 min read

How to compare ERP quotes: an RFP and normalisation method for MSMEs

ERP quotes are rarely comparable as they arrive: one is per user per month, another per year with a platform fee, a third bundles implementation, and each counts users and modules differently. To compare them, send every vendor the same short request for proposal (RFP) with your numbers and requirements, then normalise the replies into one table: same users, same modules, same period, all before GST, with one-time and recurring costs separated and gaps priced in. Only then score price against fit. This guide shows how, with an illustrative example.

It belongs to the 3–5-year ERP TCO guide section.

What to put in a short RFP

An MSME does not need a 50-page tender. Four to six pages usually work:

  1. About the business: what you make or sell, locations, GSTINs, turnover band, number of employees.
  2. Volumes and users: the numbers sheet from the ERP requirements checklist.
  3. Requirements: must-haves and nice-to-haves by process, plus the Indian compliance list.
  4. Integrations: banks, payment gateway, marketplaces, devices.
  5. Commercial format: ask for prices in a fixed template (below), before GST, in rupees; if quoted in another currency, state the currency and billing entity.
  6. Contract questions: uplift cap, minimum users, exit and data export, SLA.
  7. Timeline and references: proposed plan and two customer references of similar size.

The price template to ask for

LineYear 1Year 2Year 3Year 4Year 5Notes
Subscription or AMC by module and user typeUser counts by year
Platform or base fee
Per-company / per-GSTIN charges
Transaction charges (IRN, e-way bill, documents)Included quota
Hosting (if separate)
Partner support plan
Implementation (fixed or days × rate)Scope reference
Data migrationData sets included
TrainingSessions and users
IntegrationsEach listed
CustomisationsEach listed
Renewal uplift cap% per renewal

Ask vendors to mark any requirement not covered and the price to cover it.

Normalising the replies

  1. Convert to the same period and units: per user per year, for each year.
  2. Align users: apply your user counts by year to each vendor's price per user type.
  3. Apply the uplift: use the contract cap; if there is none, apply a cautious assumption to all vendors equally.
  4. Price the gaps: for each must-have a vendor does not meet, add the cost of an add-on, customisation or workaround.
  5. Separate one-time and recurring: so you can see cash flow as well as totals.
  6. Convert currencies at a cautious rate and add forex charges.
  7. Keep GST out if you can claim credit.

Illustrative normalised comparison (five years, 20 users)

Vendor AVendor BVendor C
Quoted as₹2,400 per user per month₹26,000 per user per year + ₹60,000 platform fee$28 per user per month, billed from abroad
Year-1 recurring, normalised20 × ₹2,400 × 12 = ₹5,76,00020 × ₹26,000 + ₹60,000 = ₹5,80,00020 × $28 × 12 × ₹88 = ₹5,91,360
Uplift cap5%None stated (assume 8%)3% in USD
Five-year recurring (with uplift)₹31,82,764₹34,02,629₹31,39,611 + 2% forex ≈ ₹32,02,403
Implementation₹8,00,000₹6,50,000₹9,50,000
Gap pricingE-way bill add-on ₹25,000 a year = ₹1,25,000NoneJob-work customisation ₹1,50,000
Five-year normalised total₹41,07,764₹40,52,629₹43,02,403

Year-1 recurring costs are within about ₹15,000 of each other, yet the order changes over five years: Vendor C, billed in dollars, is the most expensive once implementation and the gap are added, and Vendor B ends cheapest despite the steepest assumed uplift, because of its lower implementation fee. Small changes, such as Vendor B agreeing to a 5% cap, would widen its lead. You can check each total roughly in the ERP TCO estimator.

Scoring price against fit

Price is one part of the decision. A simple weighted score keeps the discussion honest:

CriterionWeightVendor AVendor BVendor C
Fit to must-haves (demo scores)35%879
Five-year cost (lowest = 10)25%9108
Partner capability and references20%768
Contract terms (uplift, exit, SLA)10%857
Ease of use in trials10%877
Weighted score8.057.358.15

Scores are illustrative. Agree weights before you see prices, so the decision does not get reverse-engineered. Then negotiate with the top two: the contract items in the SaaS contract guide are often easier to win than a lower list price.

Mistakes to avoid

  • Accepting "price on request" lines for modules you will need in year 2.
  • Comparing a vendor's standard edition with another's premium.
  • Ignoring the partner's support plan because it is a separate quote.
  • Letting the vendor define the demo script instead of using your scenarios.
  • Taking reference calls only with customers the vendor chose, without asking about problems.

See also hidden ERP costs.

FAQ

How many vendors should I invite?

Three to five is usually enough for an MSME. More than that makes careful demos impractical.

Should I reveal my budget?

A range can help vendors propose the right scope, but it can also anchor prices upwards. Many buyers share a range only after the first proposals.

Is a public tender process needed?

Not for private businesses. Government bodies and public sector undertakings follow their own procurement rules, such as procurement through GeM where applicable.

Sources

Related guides