Who Actually Delivers Your IT in Asia? The Subcontracting Layer Behind a Regional Coverage Map

The short version: Does my IT provider subcontract? In at least some cities, probably yes. Behind many regional coverage maps, some pins are the provider's own employees and some are another company's engineers. No public census measures how much IT work in Asia is subcontracted, so this report uses Brocent's published rate card and its own inbound enquiries, labelled as ours. Ask who attends, who employs them, who holds the SLA and your data.

Every regional IT provider publishes a coverage map. A pin on it says that someone can reach a city. It rarely says who that someone is: an employee with a company badge, a long-standing local partner, a firm engaged for one visit at a time, or a broker one layer further down. Buyers can sign multi-country agreements without asking, and the answer can arrive during an incident, in the wrong language, at the wrong hour.

This report asks what sits behind the pin, and it is written for the buyer, not for the provider. It starts where our report on the Hong Kong and Singapore provider landscape stopped, with a point there that deserved a full treatment: multi-market coverage that resolves, in that report's words, "into a subcontractor in every city but one." Here we ask how the layer works, why there is no statistic for it, and what a buyer can verify.

A disclosure. Brocent is itself a party to the structure this report describes. It runs a delivery network with its own engineers in some places and partners in others, and, as the data below shows, other IT companies write to it to source local delivery. We have tried to handle that by labelling every Brocent figure as ours, by using only what Brocent's own pages say, by saying where those pages leave a question open, and by writing the buyer's questions so that a buyer can put them to us as readily as to anyone else.

Key findings

• There is no public census of subcontracted IT delivery in Asia. We looked for a government statistic, an industry-body count and a survey of providers, and found none. The largest provider survey we could open does not appear to ask the question, and a report that claimed a figure would be inventing one.
• A pin on a coverage map can mean at least four different things. An employee, a long-term local partner, a per-visit dispatch contract, or a broker. Brocent's own Locations directory uses a four-label vocabulary for the same distinction: Direct Office, Partner Network, Remote Support and Supply Chain.
• Brocent's own inbound shows the layer from the inside. In the 89 enquiries that came in through brocent.com as of 2 October 2026, which we read by hand, about 16 of roughly 65 genuine buying enquiries, around a quarter, were IT service companies sourcing local delivery, not end customers. Four of the 13 enquiries that became deals came from that group. This is one company's website, not a market measurement.
• A published rate card is an itemisation of what the layer must recover. Brocent's published on-site rate is described as fully loaded for "cost-of-living, bilingual engineers, training, FX/tax handling, credit-term financing, 24×7 coordination." Whoever sits between the end customer and the engineer has to recover the same costs and then add its own.
• Brocent's own earlier research puts one multiple on the table, and says it is not all margin. Brocent's published dedicated-engineer rate is about 2.2 times the entry-level wage in Hong Kong, about 1.6 times in mainland China and about 1.0 times in Singapore, and the same report states: "That gap is not margin alone — it is a real cost stack."
• The questions that resolve it are short. Who employs the person who arrives, who answers the phone, who holds the SLA, whose name is on the invoice, and who is bound to protect your data.

What can a pin on a coverage map actually mean?

Four arrangements sit behind a pin. They are not a formal taxonomy and no standard defines them; they are our grouping of what providers describe, and each can be entirely legitimate.

Four kinds of pin, compared

• A badged employee. The engineer is on the provider's payroll, in the provider's local entity, trained by the provider and answerable to its management. The provider carries the employment relationship, the training and the replacement when someone is sick.
• A long-standing local partner. An independent firm with which the provider has worked for years, often under a framework agreement, that supplies engineers trained to the provider's procedures. The provider is the contract holder and the partner is the delivery arm.
• A per-visit dispatch contract. A firm or individual engaged for a single job at an agreed price, with no continuing relationship. It can be fast and cost-effective, and it is the arrangement where continuity of knowledge about your site is weakest.
• A broker. A party that holds the customer contract and arranges delivery through another party, which may in turn engage a third. The customer deals with the first party and may never learn the name of the last.

