Every Sri Lankan business owner who has thought about software for more than a week has had some version of the same conversation. One developer friend says “just build it custom — you’ll own it forever.” The next vendor in the room says “just buy our system — it’s 90% there.” Both are wrong, in their own way. The honest answer almost always sits in the middle.
After a decade of building software for Sri Lankan businesses — apparel exporters, FMCG distributors, retail chains, hospitals, schools — this is the framework we actually use to decide.
When off-the-shelf is the obvious answer
For anything that’s a solved problem — meaning your business does it the same way everyone else does — building custom is almost always wasteful. In Sri Lanka, this typically covers:
- Accounting and statutory compliance — VAT, WHT, EPF/ETF. ERPNext, Tally, or QuickBooks each handle this well enough that custom is a hard sell.
- HR and payroll — APIT, EPF, ETF, leave tracking. Standard modules exist and the rules don’t change by company.
- Standard retail POS — if you sell off-the-shelf products to walk-in customers, the workflow is the same as every other shop on Galle Road.
If a packaged product solves the problem at 80% fit, the remaining 20% is usually a process question, not a software question. Adapt the process. Don’t build.
When custom is actually necessary
Custom software earns its cost when the way you do business is the source of your competitive advantage — and a packaged product would force you to do it the way everyone else does. Specific cases we’ve seen:
- Apparel exporters with style-bom-costing logic that no off-the-shelf ERP captures cleanly — multi-level BOMs with embellishment, trim allocation, and order-by-order margin tracking.
- FMCG distributors running route-based sales where the rep’s mobile app needs to handle stock-on-van, on-the-spot pricing tiers, and same-day reconciliation against a depot.
- Hospitals and labs with patient flows that packaged HMIS products don’t model — multi-doctor consultation queues, lab results that feed into pharmacy recommendations, insurance pre-auth flows.
In each of these, the workflow is the business. If software forces a change to the workflow, the business loses what makes it competitive.
The middle ground — where most SMEs land
Most growing businesses in Sri Lanka don’t need a fully custom build. They need an off-the-shelf platform — usually an open-source ERP like ERPNext — with custom modules built on top of it for the two or three things they actually do differently. This gets you the best of both worlds: the heavy plumbing (accounting, inventory, purchasing, HR) is solved by the platform, and the workflows that matter to your business are tailored. (For more on which ERP platform actually fits a Sri Lankan SME, see choosing the right ERP for Sri Lankan businesses.)
We use this hybrid approach for the majority of our clients. The platform handles 70–80% of operations; we build the remaining 20–30% as platform-native customisations. The deployment side of that decision — whether to host on-prem, in regional cloud, or in a hybrid setup — is its own conversation, covered in our piece on cloud migration for Sri Lankan SMEs.
Three questions to decide
Before commissioning anything custom, ask:
- Is this how every business in our industry does it, or is it specifically how we do it? If it’s industry-standard, buy. If it’s your differentiator, build.
- Would changing our process to fit the package be worse than the cost of building? Most of the time, the answer is no. Change the process.
- If we build, can we maintain it five years from now? Custom software is a long commitment. If you can’t fund ongoing development, you’ll be stuck on a frozen version while the rest of the world moves on.
If you’re trying to decide between buying and building, we’re happy to give you a candid view in 30 minutes — usually we can tell within the first conversation whether the problem you’re solving deserves custom code or just a better-configured package. Get in touch and we’ll set up a call.