Skip to content

How to choose a software development company in Malaysia

Seven steps before you sign: check you need custom software, set a budget, write a brief, check the company, compare quotes and keep the code yours.

Rosaan Ramasamy · 7 min read

In short

Make sure you need custom software at all. Set a budget range, with a reserve on top. Decide who builds it and who makes the technical calls. Write a one-page brief and send the same one to everyone. Check the company: a live system, a client you can speak to, the SSM profile. Compare what each quote leaves out and how changes are paid for. Before you sign, put the code, hosting and accounts in your company’s name, and agree how the work is accepted and supported.

Most business owners only buy custom software once or twice. The companies selling it do this every week. That gap is where most bad projects start: a quote nobody could compare, a scope nobody wrote down, or code that turns out to sit in someone else’s account.

Here’s the order we’d go about it, whoever you end up hiring. Each step is short and links to a longer article if you want the detail.

1. Make sure you need custom software

Plenty of businesses don’t. An accounting, POS or HR package, set up properly, covers most standard work for a lot less money. Custom software earns its cost when the way you work is different enough that a package forces your staff into workarounds and spreadsheets.

So write down the work first: who does what, and where it breaks today. Then compare buying, configuring and building against that list, not against feature pages. Custom software or an existing product? walks through it. If you already have a system, the question is whether to improve it or replace it. If your accounting package is the thing straining, start with when AutoCount or SQL Account stops fitting.

2. Set a budget range before you call anyone

Most custom business systems in Malaysia cost RM15,000 to RM150,000 to build, and another 15 to 25% of that every year to keep running. Our cost guide has the ranges, and apps have their own.

Then keep a reserve on top. In a study of 1,471 IT projects, the average cost overrun was 27%. That isn’t the worrying part. One in six went over by 200% on average, and ran almost 70% late.⁠[1] Most of those projects were large and in the public sector, but the lesson carries: the risk is in the bad tail, not the average. The same researchers advise breaking big projects into smaller ones with limits on size, complexity and duration. For you, that means a small first release you can judge before committing to the rest.

3. Decide who builds it, and who makes the technical calls

  • A freelancer suits a small job with a clear end.
  • Your own developer suits steady work, if someone can direct them.
  • A software house suits a system your operations run on, or one that will keep changing.

Each one goes wrong in its own, predictable way, so pick the one whose risk you can manage.

Whichever you pick, someone has to own the technical decisions: how the system is built, how it’s kept secure, what gets built first. If nobody in your company can, you either hire for it or pay a team that takes it on.

4. Write a one-page brief

This is the step people skip, and the one that matters most. In PMI’s 2014 study, 47% of projects that missed their goals did so because of inaccurate requirements management.⁠[2]

The brief doesn’t need to be technical. Who will use the system, the workflows it must handle, your top three priorities, the systems it connects to, and how you’ll decide it’s done. Add your budget range. Then send the same brief to every company, so the quotes you get back are pricing the same thing. What to prepare before asking for a quotation has a copyable version, and planning an integration helps if other systems are involved.

5. Check the company, not just the quote

A quote tells you what they’ll charge. It doesn’t tell you whether they can deliver. Five checks that do:

  • Ask to see a live system they built and still look after. Screenshots in a portfolio are easy. A system in daily use, with someone still maintaining it, is harder to fake.
  • Ask to speak to a client, and read their reviews. Most buyers already do this: in TrustRadius’s 2026 survey of 1,862 technology buyers, 74% read reviews and 53% spoke to a peer.⁠[3] Those buyers were choosing software products, not custom builds, but the habit is worth copying. Many Malaysian clients won’t write public reviews, so a thin review page isn’t a red flag on its own. A company that can show you nothing at all is.
  • Ask who you’ll deal with day to day, by name, and who checks their work. The senior person in the sales meeting is often not the one building your system.
  • Look the company up on SSM. A company profile from SSM e-Info costs RM15.40 and shows when it was registered, its status, its directors and shareholders, and a summary of its financials.⁠[4] Check that the company on the contract is the one you met.
  • Notice how they quote. A good company asks questions back before it sends a price. One that prices a WhatsApp message in an hour hasn’t understood the work yet. And a company that tells you part of it doesn’t need them is one worth trusting.

6. Compare quotes, and how you’ll pay

Put the quotes side by side against your brief. A much cheaper one is rarely the same work. It usually leaves out testing, deployment, documents or support after launch. Ask every company what’s written down as not included, and how changes are priced once work starts. How to compare the quotes you get has the full list.

