Choosing an IT Vendor in Laos: Questions to Ask Every Provider, Including Us

The vendor matters more than the brand

The same equipment installed by two different teams can turn out worlds apart. Most of the problems we get called in to fix aren't failed hardware. They're poor design, insecure configuration, no documentation at all, and a previous vendor who no longer picks up the phone. This checklist works for every vendor. Including us.

1. Who will actually do the work?

• Ask for the names and roles of the lead engineers who will be on site, not just the company name.
• Does the team hold manufacturer certifications for what they're proposing? Ask to see them, and check.
• Ask for 2–3 references with similar projects, and phone them yourself.
• Have they worked somewhere like yours: a mine, a hotel, a bank, multiple sites?
• Do they use subcontractors? If so, who answers for the quality?

2. Where does the equipment come from, and does the warranty really work?

Most IT equipment in Laos comes in via Thailand or other countries. That's fine, but it makes these questions matter:

• Is it from a legitimate distribution channel? Ask for invoices and serial numbers.
• Check the serials on the manufacturer's own website: which region is the warranty registered to, and is it valid in Laos? Some models are country-specific and their warranty doesn't cross borders.
• If something fails, where does it go for repair and how many days, including customs? Is there a loan unit in the meantime?
• Are licences and subscriptions (firewall, antivirus, cloud) registered in your organisation's name?
• Is it a current model, or close to end-of-life?

3. Design and quotation

Did they visit the site before quoting? Is the quote itemised: models, quantities, licence terms, labour, what's in and what's out? Is there a design (network diagram, camera layout), not just a product list? And ask straight out: why this model and not a cheaper one? A good engineer can answer in two sentences.

4. Handover day: what you should receive

Put it in the contract that at handover you get:

5. After-sales and SLA

• How do you report a problem: phone, WhatsApp, email, a ticket system? What are the support hours?
• Response time and resolution time by severity, written as numbers, not "as soon as possible".
• Will they come to provincial sites, and how is travel charged? How many days to Luang Prabang or Savannakhet?
• What does preventive maintenance cover, and how often?
• Which languages can they work in: Lao, Thai, English? It matters with mixed teams.

6. Security and access to your systems

How does the vendor reach your systems remotely? Separate named accounts with MFA? Do they change default passwords and update firmware before handover? If the contract ends, how do access and data come back to you?

If the vendor offers cybersecurity services such as SOC monitoring, ask who actually watches the alerts, whether anyone is on duty outside office hours, how many minutes they take to respond, and what they are allowed to do in your systems. Ask for a sample monthly report with client details removed.

Red flags

1. A price far below everyone else, with no explanation of why.
2. Refusing to hand over admin passwords or configuration files.
3. No site visit, but a quote arrives the same day.
4. Serials that can't be verified, or warranties registered in another country.
5. Claims of a special relationship with a brand that can't be backed up.

Scoring fairly

Use a weighted scorecard. Example weights: skills 25%, design 20%, after-sales 25%, 3–5 year total cost 20%, documentation 10%. Score each area 1–5 and multiply. Note that price carries only a fifth of the weight.

Worked example: scoring three bids

A trading company with 70 staff asked three vendors to quote the same scope: a new firewall, 12 access points, two switches and a backup NAS. Using the weights above:

Vendor B had the lowest price, but no site visit, a product list instead of a design, and no written response times. Vendor C was strong technically but had nobody based in Laos, so a failed switch at night meant waiting for the next flight. Vendor A cost more up front and won on the areas that decide how the next five years go. Your weights may differ. A mine with a single site three hours from town might give after-sales 35%. The point is to agree the weights before you open the quotes, so the cheapest number on the page doesn't decide by default.

Foreign and Thai-based vendors

Many IT vendors serving Laos, including us as specialists from Thailand, bring engineers, stock and distributor relationships from across the border. That can be a real strength: wider product choice, spare parts close by, and engineers who have done the same job many times. It also raises fair questions. Ask who is on the ground in Laos day to day, how many hours it takes to get an engineer to your site, whether staff speak Lao, and how spare parts cross the border when something fails. A good answer has names and hours in it.

Common mistakes when buying

• Letting the vendor own the cloud account. The firewall or Wi-Fi dashboard is registered to the vendor's email. When the relationship ends, so does your access.
• No acceptance test. Pay the final instalment only after you have checked the system works as agreed.
• Warranty that starts at shipment, not installation. Equipment that sat in a warehouse for four months has already used part of its warranty. Check the start date.
• Paying everything up front. Milestone payments, for example 30% at order, 50% at delivery and 20% after acceptance, keep everyone motivated.
• Buying licences for one year only. Security and cloud-managed devices can stop working or lose features when a subscription lapses. Budget the renewal in year two.

Acceptance before the final payment

Before you sign off, walk the site with the vendor's lead engineer. Test Wi-Fi in the far corners, pull one power cable to check that UPS shutdown works, restore one file from backup, and confirm you can log in to every device with your own admin account. Write down anything that fails and agree a date to fix it. Our IT asset management page explains how to keep the asset and warranty list current after handover.

Local conditions to raise

Ask how the design copes with power cuts and voltage swings, and whether UPS units and surge protection are in the quote or left for later. Ask how the vendor reaches provincial sites in the rainy season, when some roads close for days. And ask whether manuals and training can be given in Lao, so the people who use the system every day can actually follow them.

What we recommend

Compare at least 2–3 vendors against the same scope of work, or you're comparing mangoes with tamarinds. Weigh local service and on-site response as heavily as price. Make sure your organisation owns every account, licence and document. And if you can, start with a small project to see whether you work well together.

Comparing vendors right now? Send us your scope or a quote you already have through our contact page. We will answer every question on this list in writing, the awkward ones included, so you can set our answers beside those of the other vendors.