IT Support for Chinese Companies Expanding to Southeast Asia: A Local-Delivery Guide for MSPs

IT support for Chinese companies expanding to Southeast Asia usually lands on the MSP that already serves them at home, and that MSP does not need to hire in four countries; it needs to line up a local delivery partner. The MSP keeps the client, the contract and the remote layer. The partner supplies hands, language and physical presence in Singapore, Malaysia, Indonesia and Thailand under the MSP's own process. What you must pin down is coverage by city, delivery pattern, lead time and a per-country price you can resell.

Who is the MSP in this story, and why do its clients' overseas offices land on its desk?

Picture a mid-sized IT services company in a Chinese city. Call it the MSP. For years it has looked after the IT of a handful of large platform and manufacturing clients: desktops, networks, cloud tenants, a service desk that speaks the client's language and an on-site team that knows the client's floor plan. The relationship is built on trust, on a single contract and on one phone number to call.

Then the clients go overseas. In Chinese business circles the word is 出海, literally "going out to sea", and it describes a company opening a sales office in Singapore, a plant or warehouse in Malaysia, a development team in Indonesia, a service hub in Thailand. The client does not start a new IT relationship in each country. It phones the MSP it already trusts and says: the new offices open in the second half of the year, please take care of IT there as well.

At that moment the MSP has won the scope and has nobody outside China. That is the situation this article addresses. In the buyers' own shorthand, the requirement is 海外现地运维, which we render as overseas local operations support, and the words that follow it in almost every brief are 驻场 (a resident engineer at the site), 每周固定 (fixed days each week) and 按上门工时 (billed by attended hours).

A clear note before going further. The MSP described here is an illustrative composite, not a named company. It is built from the shape of a request that Chinese IT services firms meet again and again, and every figure about Brocent below is a published number that we cite with its source, never a figure invented to suit the story.

One more boundary: this is not an article about Mainland China. The work happens in Singapore, Malaysia, Indonesia and Thailand, and the buyer happens to be a Chinese company that wants to resell it. If you are an end client weighing a provider for your own overseas offices, the same arithmetic applies, but the contract questions are different, and our guide to vetting a local IT delivery partner is the better starting point.

Why are Singapore, Malaysia, Indonesia and Thailand four different problems?

It is tempting to treat Southeast Asia as one territory and ask for one number. The published rate card does not support that, and neither does experience. Each of the four countries differs on at least three axes: what an engineer-hour costs, which languages a site engineer needs, and how quickly someone can be on a client's floor.

What does the published rate card say about the four countries?

Brocent publishes indicative on-site dispatch rates by country on its dispatch and on-site rates page. The basis is Level 1 end-user-computing support, next-business-day, 9×5, in US dollars, tax exclusive, city centre, from the 2026 H2 standard price book. As published on 2026-10-05, the four rows read:

• Singapore: USD 85 for the first hour, USD 78 for each additional hour.
• Malaysia: USD 65 for the first hour, USD 59 for each additional hour.
• Indonesia: USD 46 for the first hour, USD 39 for each additional hour.
• Thailand: USD 65 for the first hour, USD 59 for each additional hour.

Two details matter to a reseller. The first-hour rate is a minimum that includes travel within the metro or city-centre area, so a one-hour job costs the same as a three-quarter-hour job. And these are described as fully loaded, billed after the job with no prepayment, and falling at higher volumes, which is exactly the lever an MSP bringing several countries at once should ask about.

Dedicated, full-time engineers are a different table. Monthly rates exist for Singapore (USD 4,160) and Malaysia (USD 1,820), described as a dedicated engineer, entry level, no backfill. Indonesia and Thailand have dispatch rates only. There is no published monthly figure for either, and we will not extrapolate one from the other two, because a price made up from a neighbour's numbers is exactly the kind of quote that embarrasses a reseller later.

Where does Brocent actually have people?

Presence claims should be as careful as price claims. Brocent has been headquartered in Singapore since 2021 (founded 2007) and has had a Hong Kong office since 2016. On the Southeast Asia side, its coverage page says Singapore, Malaysia and Thailand are served through direct Brocent teams, with Indonesia served through a certified ASEAN partner network, all coordinated from Singapore. The Malaysia page describes a Kuala Lumpur service satellite site, and the Thailand page describes a Bangkok-based team serving since 2018.

