Business

Due Diligence on an Indonesian Software Firm: A Checklist for Overseas Buyers

November 11, 2026 · 8 min read · Etzal Group Team

A logistics company in Singapore receives a polished proposal from a software firm in Jakarta. The price is a third of local quotations. The portfolio is impressive and the video calls go well. Before signing, the operations director asks a simple question that nobody can answer: how do we know? Who are these people, does the company exist as described, did they build what the portfolio shows, and what happens if it goes wrong? Checking an Indonesian software firm, or any overseas partner, is a few days of structured work. It is far cheaper than finding out later.

Six areas to check

1. Legal standing

Confirm that the company exists and that you are contracting with the right entity.

Ask for:

  • Deed of establishment and any amendments, showing the company name, directors and shareholders.
  • NIB, the business identification number issued through Indonesia's licensing system.
  • NPWP, the tax identification number.
  • Company domicile: the registered address.
  • Who is authorised to sign on the company's behalf.

Check that:

  • The entity name on the proposal, the contract, the invoice and the bank account are the same. A request to pay a personal account, or a different company, needs a clear explanation.
  • The directors named in the documents are people you have met or can meet.
  • The company has existed for as long as it says.

Most Indonesian companies you will deal with are a PT, a limited liability company. A legitimate firm provides these documents without hesitation.

2. People

You are buying the work of specific people.

  • Who will work on your project? Names, roles, experience, and the share of their time.
  • Are they employees? Or subcontractors and freelancers brought in for your project? Neither is wrong, but you should know.
  • Can you interview them? The lead developer and the project manager at least.
  • How long have they been with the firm?
  • What is the firm's size and turnover of staff?
  • English level of the people you will work with daily, not only the salesperson.

Ask for a video walk-through of the office during working hours. It takes five minutes and tells you a great deal.

3. Delivery evidence

A portfolio shows what a firm says it built. Verify it.

  • References. Two or three clients, with at least one from a project similar to yours. Speak to them yourself, by video.
  • Live systems. Ask to see something running in production, with the client's permission, not only screenshots.
  • Their role. For each portfolio item, what exactly did they do? The whole system, the front end only, a few months of maintenance?
  • A case that went badly. Every firm has one. How they describe it is revealing.
  • Code or technical samples. Where confidentiality allows, a look at code quality, tests and documentation by someone technical on your side.

Questions for references:

  • What did they build for you, and is it still in use?
  • Was it delivered on time and on budget? If not, why?
  • What went wrong, and how did they respond?
  • Who did you actually work with?
  • How did they handle changes?
  • Would you hire them again? What would you do differently?

The pause before the answer to the last question is informative.

4. Process and communication

  • How do they work? Sprints, demonstrations, how often you see working software.
  • Who is your daily contact, and what are their hours?
  • What tools: task tracking, repository, communication. Will you have access?
  • How are requirements and changes documented?
  • How do they test?
  • Whose repository holds the code? It should be yours, or you should have full access from the first day.

Notice how they have communicated so far. Proposals that arrive when promised and questions that show understanding predict the project better than any process diagram.

5. Security and data protection

  • Access control: who can reach your code and data, and how is access removed when someone leaves?
  • Devices: company-managed or personal?
  • Environments: will they use real production data in development? They should not need to.
  • Secrets: how are credentials stored?
  • Certifications, if they claim any, with the certificate and its scope.
  • Personal data. If your customers' or employees' personal data will be accessed from Indonesia, both your own data protection law and Indonesia's personal data protection law are relevant. Singapore's PDPA, for example, sets conditions on transferring personal data overseas. Settle the roles, safeguards and breach notification in the contract, with advice.

6. Financial stability

A firm that runs out of money mid-project is a failed project.

  • How long have they operated?
  • How many active clients? A firm dependent on one client is fragile.
  • Payment terms they ask for. A very large upfront payment can indicate cash pressure.
  • Do they pay their people on time? Hard to ask directly. High staff turnover is the usual sign.

Contract terms that matter across borders