None of these is a fault in itself. A buyer with a single site in one city may be perfectly served by any of them. The problem is that the map draws all four the same way, and the difference becomes visible only when something goes wrong.

Brocent's own pages show the distinction in the provider's own words. Its Coverage page describes a two-part model: "Brocent employs in-country engineers who understand local IT, language, and business culture" in a named list of countries, and "Beyond Asia, we work with pre-qualified field engineers and IT service partners in 100+ countries — vetted, trained to Brocent's standards, and centrally coordinated." Its Locations directory labels each location with a tier, using four labels: Direct Office, Partner Network, Remote Support and Supply Chain. The Coverage page names ten countries with in-country engineers (Singapore, Hong Kong, China, Taiwan, Japan, Poland, the USA, Thailand, Malaysia and Vietnam), but its headline claim of 100+ countries does not say which of the others are served by employees and which by partners. That is not a criticism peculiar to Brocent. It is the normal shape of a coverage claim, and it is the reason for the questions later in this report. A buyer should put them to Brocent as well.

Why is there no statistic for the layer nobody reports?

Before using any internal data, it is worth stating what could not be found, because the gap is itself the finding.

We looked for a measure of how much IT field work in Asia is subcontracted: a government statistic, an industry-body census, or a provider survey that asks the question. We did not find one. What exists are market-size estimates for IT outsourcing and for field-service software, which describe revenue, not who employs the engineer who attends a site. Two named sources are the closest relatives, and neither answers the question.

Kaseya's 2026 State of the MSP report surveyed more than 1,000 managed service providers worldwide. It is useful context on the provider side of the market, but we found no question or finding in it about subcontracting or partnering for delivery, and we draw no conclusion about Asia from it. We were unable to re-open the report while finalising this article, so we quote no figures from it here.

CompTIA's IT Industry Outlook 2025, published in December 2024, reports that 90% of channel companies partner with other industry players to handle the growing complexity of technology. That is a statement about partnering of any kind, and it is not broken out for Hong Kong or for delivery work specifically. The public page for the 2026 edition is an excerpt that carries no channel or partnering figure, and we did not use the gated full report.

The honest summary is that nobody publishes how many of the engineers who attend a site in Hong Kong, Singapore or elsewhere in Asia work for the firm whose name is on the contract. We do not manufacture a number by combining a channel-partnering share with a country count from a coverage map. Doing so would produce something that looks like a statistic and measures nothing.

What does Brocent's own inbound show?

What a single provider can offer is a sample of one website, and it is worth being exact about what that sample is.

This section is Brocent's own operational data, not research. It comes from the enquiries that arrived through brocent.com, which we read one by one and classified by hand. We use one pull, with its date and denominator: as of 2 October 2026 there were 89 such enquiries. We do not name any enquirer, and we describe types of request, not individual ones.

• About a quarter of genuine buying enquiries came from IT service companies. Of roughly 65 enquiries that were genuine requests to buy, about 16, or around a quarter, were not end customers. They were IT service companies that had won work they could not physically deliver and were looking for local hands. The figures are approximate because the classification is ours.
• That group is a small but real part of what converted. Thirteen of the 89 enquiries became deals, and four of those thirteen came from this group. Four is a small number, and we draw no rate from it.
• The ask is precise and pre-scoped. As we read these enquiries, they set out which city, what pattern of support, in which language, by what date and at what price, far more often than they ask why a company should outsource at all.
• Language is stated as a requirement. Several of these enquiries name the language of the engineer as a condition, for example Mandarin, bilingual Chinese and English, or English. We have not counted how many.
• Singapore volume is inflated by this group. Country mentions across the 89 enquiries ran Singapore 58, China 33, Hong Kong 18 and the United States 10, with a record able to mention more than one country. A large share of the Singapore mentions came from IT service companies sourcing engineers for their own clients, not from Singapore end customers.