So for the MSP the four countries are not uniform even before price. Three are direct-team markets; Indonesia is delivered through a partner network under Brocent's coordination. That does not make Indonesia worse, but it changes what you ask in diligence, such as who the contracting party is for a visit and how the engineer is vetted.

Why do languages and lead times differ by country?

An engineer who works on a client's floor in Bangkok needs Thai for reception, building management and the local ISP. An engineer in Jakarta needs Bahasa Indonesia for the same reasons. In Singapore and Malaysia English carries most daily work, while Mandarin is often an advantage when the client's own staff are Chinese-speaking. What the client's people need is a scoping question for each site, not a country default. Brocent's FTE description speaks of bilingual engineers, but a published statement that a given country always has a Mandarin-speaking engineer does not exist, so ask for it per role and get it in writing.

Lead time depends on what is being started: a dispatch arrangement that only needs a service request channel, or a resident engineer who needs to be assigned, cleared for the building and onboarded to your tools. We come back to lead time below.

What are the three delivery patterns, in the buyer's own words?

The brief that arrives on an MSP's desk almost always names one of three patterns. They are not mutually exclusive, and a sensible overseas programme usually mixes them by country and by site size.

驻场: a resident engineer at the client's site

Resident means a named person at the client's premises on agreed days, often every working day, who becomes part of the daily rhythm of the office. This is the pattern clients picture first because it resembles what the MSP does in China. It is also the most expensive per hour of actual work, since you pay for a full month whether the printers behave or not.

Brocent describes its full-time onsite IT support as a dedicated engineer embedded in your office, backed by Brocent's technical team, with leave cover from a pool of trained engineers and flexible full-time, part-time or rotation models. On the rate card, a monthly figure is published for Singapore and Malaysia only.

每周固定: fixed days each week

The middle option is a fixed visit schedule, for example one morning a week at each site. It suits small offices that produce a steady trickle of requests: onboarding a new joiner, replacing a monitor, checking the switch cupboard, collecting the week's small jobs in one visit. Brocent's field dispatch service lists scheduled preventive maintenance visits, monthly or quarterly, as one of its included features. A weekly cadence is a scoping conversation on top of that rather than a published product, so treat it as something to specify, not something to assume.

按上门工时: billed by attended hours

The third pattern is on-demand dispatch: a ticket arrives from the MSP's service desk, an engineer attends, a signed report records the start and end times, and the visit is billed at the published hourly rate. Brocent's field IT dispatch page describes requests submitted through its helpdesk or an ITSM platform, a 4-hour emergency window or next-business-day attendance, and coverage in more than 100 countries through a single contract. It is the cheapest pattern when the physical work is occasional, and it leaves the MSP with a clean cost line that maps to the client's ticket history.

"Two or three people per country": is redundancy the real cost driver?

A sentence heard in almost every scoping call is: "roughly two or three people per country should be enough." Take that as a planning assumption, not a fact. It deserves a closer look because it is where overseas programmes quietly stop being cheap.

Why two or three? One engineer is a single point of failure. They take annual leave, fall ill, attend a public holiday that differs from the client's, and sometimes resign. The client's contract with the MSP nearly always promises something like continuity, so the MSP ends up needing a second person who knows the site, and a third once the client adds an office in another city of the same country.

The cost consequence is simple. A published monthly rate buys one engineer, and the Singapore and Malaysia figures are explicitly no backfill. Two people at those rates is double the monthly line, three is triple, and that multiplication, not the hourly rate, is what separates a comfortable margin from a loss. Brocent describes leave cover from a pool of trained engineers for its full-time service, and backfill appears as an option on the rate page, but no price for backfill is published, so ask for it as a separate line.

This is the strongest argument for mixing patterns. Pooled dispatch has redundancy built in, because the service level is contractual and whichever engineer is available attends. Resident staff have it only if you pay for it. For a small office, a fixed weekly slot plus on-demand dispatch for the rest often gives better continuity per dollar than one resident engineer with no cover.

How does white-label delivery work in practice?

White-label means the end client experiences the MSP, not the partner. Three questions define it, and each should be answered in the contract before the first visit, not discovered during it.

Whose badge and whose name?

