How Much Does ERP Software Cost in Sri Lanka?

ERP is not a product in the way a phone is a product. Two businesses of the same size in the same industry can need systems that differ by a factor of three in effort, because one runs a straightforward counter operation and the other runs production batches, three warehouses and a delivery fleet. A published price is therefore either an entry-level figure that will not survive your requirements, or a padded figure that assumes the worst.

What you should expect instead is a written quotation against a defined scope, produced after someone has actually looked at how your business runs. If a vendor gives you a number before that conversation, ask what scope the number covers.

Every ERP quotation you receive is some combination of these five. Understanding them lets you compare quotations that are structured completely differently.

There are two commercial shapes in the Sri Lankan market and they are not comparable line by line.

• Licensed products (local or international) charge per user per month or per year, often with a separate implementation fee. The build cost is low, the running cost never stops, and customisation is billed as consulting.
• Custom builds are quoted once against a scope. The upfront figure is higher, there is no per-seat meter, and the system belongs to your business.

The right comparison is total cost over three to five years, including licences, implementation, customisation requests and support. A licence that looks cheap at ten users looks different at forty.

• Customisation after go-live, when the business discovers what it actually wanted — ask how change requests are priced before you sign.
• Data migration that was scoped as "masters only" and turns out to need three years of transactions.
• Training for staff who joined after the rollout.
• Hosting, backups and SSL if the vendor does not include them.
• Support after the warranty period. Ask for the annual figure in writing at quotation stage, not at renewal.

A quotation that omits support pricing is not cheaper. It is incomplete.

1. Line up the module lists side by side. If one quotation says "inventory" and the other lists eight inventory functions, they are not quoting the same system.
2. Ask both vendors what happens to the price if you add a module in month eight.
3. Ask what the data migration includes, specifically: which masters, how many years, and who cleans the data.
4. Ask for the support cost per year, in writing, and what response time it buys.
5. Ask who owns the source code and the data if you leave.
6. Ask to speak to a customer running the same modules in a similar business.

Any vendor confident in their work will answer all six without hesitation. Reluctance on the last two is the most informative signal you will get.

Rather than starting from a figure, start from what the current problem costs you. Count the hours spent re-typing between systems each month, the value of stock written off after a bad count, the sales lost while someone checks availability by phone, and the cost of a wrong delivery. Businesses are usually surprised how quickly that adds up — and it gives you a defensible ceiling for what a system is worth.

Then scope in phases. A first phase that fixes stock and sales in eight weeks generates the confidence — and often the savings — to fund the second.

We run a free requirement study first, on site, with the people who do the work. That produces a written module list, a phase plan and a fixed price for the scope. Change requests raised later are quoted before they are built, never billed silently. Support after handover is quoted separately so you can weigh it on its own merits.

If your requirement turns out to be a close match for an off-the-shelf product, we will say so. Selling a build that a package would have covered is not a good outcome for either of us.