When is off-the-shelf software the right choice?

When the process is standard across companies, such as accounting, payroll, email, file storage and basic HR, a mature product is cheaper, better supported and already known to your staff and auditors.

When is custom software the right choice?

When the process is what makes the company what it is, such as field capture, job-to-document workflows and the company's own document formats, and you would not change the process to fit a product.

Is an ERP a middle ground?

An ERP or low-code platform configured by consultants suits a large company with a standard core and few variations. For a mid-size company whose value is in the variations, it costs the timeline of a build without the fit.

Custom software or off-the-shelf? A guide for established Malaysian companies

Buy it when the process is standard

Accounting, payroll, email, file storage and video calls are standard. A Malaysian company gains nothing from a custom accounting system: the rules are set by LHDN and the auditors, the products are mature, and a local accountant already knows them. The same is true of a CRM for a straightforward sales team and of an HR system for leave and claims. If a process looks the same in your company as in the one next door, buy the product, and spend the money you save on the processes that do not.

Build it when the process is the business

The processes worth custom software are the ones that make the company what it is: how field teams capture work at the site, how a job moves from request to signed document, how the company's own documents are produced, and how a manager knows where everything stands. These are rarely standard. An engineering consultancy's site forms are not an insurer's claims, and a packaged product forces one of them to work like the other. When the process is the business, the system should follow the process, not the other way round.

The middle: configure a platform

Between buying and building sits a third option that packaged vendors sell as configuration. A general-purpose platform, an ERP or a low-code tool, is bent toward your process by consultants. This is where the nine-month timelines and the large integrator invoices come from, and where a company ends up with a system that is neither the product nor its own. It is the right choice for a large company with a standard core and a small number of variations. It is the wrong choice for a mid-size company whose value is in the variations.

Five questions that decide it

Does the process look the same in every company in your industry? If yes, buy.
Would you change the process to fit a product? If you would not, build.
Does the process end in a document in your own format, signed by your own people? Custom systems produce that document; packaged products produce theirs.
Do the people doing the work carry phones with no signal at the site? Packaged products rarely handle offline capture well; a custom system is built for it.
Who will change the system when the process changes next year? A product changes on the vendor's schedule. A custom system changes on yours.

What custom should cost you in time

Custom software has a reputation for long timelines and open-ended budgets, and it has earned it. Our answer is in the commit history: recent modules went live in one day, one week and seven build days, because each was added to a platform already running in production rather than started from nothing. The numbers are in How long does custom software take to build?. Ask any developer you are considering for the same figures, from real projects, before you sign.

A way to decide without deciding

If the answer is not obvious, do not buy a whole system either way. Pick the one process that hurts most and have it built as a first version your staff use for a few weeks. What they do with it will settle the question faster than a tender. For the right company and process, we build that first version at no cost.