The engineer attending a client's site can introduce themselves as the MSP's engineer, wear the MSP's badge, or be openly identified as a partner's engineer. Building management, security desks and landlords often need a named company on the visitor list, so a fully hidden partner is rarely practical. What an MSP usually needs is not secrecy but a clause on communications: the partner does not market to the client, does not solicit the client's staff, and refers any commercial question back to the MSP.

Whose ticket system?

Most MSPs want their own ticketing system to remain the single record. The published dispatch description says requests are submitted through Brocent's helpdesk or an ITSM platform. That leaves open whether your system is the entry point, whether tickets are mirrored through email or an integration, and who owns closure. Do not assume it; make it an onboarding item with a named owner on each side.

Who talks to the end client?

The cleanest rule is a split by situation. The partner engineer speaks to the client's people during the visit about the job itself. Anything about scope, price, escalation or dissatisfaction goes through the MSP. The engineer's report is addressed to the MSP, which then shapes what the client sees. A partner that is comfortable with this is also a partner that will not go around you later.

What does it cost per country? A worked example on published rates

The arithmetic below uses only the published figures above, as published on 2026-10-05. It is illustrative arithmetic, not a quote. The assumptions are stated each time, and real programmes should be priced by a consultant because volume, scope and site conditions change them.

Pay by attended hours

A two-hour visit costs the first hour plus one additional hour: Singapore 85 + 78 = USD 163; Malaysia 65 + 59 = USD 124; Indonesia 46 + 39 = USD 85; Thailand 65 + 59 = USD 124. A four-hour visit costs the first hour plus three additional hours: Singapore 85 + 3 × 78 = USD 319; Malaysia and Thailand 65 + 3 × 59 = USD 242 each; Indonesia 46 + 3 × 39 = USD 163.

Fixed weekly slot

Suppose each of the four countries gets one four-hour visit a week, taken as four weeks a month for simplicity. The monthly attended-hours cost is Singapore 4 × 319 = USD 1,276, Malaysia 4 × 242 = USD 968, Thailand USD 968 and Indonesia 4 × 163 = USD 652. The four together are USD 3,864 a month, with the caveat that urgent extra visits are not included.

Resident engineer

Where a monthly rate is published, one dedicated engineer is USD 4,160 in Singapore and USD 1,820 in Malaysia, or USD 5,980 for one in each. Two per country, the planning assumption from earlier, doubles that to USD 8,320 and USD 3,640, and three per country gives USD 12,480 and USD 5,460. Indonesia and Thailand cannot be added to this calculation because no monthly rate is published for them.

Where does one pattern overtake another?

Set the Singapore monthly rate against four-hour visits: 4,160 divided by 319 is about 13 visits a month, roughly three a week. In Malaysia, 1,820 divided by 242 is between seven and eight visits, a little under two a week. In practice, if a site needs less attended time than that, dispatch is cheaper; above it, a resident engineer is. Published rates are described as falling at volume, so a multi-country programme will price below these single-ticket figures; this arithmetic gives you an upper bound to negotiate down from, not the final number.

How long from signature to the first engineer on site?

We will not give a number of days, because there is no published lead time for this to be quoted from, and an invented figure would be worse than none. What can be said is what drives it.

For on-demand dispatch, the clock that is published is the service level once a request exists: the standard tiers give P1 response in 2 hours and P2 in 4 hours with next-business-day attendance for 8×5 cover, 1 and 2 hours with same-day attendance for 8×7, and 15 minutes and 1 hour with 4-hour attendance for the 24×7 emergency tier. The setup before that, such as a contract in place, a request channel agreed and the client's sites registered, is separate and is where an MSP's own paperwork usually takes the longest.

For a resident engineer, the drivers are who is assigned, how long the client's building takes to issue a pass, whether the engineer needs accounts in the MSP's tools, and how much handover from the client's previous arrangement there is. Ask the partner for a written plan with named steps, and ask which of them depends on you.

What belongs in the back-to-back contract?

A back-to-back contract means the promises you make to your client are matched, clause for clause, by what the partner promises you. It is where a good programme avoids a bad week. Cover at least these points.

