Business · Strategy

Build or buy: an honest guide to custom software for Malaysian businesses

Custom software is not always the answer, and we say so to prospective clients regularly. A framework for deciding, with real price ranges and timelines.

Pikabyte Engineering 4 min read

RM30k to RM150k

the range most of our custom software projects fall into

The first thing we tell a prospective client is often that they may not need us. Off-the-shelf software is cheaper, available today, and maintained by someone else. If a subscription product fits how your business works, buy it.

Custom software earns its cost in a specific set of circumstances. Here is how to tell which side of the line you are on.

Buy when the process is ordinary

Accounting, payroll, email, basic CRM, standard e-commerce. Thousands of companies do these the same way, and the products are mature. Building your own is almost always a mistake. Your process here is not a competitive advantage, and compliance changes such as e-invoicing are the vendor’s problem to keep up with.

Buy when:

  • your process matches the product’s assumptions without workarounds
  • the per-user cost is acceptable at your expected headcount
  • the vendor is established and you can export your data

Build when the process is the business

Custom software pays when the way you work is specific to you and central to what you sell.

A law firm that processes hundreds of banking recovery accounts a month, each needing the right document at the right stage with interest calculated to the cent. A manufacturer whose customers and authorities need a verifiable test certificate for every product shipped. An education company that must produce syllabus-aligned content in two languages with expert review.

None of those could be bought. Each is now a platform we run.

Signs you are in this territory:

  • You have bent a generic product until it broke. Custom fields, exports to Excel, a macro, a person whose job is the workaround.
  • The spreadsheet has become infrastructure. One file, one person who understands it, no audit trail.
  • Two or more systems must agree and do not. Staff re-enter data between them.
  • The process has rules a regulator, bank or customer checks. You need to prove it was followed.
  • Per-user pricing punishes growth. Fifty factory workers who each need thirty seconds a day are expensive on a per-seat subscription.

The middle path

Often the answer is both. Buy the commodity system, and build the piece that is unique, connected to it.

Our litigation platform does not replace the firm’s accounting software. It creates invoices in it. The firm bought accounting and built litigation operations.

What it costs

Most of our projects fall between RM30,000 and RM150,000, depending on scope and complexity. A medium-complexity system typically takes around eight weeks. Our median from kickoff to production across delivered systems is six weeks.

Ongoing, expect hosting and maintenance. A well-designed system for a small or medium business runs on modest cloud infrastructure, in an account you own.

Compare that honestly against the alternative:

  • Subscription cost over five years at the headcount you expect, not the headcount you have.
  • The cost of the workaround. Hours a week of manual work, multiplied by a loaded hourly rate, multiplied by fifty weeks.
  • The cost of errors. A wrong document, a missed deadline, an unverifiable certificate.

Clients commonly recover ten to twenty hours of manual work a week. At that rate most projects pay back in six to eighteen months. Our free automation readiness assessment includes a worksheet for the calculation.

How to reduce the risk of building

Custom projects fail in predictable ways. You can design most of them out.

Start small. Build the one workflow that hurts most. Our clients usually begin with a single system and expand once it has proved itself.

See working software before you sign. We build a working demo before we send a proposal or quotation, so a client can click through it and tell us what we got wrong. Whoever you work with, ask for the same. A demo you can use tells you more than any slide.

Own everything. Source code, data and the cloud account in your company’s name. If the relationship ends, you keep the system.

Ask about tests and deployment. A system with automated tests and a deploy pipeline can be changed safely for years. One without them becomes the next legacy problem.

Talk to the people who will build it. If you only meet a salesperson before signing, expect to be surprised later.

A five-question test

  1. Does an existing product fit without workarounds? Buy.
  2. Is this process a reason customers choose you? Lean build.
  3. Is someone’s full-time job compensating for the software? Lean build.
  4. Do you need to prove to an outsider that the process was followed? Lean build.
  5. Would it pay back within eighteen months on saved hours alone? Build.

If you are unsure, ask. We will tell you if a subscription would serve you better.

Written by

Pikabyte Engineering

Pikabyte builds custom business systems, applied AI and secure cloud infrastructure from Malaysia. Talk to us.

Start a conversation

Want this applied to your business?

Tell us what is slowing the business down. You will talk to an engineer, not a salesperson, and get a straight answer on whether software is the right fix.