The limits matter as much as the figures. This is one website, in one period, classified by one team. Later pulls (98 enquiries on 23 October 2026 and 105 on 30 October 2026) were not re-classified by type, so we do not apply the quarter to the new records. These numbers say that, to Brocent, IT service companies are a visible source of demand for local delivery. They do not say how common subcontracting is in the market, and nobody should read them that way.

Why are there two margins, not one?

Brocent published research in the third quarter of 2026 on what Asia pays for on-site IT support: the wage-to-rate gap across twelve markets. It is Brocent's own research and it uses Brocent's own published prices as the rate side, because they were the only pricing dataset in the study quoted consistently, per dedicated engineer per month, across several countries. The report says plainly that every ratio in it is directional.

For the three markets that matter here, the report compares Brocent's published dedicated-engineer monthly rate with published estimates of an entry-level support engineer's monthly wage:

• Hong Kong: a wage of roughly US$1,872 to US$2,218 against a Brocent rate of US$4,810 a month, about 2.2 times the upper end of that range (2.2 to 2.6 times across it).
• Mainland China: a wage of roughly US$1,250 to US$1,667 against US$2,730 a month, about 1.6 times the upper end of that range (1.6 to 2.2 times across it).
• Singapore: a wage of about US$4,201 against US$4,160 a month, about 1.0 times.

Across all twelve markets in the study, the report finds that the multiple "ranges from roughly 0.6x to 5x depending on market and which wage benchmark you compare against." It also states that "that gap is not margin alone — it is a real cost stack." That sentence is the point of the next section.

Here is the argument this report adds, and it is reasoning, not measurement. The multiple in Brocent's research is one gap: between what one provider charges for an engineer and what a comparable engineer earns. When a second company is inserted between the end customer and the engineer, a second gap appears. The delivering firm still has to recover its own cost stack. The intermediary has to recover the same costs it incurs for finding, qualifying, coordinating and invoicing, and then earn something for taking the customer relationship and the risk. We have no public figure for that second gap and we do not offer one. The mechanism is not controversial. What is missing is any data about its size, which is another reason to ask the question.

What does the layer absorb?

Brocent publishes an on-site dispatch rate card, and one footnote on it works as an itemisation of what any delivery chain has to cover. The dispatch rates page lists rates for 42 countries from Brocent's 2026 H2 standard price book, and its footnote reads: "Indicative 2026 rates (EUC L1, NBD, 9×5), USD, tax exclusive, city centre — fully loaded (cost-of-living, bilingual engineers, training, FX/tax handling, credit-term financing, 24×7 coordination), falling at higher volumes."

For the markets in this report, the first-hour and additional-hour figures on that page are:

• Hong Kong: US$98 for the first hour and US$78 for each additional hour.
• Singapore: US$85 and US$78.
• Mainland China: US$65 and US$59.
• Japan: US$130 and US$117.

The labels matter. These are indicative rates for level-one end-user computing support, next-business-day, on a nine-to-five weekday schedule, in the city centre. They are a first-party reference, not a market benchmark, and they are Brocent's prices, not the cost of the engineer.

Each item in that footnote is something a delivery chain must carry. What follows is reasoning about what happens to each when a layer is added, not a measurement.

• Bilingual engineers. The language the end customer needs has to travel intact from the customer's request to the person who arrives. Every hand-off is a place where a requirement stated as "Mandarin, onsite, Tuesday" can become "someone, onsite, Tuesday."
• Training. Knowing your site, your standard build and your escalation contacts is learned by the people who attend repeatedly. An engineer engaged per visit starts from zero each time, and a broker may not hold that knowledge at all.
• FX and tax handling. Each firm in a chain is a separate invoicing party, often in a different jurisdiction and currency. Who issues the local tax invoice, and who bears the currency and withholding costs, is decided somewhere in the chain.
• Credit-term financing. The firm that does the work waits to be paid. Brocent's rate page says dispatch visits are billed after the job on standard 30-day terms. In a chain, the delivering firm may be waiting on an intermediary that is itself waiting on the end customer, and the cost of that wait is priced in somewhere.
• 24×7 coordination. Someone has to answer the phone at three in the morning and know which engineer to call. In a layered arrangement it is worth knowing which of the parties owns that phone.