• Service levels: the response and attendance times you offer the client, mirrored at least as strictly in the partner's contract, with the time zone and public holidays of each country stated.
• Scope by country: which cities are in, which are out, and what the first-hour rate covers in travel.
• Cover and continuity: who covers leave, how soon, and whether the cover engineer is briefed on the site.
• Reporting: the signed service report format, the fields it carries and how quickly it reaches you after a visit.
• Access and security: which of your tools the partner's engineers may use, under what accounts, and how access is removed when someone leaves.
• Non-solicitation and communications: the partner does not approach your client, and you do not approach the partner's engineers.
• Pricing and review: rates by country in a named currency, the volume tiers, the tax treatment and when rates are reviewed.
• Termination and handover: what happens to documentation and site knowledge if either side ends the arrangement.

If you want a longer checklist for judging the partner itself, rather than the contract, use the vetting guide linked earlier, and compare against the service pages below.

Build your own team, hire local freelancers, or use a delivery partner: how do the three compare?

Comparing three ways to put hands on the ground

• Own overseas team: the most control, since engineers are your employees, on your process and your brand. It is also the heaviest commitment: you need a local entity or employer of record, local hiring, leave and public-holiday cover, and a workload that keeps people busy in four countries at once. It makes sense when you already have enough committed demand in a country to carry the payroll.
• Local freelancers: the fastest and lightest to start, and fine for one-off jobs. The weak points are continuity and accountability. Nobody covers the freelancer's leave, quality varies, and there is no standing process for security, reporting or replacement, which a client's audit will eventually ask about.
• Local delivery partner, white-label: a managed middle path. You get a contract, a service level, pooled cover and reporting without a payroll, and the price is that you depend on the partner and give up some margin. It suits an MSP that has won overseas scope but cannot yet predict volume per country.
• Rule of thumb: begin with a partner everywhere, move to your own staff in the one country where volume proves steady, and keep freelancers for pure overflow rather than the core.

Frequently asked questions

Can the partner's engineers use our ticketing system?

It is something to agree, not to assume. Brocent's published description is that requests are submitted through its helpdesk or an ITSM platform. Whether your system is the entry point, how tickets are mirrored and who closes them are onboarding items that you should write down with a named owner on each side before the first visit.

Can engineers work in our name?

Often yes in conversation, but physical sites usually need a named company on the visitor record, so complete invisibility is rarely realistic. What can be agreed is how engineers introduce themselves, what they wear, and a clause that the partner does not market to your client. Treat this as a contract term to confirm in writing; it is not a published product feature.

Can one contract cover all four countries?

Brocent describes field dispatch as coverage in more than 100 countries through a single contract, and its Southeast Asia coverage as direct teams in Singapore, Malaysia and Thailand with Indonesia through a certified partner network, coordinated from Singapore. A single commercial framework is therefore the model; how invoicing, currency and local tax invoices are split by country is a point to settle in the proposal.

How soon can an engineer be on site?

No lead time is published, so we do not quote one. For dispatch, the published service levels apply once a request exists. For resident cover, the time depends on assignment, building access and onboarding to your tools. Ask for a step-by-step plan from signature to first visit.

Do the engineers need to speak Chinese?

Only if the client's site needs it, and that is a per-site decision. Local languages matter more day to day, such as Thai in Bangkok and Bahasa Indonesia in Jakarta. Brocent's resident service describes bilingual engineers, but there is no published guarantee of a Mandarin speaker in each country, so state the language requirement as a line in the scope for each role.

Who covers when the engineer is on leave?

For the full-time service, Brocent states that leave is covered by a replacement from a pool of trained engineers. The published monthly rate is described as no backfill, so ask for the backfill option and its price as a separate line, and see our Singapore guide to leave cover and backfill for the question list.

Can the price be quoted per country?

Yes, and it should be. The published rate card is per country already: dispatch rates for Singapore, Malaysia, Indonesia and Thailand, and monthly rates for Singapore and Malaysia only. Ask for each country as its own line so you can resell by country, then ask what the volume discount looks like when all four are on one contract.

What should an MSP do next?

Start with one question per country: how many sites, what pattern each one needs, and what the client's service level promise is. Then match the pattern to the price. For a handful of small sites, fixed visits plus dispatch will usually beat resident staff; for a busy office with daily demand, the monthly rate starts to win, with cover priced in.

If you want to see how those pieces fit your clients' overseas offices, read the field IT dispatch service page, which is the MSP-facing route for per-country dispatch and a proposal request. For the end-client side of the same story, the managed IT support overview and pricing pages are the reference, and the contact page is the place to ask for a per-country quote.