Take legal advice in your own jurisdiction. The points to cover:

  • Governing law and dispute resolution. Many cross-border contracts choose arbitration in a neutral venue, because an arbitration award is generally easier to enforce abroad than a court judgment. Singapore is a common choice in the region.
  • Language. Indonesian law has requirements on the use of the Indonesian language in agreements involving Indonesian parties. In practice, such contracts are often prepared in two languages. Ask your lawyer how this applies to you.
  • Intellectual property. A clear assignment of all rights in the work to you on payment, including from the firm's employees and subcontractors.
  • Confidentiality, binding the firm and the individuals.
  • Data protection terms as above.
  • Payment tied to accepted milestones, in an agreed currency.
  • Tax. Cross-border service payments can involve withholding tax and treaty relief. Ask your accountant before agreeing the price as gross or net.
  • Termination and handover: what you receive if the contract ends early.
  • Non-solicitation, if you might later hire their staff, or they yours.

Start small

The best due diligence is a small real project.

  • A paid discovery or a two to four week pilot on a self-contained piece of work.
  • Judge: quality of what was delivered, communication, how they handled something unclear, whether estimates were met.
  • Then decide on the larger engagement.

A firm that resists a small start, and wants a large commitment first, has told you something.

Working with a team in Indonesia

A few practical points.

  • Time zones. Western Indonesia Time is UTC plus 7. Singapore is one hour ahead. Agree fixed overlap hours and a regular meeting slot.
  • Public holidays. Indonesia has a number of national and religious holidays, and the period around Eid is a long break when little gets done. Ask for the year's calendar and plan releases around it.
  • Communication style. Teams may be reluctant to say no or to report bad news directly to a client. Ask open questions, invite problems explicitly, and reward early warnings.
  • Visit. A few days in person at the start changes the relationship.
  • One point of contact on each side.

Warning signs

  • Reluctance to provide company documents.
  • Payment to an account that does not match the contracting entity.
  • No named team.
  • References that cannot be reached, or are all friends of the founder.
  • A portfolio of famous logos with no explanation of the firm's role.
  • A price far below every other quotation, with no reason given.
  • Pressure to sign quickly.
  • Promises that everything is possible.
  • Unwillingness to do a small paid trial.
  • Code kept in the vendor's repository only.

One sign deserves a question. Several deserve a different vendor.

A one-week plan

  • Day 1. Request company documents, team list and references.
  • Day 2. Review documents. Video walk-through of the office.
  • Day 3. Interview the proposed lead developer and project manager.
  • Day 4. Call two references.
  • Day 5. Technical review of a sample and of their process. Draft terms with your lawyer.
  • Then: a small paid pilot.

We are an Indonesian firm ourselves, and we would rather be checked thoroughly than chosen on a presentation. We provide our company documents, named team members and client references on request, and we usually begin with a fixed-price discovery. See how we work in Enterprise Software, or contact us.

Summary

Verify six things before hiring an overseas software partner: that the legal entity exists and matches the contract and bank account, who the people are, what they have really delivered, how they work, how they protect code and data, and whether they are financially stable. Speak to references yourself. Cover governing law, language, intellectual property, data, tax and handover in the contract with proper advice. Then begin with a small paid project before committing to a large one.

Frequently asked questions

How can I verify that an Indonesian software company is legitimate?

Ask for its legal entity documents: the deed of establishment, the business identification number known as NIB, and its tax number. Check that the entity name on the contract matches those documents and the bank account you will pay. Then verify the people: named staff with public professional profiles, an office you can see on a video walk-through, and client references you speak to yourself.

What are the main risks of outsourcing software development overseas?

Misunderstood requirements, less visibility of who is actually doing the work, intellectual property and data protection across two legal systems, and difficulty enforcing a contract abroad. Each is manageable: clear acceptance criteria, named team members, proper contract terms on ownership and data, staged payments and a small paid trial before a large commitment.

Is the time difference with Indonesia a problem?

Western Indonesia Time is UTC plus 7, one hour behind Singapore and seven hours ahead of London in winter. For Singapore and Australia the working days overlap almost fully. For Europe there are a few shared hours in the morning. For the Americas there is little overlap, so the work depends on written communication and agreed handover times.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

Free consultation

Not sure where to start? We will map the right system for your business, free.