Due-diligence checklist: how to vet a software company in Thailand
A practical checklist for vetting a Thai software vendor: entity and BOI verification, references, retention, contract terms, and the signals that predict delivery.
Vetting a software company in Thailand takes four passes: verify the entity (registered legal name, and BOI promotion if claimed, checked against official records); verify the track record (references interrogated about behaviour under stress, not satisfaction in general); verify the people (the named lead and team who would actually run your account, and the vendor’s retention record); and verify the terms (IP assignment, NDA, executable exit - stated in writing before signing). A vendor who passes all four rarely fails in delivery; a vendor who resists any of them is answering your question early. Here is the checklist in working order.
Pass 1: Is the company what it claims to be?
Twenty minutes of registry work, done before any deeper investment:
- Legal entity. Get the exact registered name (not the brand) and confirm it in official Thai company records. Match it to the entity that would sign your contract - not a similarly named affiliate or a director personally.
- BOI claim. If the vendor presents itself as BOI-promoted, ask for the promotion reference and verify it through the Board of Investment. Promotion is a legitimacy threshold, not a quality certificate - but an unverifiable claim of it is disqualifying.
- Physical reality. A real office you could visit (and eventually should - on-site days build more alignment than any process document), verifiable phone lines, a domain and email that match the entity.
- History. Years in operation and continuity of identity. A ten-year-old company with the same name and address has survivable habits; a serially renamed one is hiding a trail.
Pass 2: Does the track record survive contact?
Portfolios show the wins. Your job is sampling the distribution:
- Reference calls, not reference letters. Two or three past or current clients, ideally in engagements shaped like yours. Ask about stress, because that is what you are buying insurance against: How did they handle a missed estimate? A defect found after release? Did the team stay stable? Would you start again with them tomorrow?
- Relevant shape, not just relevant logos. A vendor whose longest engagements look like yours (a dedicated team held for years, or complex integrations, or rescues of inherited code) transfers better than one with famous names on unrelated work.
- Engagement longevity. Ask how long their top five client relationships have run. Multi-year relationships are the single hardest credential to fake.
Pass 3: Who exactly would do the work?
Companies don’t write code; people do. The sales team you met will not build your system:
- Named lead. Meet - on a call, in English - the person who would run your account, and ask them technical questions about your project. Their answers are your preview of every future status meeting.
- Seniority mix. What ratio of senior to junior would staff your work? (It should also appear in the quote’s written assumptions.)
- Retention. Ask directly: what is your developer retention, and how long have the people proposed for us been with you? Turnover quietly dominates the real cost of long engagements. Concrete answers matter more than flattering ones.
- Communication under mild stress. Notice reply latency and precision during the sales process - while they are on best behaviour. It only degrades from here.
Pass 4: Do the terms let you trust - and leave?
The contract is where due diligence becomes enforceable. The full treatment is in our contract-clauses guide; the checklist version:
| Item | Pass | Fail |
|---|---|---|
| IP | Assigned to you, explicitly, incl. subcontractors | Vague, licensed, or “on final delivery” |
| NDA | Signed before technical talks | Resisted or watered down |
| Infrastructure | Your repos and accounts on request | Everything lives on vendor systems only |
| Exit | Notice + defined hand-over deliverable | Lock-in, ransom pricing, “reasonable assistance” |
| Quote | Assumptions and seniority mix in writing | A confident total against a vague brief |
| Pilot | Offered at normal rates, same terms | Free pilot, or “no need, trust us” |
The tie-breaker: run the pilot
When two vendors survive all four passes, stop analyzing and start observing: a scoped pilot - one or two developers, one or two months, real work, full contract terms - converts remaining uncertainty into evidence for the price of a few weeks of development. Every failure mode the checklist above screens for is visible in miniature within a month.
In short
- Four passes: entity, track record, people, terms - in that order, cheapest checks first.
- Verify registry facts yourself (legal name, BOI reference); take nothing from a website as final.
- Interrogate references about behaviour under stress; ask vendors for retention numbers and the named lead.
- Insist on written assumptions, assigned IP, and an exit you could execute - before signing, when you still have leverage.
- Finish with a paid pilot at full terms: observed behaviour beats every document in this list.
AD System Asia is built to pass this checklist - BOI-promoted and verifiable, references on request, named leads you interview, IP and exit terms in writing, pilots at normal rates. Run us through it.
Frequently asked questions
How do I verify that a Thai software company is a legitimate business?
Confirm the registered legal entity name and check it against official Thai company records; if the vendor claims BOI promotion, verify the reference through the Board of Investment (boi.go.th). Match the entity that would sign your contract to the one in the registry - ten minutes that filters out the informal end of the market.
What questions should I ask a software vendor's references?
Ask about behaviour under stress, not satisfaction in general: how did the vendor handle a missed estimate or a defect found late? Did the team stay stable? Would you start a new project with them tomorrow? References volunteer praise; you are listening for how problems were surfaced and fixed.
What are the red flags when choosing an offshore software company?
Resistance to naming the people who would run your account, no verifiable legal identity, reluctance to state quote assumptions in writing, contract terms that block your exit, free-pilot offers, and answers that stay in sales language when the questions turn technical.
How important is developer retention when choosing a vendor?
For engagements beyond a few months it is one of the strongest predictors of total cost: every departure takes project knowledge with it. Ask for retention figures and team-tenure examples, and treat a vendor who cannot discuss the topic concretely with caution.
How long should vendor due diligence take?
For a small project: a few days - entity check, one reference call, contract review. For a dedicated team or a multi-year engagement: two to four weeks including reference calls and a scoped pilot. The pilot replaces speculation with observed behaviour and is worth more than any further paperwork.