What does this mean for Hong Kong specifically?

Hong Kong is the focus market for this report, and it is the market our own Hong Kong IT support page describes in most detail. Consider a buyer with a Hong Kong head office and a few sites outside it. The distinction between one kind of pin and another matters most at the edges of that footprint, not at the centre.

For Brocent, Hong Kong is a direct location. Its Locations directory lists Hong Kong as a Direct Office, describes it as Brocent's Greater China regional hub since 2016 with 15 or more engineers, and lists English, Cantonese and Mandarin as working languages. That is what the provider says about its own Hong Kong pin. We have not audited it and a buyer should not take our word for it any more than anyone else's. The per-user monthly price for that Hong Kong delivery is published on our quote tool, which is the other half of the same answer: who attends, and what it costs.

Two features of the Hong Kong market make the question worth asking. The first is the rate structure. In Brocent's own research, the Hong Kong multiple of about 2.2 times the entry-level wage is higher than mainland China's about 1.6 and Singapore's about 1.0, and the first-hour rate of US$98 sits between mainland China's US$65 and Japan's US$130. A buyer comparing providers on price is comparing prices that can reflect very different delivery structures. A low quote may mean efficient direct delivery, or a chain in which the delivering firm is being paid less.

The second is verification. A Hong Kong buyer can verify a good deal about the party that signs the contract: its registered entity, its address, its staff. It can verify far less about the person who will actually attend a site in another city, and the contract may not say. That is why the questions in the next section ask for the name of the entity, not a description of a model.

Which questions actually resolve it?

These questions are written for the end customer. They are not a vetting checklist for a managed service provider that is itself subcontracting, which is a different problem for a different reader. For the first question most buyers should ask, who physically attends a site and whether they are an employee or a subcontractor, our report on the provider landscape sets out the reasoning, and we do not repeat it here. These questions go a step further.

• Who answers the phone, and who do they call? Ask for the escalation path in writing, with the named entity that operates the service desk and the named entity that dispatches. If those are different companies, ask what the hand-off looks like and who is on the clock.
• Who employs the person who arrives? Ask for the employing entity of the engineer who will attend your site in each city, and how the engineer will be identified on arrival. A company badge and an employer you can name are different things from a printed card.
• Who holds the SLA, and what happens when the delivering party misses it? The provider you contract with should hold the response commitment, and the contract should say who bears the consequence if a partner fails. Ask whether the SLA clock starts when you report the fault or when the delivering firm receives the job.
• Who is bound to protect your data? An engineer on your site sees your systems. Ask which entity is contractually bound to confidentiality and data handling, and whether that obligation passes down to anyone the provider engages.
• Whose name is on the invoice and the tax document? In each country where work is done, ask which entity issues the local invoice. It shows where the contractual relationship actually sits.
• How will you be told if the delivering party changes? A partner that served you well for two years may be replaced. Ask for notice of a change and the right to object.

None of these is a trap. A provider that delivers through partners can answer every one of them well, and a provider that delivers with its own staff can answer them in a sentence. The quality of the answer is the information.

Where does Brocent stand?

Brocent sits on both sides of this question, and a report that asks it of others should say so.

As a provider, Brocent describes a delivery model that combines its own engineers in some countries with partners in others. Its Coverage page states that Brocent employs in-country engineers in a named list of countries and works with pre-qualified field engineers and IT service partners in 100+ countries, and its Locations directory labels each location with a tier. That means some pins on Brocent's own map are Brocent employees and some are not, and neither page says, for the 100+ countries beyond the named list, which are served by employees and which by partners. A buyer should ask Brocent which is which, in the same terms as the questions above.

