How much does a custom ERP cost in Sri Lanka?

Every ERP conversation starts with the same question, and most vendors dodge it. The honest answer is that a custom ERP has no sticker price — but the reasons it doesn't are knowable, and once you understand them you can read any quotation and know exactly what you're paying for.

This is the framework we use to price ERP projects at Acmevia. It applies whether you build with us or with anyone else.

The five things that actually drive the price

1. How many departments the system touches. An ERP that handles finance and inventory is a different animal from one that also runs procurement, production planning, HR, and fleet. Each module isn't just more screens — it's more people to interview, more edge cases, more integrations between modules. Module count is the single biggest cost driver.

2. How messy the current data is. Five years of records living in seventeen spreadsheets (a real number from a manufacturing client) have to be cleaned, de-duplicated, and migrated. Migration is regularly 15–25% of a project's effort, and it's the part most quotes quietly under-scope — which is how "on budget" projects go over.

3. Integrations. Does the ERP need to talk to your bank, your POS, a government tax portal, a courier API, or an existing e-commerce store? Each integration is a small project of its own. List them before you ask anyone for a number.

4. How much of your process is genuinely unusual. Most businesses believe 80% of their workflow is unique. In our experience it's closer to 20% — and that 20% is precisely where custom software earns its keep. A good vendor builds the standard parts fast and spends the budget on the parts that make you you.

5. Who has to use it. Twenty trained back-office staff need a different interface — and a different testing budget — than two hundred field workers on budget Android phones with patchy connections.

The costs nobody quotes you upfront

Ask any vendor these four questions before signing:

• Training and rollout — is it included, and for how many sessions?
• Data migration — scoped as its own line item, or hand-waved?
• Support after go-live — what does the first year of fixes, updates, and "can we add one small thing" actually cost?
• Hosting — whose cloud account, and who pays the bill when you scale?

If a quote is silent on all four, it isn't a low price. It's an incomplete one.

Custom vs. off-the-shelf: the real trade

Off-the-shelf ERPs look cheaper because the licence fee is visible and the adaptation cost is not. You pay in workarounds: spreadsheets on the side, double entry, and staff bending their day around software that wasn't built for it. A custom system costs more on the invoice and less in the years after — one manufacturer we worked with cut order-processing time by 60% because the system finally matched the flow of their factory floor, not the other way round.

The right answer is honestly not always custom. If your operation is genuinely standard, buy standard software. The moment you hear your team say "we do it differently here" more than a few times a day, start pricing custom.

How to get a real number in a week

We scope ERP projects in a fixed sequence: sit with the people who do the work, map what actually happens, write a scope with clear boundaries, and put a fixed price and date against it. You know what you're getting before we write a line of code — and the same eight-step process has delivered every project since.

If you want that number for your operation, book a free demo and bring your messiest spreadsheet. We reply within 24 hours.