Then decide how you’ll pay. A fixed price suits a scope that’s written down, signed off by one person, and won’t change much after launch. Monthly suits work that will keep moving. Requirements usually do change once staff start using a system, and research links that change to cost and schedule overruns.⁠[5] Why software requirements keep changing explains how each model handles it.

Whichever you choose, ask to see working software every few weeks, not just at the end. In a study of 1,002 projects, the more a project used agile methods (short cycles, adjusting as it went), the more often it met its cost and time targets, and most of all what the customer wanted. Those projects didn’t plan less up front.⁠[6] A fixed-price project can be run this way too, so ask how they’ll do it.

7. Before you sign: ownership, acceptance and support

Keep the accounts in your company’s name: the code repository, hosting, domain and app store accounts. Who should own the code, hosting and accounts? has the list.

Read the IP clause. Under the Copyright Act 1987, copyright in work you commission is treated as transferred to you, unless the contract excludes or limits that.⁠[7] So the law starts on your side, and the contract can take it away. This isn’t legal advice; for a large contract, have a lawyer read it.

Agree how the work is accepted, in writing, before it starts. Then agree how long bugs are fixed free after go-live, what maintenance covers and what it costs. What happens after go-live and what a maintenance contract should cover go through both.

Agree what happens if you part ways: what you get, and how the handover works.

Be wary of a firm start or finish date given before anyone has seen the work. How fast can you start? explains what actually decides it.

Once the work starts

Three questions tell you whether it’s paying off, under any contract. How do you know your software developer is doing a good job? goes through them.

If you’re replacing a vendor

The same steps apply, with two more at the start. Find out who controls the code, accounts and data today, and get the system reviewed before anyone decides to rebuild it. Taking over software from another vendor covers both.

The checklist

  1. We know what the system must do, and a package won’t do it.
  2. We have a budget range, with a reserve on top.
  3. We know who builds it, and who makes the technical calls.
  4. Every company got the same one-page brief.
  5. We’ve seen a live system, spoken to a client and checked SSM.
  6. We know what each quote leaves out, and how changes are paid for.
  7. The code and accounts will be in our name, and acceptance, support and exit are written down.

Common questions

How do I check if a software company in Malaysia is legitimate?

Buy its company profile on SSM e-Info for RM15.40. It shows the registration date, status, directors and shareholders.⁠[4] Then ask to see a live system they look after, and to speak to one of their clients.

Should I pick the cheapest quote?

Only if it’s pricing the same work. Ask what each quote leaves out and how changes are priced. A low quote with expensive changes often ends up costing more.

Who owns the code if I pay for it?

By default under Malaysian law, copyright in commissioned work passes to the client who commissioned it, but the contract can exclude or limit that.⁠[7] Read the IP clause, and keep the code repository and accounts in your company’s name either way.

How many quotes should I get?

Two or three is enough, as long as each company got the same brief. More than that and you spend your time comparing quotes instead of checking companies.

Is Antdragon right for you?

We build and run business systems for Malaysian companies. If the system runs your daily operations and will keep changing, that’s Managed Delivery, from RM13,000 a month, month to month. If the scope is written and fixed, a build can be a Custom Project, from RM30,000.

If your budget is below that, a good freelancer, a smaller firm or a package is likely the better fit, and we’d rather say so now.

Sources

Company guides are published by software companies about their own market, not independent surveys. Treat their figures as a rough guide.

  1. 1.

    Research

    Why Your IT Project May Be Riskier than You Think (opens in a new tab)

    Bent Flyvbjerg and Alexander Budzier, Harvard Business Review, 2011. Checked 1 November 2026.

  2. 2.
  3. 3.

    Company guide

    Trust More, Verify Everything: what the 2026 B2B Buying Disconnect report says (opens in a new tab)

    TrustRadius, via HG Insights, 2026. Checked 1 November 2026.

  4. 4.

    Official

    Company and business information search (opens in a new tab)

    SSM e-Info, authorised portal of the Companies Commission of Malaysia. Checked 1 November 2026.

  5. 5.

    Research

    A Study of the Impact of Requirements Volatility on Software Project Performance (opens in a new tab)

    Didar Zowghi and Nur Nurmuliani, Asia-Pacific Software Engineering Conference (APSEC), 2002. Checked 12 October 2026.

  6. 6.

    Research

    Does Agile work? A quantitative analysis of agile project success (opens in a new tab)

    Pedro Serrador and Jeffrey K. Pinto, International Journal of Project Management, 2015. Checked 1 November 2026.

Rosaan Ramasamy

Founder and Managing Director, Antdragon

Rosaan started Antdragon in 2020 to be the team that stays accountable once software goes live, and works with business owners on the systems they rely on every day.

Filed under Planning new software

ShareWhatsAppLinkedIn