Brocent also advertises a field dispatch service with 100+ country coverage and a four-hour emergency or next-business-day dispatch SLA; that page, too, does not say which of those countries are served by employees. As a counterparty, Brocent is also written to by other IT companies that need local delivery in cities they cannot serve themselves. In Brocent's own inbound, as described above, that group is about a quarter of genuine buying enquiries. Brocent is, in other words, a possible link in other providers' chains as well as the owner of its own. We say that because it is true and because it is why we can see the layer from the inside.

We do not claim that this makes Brocent's answers better than anyone else's. It means we know the questions, and that we think a buyer is entitled to ask them.

What does this report not claim?

A research report is only as useful as its limits are clear. These are ours.

• It does not measure how much IT delivery in Asia is subcontracted. No public source we could find does, and we have not tried to derive a figure.
• The enquiry figures are Brocent's own and approximate. They come from one website, one pull dated 2 October 2026 with 89 enquiries, hand-classified by us. We did not re-read the type split on the later pulls of 98 and 105 and do not apply it to unread records.
• The wage-to-rate multiples are directional and use Brocent's own prices. They compare one provider's published dedicated-engineer rate with published wage estimates, and are not a market margin.
• The "second margin" is reasoning. We offer no number for it.
• The four pin types are our grouping, not a standard, and each can be legitimate.
• Kaseya and CompTIA are context. Neither source, as far as we could read, measures subcontracting, and neither sample describes Hong Kong.
• Brocent's statements about its own delivery come from its published pages. We have not audited them and they do not split employees from partners.

Frequently asked questions

Does my IT provider subcontract?

You should assume it might, in at least some cities, and ask. Many providers deliver with their own employees where they have an office and through partners elsewhere. That can be a perfectly good model. The useful question is not whether they subcontract but who employs the engineer who will attend your site, who holds the SLA and who is bound to protect your data.

How much IT support in Asia is subcontracted?

Nobody publishes a figure that we could find. We looked for a government statistic, an industry census and a provider survey, and found none. Market-size reports describe revenue, not who employs the engineer. A figure assembled from channel-partnering surveys and coverage-map country counts would only look like a statistic.

What does a coverage map tell me about who delivers?

Very little. A pin says someone can reach a city. It does not say whether that person is the provider's employee, a long-standing partner, a firm engaged per visit or a broker's contact. Ask for the employing entity in each city that matters to you.

Is it a problem if an IT provider uses local partners?

Not by itself. A buyer with sites in several countries often cannot be served by a single employer everywhere. The risk is accountability that is undefined until something fails, so the contract should say who holds the SLA, who is bound to your data and how you are told if a partner changes.

What should I ask a provider about who delivers my IT?

Ask who answers the phone and who they call, who employs the person who arrives, who holds the SLA and what happens if a partner misses it, which entity is bound to protect your data, whose name is on the local invoice, and how you will be told if the delivering party changes.

Why can a low quote for onsite IT support be a warning sign?

It can mean efficient direct delivery. It can also mean a chain in which the firm doing the work is being paid less, and prices that look similar can sit on very different structures. Brocent's own research found that the gap between a published rate and local wages is "not margin alone," so the quote needs to be read against what it includes, such as language, training and 24×7 coordination.

Does Brocent subcontract?

Brocent's own pages describe a model that combines its own engineers in some countries with partners in others, and for the 100+ countries beyond the named list they do not say which is which. We say so openly, and a buyer should ask us the same questions as anyone else. Brocent also receives enquiries from other IT companies looking for local delivery, which is how it sees the layer from the inside.

Next steps

Put the six questions above to every provider you are comparing, including us. If Hong Kong is one of your sites, the quote tool shows the published per-user monthly price for direct delivery there, so you can read a quote against a known structure. If you would rather put the questions to a person, talk to a consultant and ask them in whatever order you like.