Twelve People and a Thirteen-Hour Gap: IT Support for a US Software Company's Singapore Sales Office

A regional office's IT problem is rarely skill; it is time zone and hands. Support has to run in Singapore hours, and someone has to be able to walk in. Both can be bought without a hire, while headquarters keeps control of identity and policy, which is how a twelve-person Singapore sales office gets covered properly.

The office: twelve people, no IT function, and a very long way from headquarters

Picture the Singapore sales office of a US-headquartered software company. Twelve people work there: account executives, a couple of pre-sales engineers, a sales-ops coordinator and a finance coordinator who handles local invoicing and expenses. The office is a serviced or leased floor in the central business district, with a reception desk shared with other tenants, one shared printer, and two meeting rooms. One of those rooms is fitted with a video conferencing screen and a ceiling microphone, and it hosts customer calls across Asia-Pacific almost every day.

The laptops were ordered by headquarters and are enrolled in the company's device management tool. Accounts live in the identity platform that headquarters runs. Security policy, software licences and the list of approved applications are all decided in the US. Nobody in the Singapore office is an IT person. The sales-ops lead, who is the reader this article is written for, ends up as the unofficial fixer simply because they are organised and sit near the printer.

One clear note before going further. This is an illustrative composite scenario, not a named client. It is built from the shape of a situation that is common for foreign software companies, where a small revenue-generating office is set up quickly and the IT model is simply extended from the head office without much thought about what a twelve-person site on the other side of the world actually needs.

The office does not need a big IT programme. It needs a handful of things to work reliably in its own working hours: sign-in, video calls, printing, Wi-Fi, and new starters who can be productive on their first morning. That is a small problem, but it is a stubborn one, and it is stubborn for a reason that has nothing to do with the quality of anyone's engineering.

If your situation looks more like a regional headquarters with a small IT team drowning in tickets from plants, that is a different problem, covered in a separate case. This article is about the office with no IT function at all, which supports nobody else and has nobody to escalate to except a queue in another hemisphere.

What actually goes wrong at 9 a.m. in Singapore?

A regional office does not suffer exotic failures. It suffers ordinary ones at the wrong hour. Here are three that a twelve-person office will meet within a few months of opening, and each one shows a different part of the problem.

A locked account before the first customer call

An account executive arrives at 8:45 a.m. with a call booked at 9:30 for a prospect in Jakarta. Their password expired over the weekend, or a new phone has broken the multi-factor prompt. They cannot open email, the calendar or the demo environment.

At 8:45 a.m. in Singapore it is 8:45 p.m. the previous evening in New York during daylight saving time, or 7:45 p.m. in winter. The HQ service desk is either closed for the night or staffed by a follow-the-sun contractor working a queue in the order it was received. The account executive files a ticket, and the ticket is picked up when the US morning starts, roughly when the Singapore afternoon is ending. The customer call is over by then, and so is the opportunity to have made a good impression.

A meeting room that will not join the video call

The room screen shows a spinning wheel because a firmware update was applied overnight, or because someone unplugged the cable that carries the camera and the speaker, or because the room device lost its sign-in. The sales team is standing in the doorway with a customer waiting in the lobby. Remote support could possibly restart the device, but the person who knows which cable goes where is not in the building, and neither is anyone who has ever seen the room.

This is the classic example of the "hands" problem. The fix is not intellectually hard. Somebody just has to be in the room, press the right button and check the cable. A remote engineer on the other side of the world cannot do that, however skilled they are.

A new hire whose laptop shipped late

A new account executive starts on Monday. Their laptop was ordered from headquarters and sent by international courier. It cleared customs on Thursday, was held for a paperwork query on Friday and arrives on Tuesday. The new hire spends their first two days borrowing a colleague's machine, which is a security exception nobody planned, and waits for an HQ engineer to be available to walk them through enrolment during a time slot that suits neither side of the world.

None of these three incidents is severe. Taken together, though, they explain why a regional office quietly loses confidence in IT. Each one costs the office a few hours, a small amount of credibility with a customer or a new colleague, and a mild but real dent in the feeling that this company is set up to support Singapore properly.

Why can't HQ IT fix this from the US?

The tempting conclusion is that headquarters IT is not doing its job. That conclusion is almost always wrong, and acting on it produces a worse outcome than doing nothing.

Consider what HQ IT is set up to do. It looks after identity, security policy, licences, device fleets, and the systems that the company runs on. It is usually a small, stretched team measured against the needs of the whole company, and the bulk of its users sit within a few hours of each other in the US. Its service desk hours, its escalation paths and its staffing are all designed around that population. Singapore is one small site among many, and it sits about twelve to thirteen hours ahead of US Eastern time, and fifteen to sixteen ahead of Pacific. The exact gap shifts by an hour depending on daylight saving in the US, since Singapore does not observe it.

The difficulty is structural, and it has two parts.

• Time. The Singapore working day sits almost completely outside the US working day. The overlap is a thin slice of the evening in Singapore, when people are heading home. Anything that needs a human at HQ during Singapore's morning has to wait for the next US business day, or be handled by an on-call arrangement that HQ engineers understandably resent.
• Hands. A remote engineer can reset a password, push a policy and reinstall an application. They cannot swap a cable, unbox a laptop, replug a room device, chase an internet provider on a site visit, or hand a machine across a desk and watch the person sign in for the first time.

Both problems are solved by the same kind of resource: someone physically and temporally near the office. Neither problem is solved by asking HQ IT to work harder, buy a better ticketing tool or add another service desk shift. Framing this as a performance issue makes HQ IT defensive, and it also tends to result in the regional office being handed a list of "self-service" tips that nobody in Singapore has the time or the access to follow.

The better framing is the one that comes naturally to operations people: some jobs are best done centrally, and some are best done locally. HQ IT should keep doing what it does well, which is deciding who may sign in, what a laptop must comply with and which tools the company uses. The Singapore office needs a second pair of hands and a second clock, without any of the control moving away from HQ.

The split that works: HQ owns identity, policy and tooling; a local partner owns the hours and the room

The arrangement that holds up in practice is a clean division of responsibilities, agreed in writing, where each side does the part it is positioned to do.

HQ keeps the things that should never fragment across regions:

• The identity platform, including who is created, who is disabled and who has administrative rights.
• Security policy, device compliance rules and the software catalogue.
• The tooling itself, meaning the device management console, the ticketing system and the licence pool.
• The decision about what counts as a policy change.

The local partner takes the things that depend on the clock and on presence:

• First-line response in Singapore working hours, using HQ's own tools under a scoped role rather than a separate set of systems.
• Physical presence: walking into the office, checking the meeting room, replacing a failed peripheral, unboxing and handing over a new laptop.
• Local coordination with the building manager, the internet provider and the couriers who deliver equipment.
• A clear escalation back to HQ for anything that touches identity, policy or a system HQ owns.

The remote side of this is what a 24×7 help desk is designed to provide. Brocent's published figures for that service are around 15,000 IT incidents handled annually, with 90% of calls answered within 40 seconds, available 24×7×365 in Mandarin, Cantonese and English. When a remote fix is not possible, the service escalates to on-site dispatch. For a Singapore office the value is that someone is answering during Singapore's day, and that the same organisation can then send a person when the problem turns out to be physical.

The point of the split is that the local partner works inside HQ's tooling, not beside it. If the partner has to run its own ticket queue, its own remote-access tool and its own set of admin accounts, HQ has lost visibility and gained a new security review. If the partner works inside the systems HQ already runs, with a defined role, HQ keeps one audit trail and one policy.

What does onsite support look like at twelve people?

The instinct is often to ask for an engineer in the office. At this size that is almost never the right shape, and the arithmetic makes it obvious. The figures below are arithmetic on Brocent's published indicative rates as read on 30 September 2026. Rates change, so check the live dispatch rate card before you budget.

Option one: on-demand dispatch

For Singapore, the published dispatch rate is USD 85 for the first hour and USD 78 for each additional hour. These are indicative 2026 rates for Level 1 end-user-computing support, on a next-business-day, 9×5 basis, in US dollars, tax exclusive, for the city centre. The first-hour minimum includes travel within the metro or central business district area, and the work is billed after the job, with no prepayment and no contract minimum.

Arithmetic on those numbers: a two-hour visit is USD 85 plus USD 78, which is USD 163. Four such visits in a month would come to USD 652. For a twelve-person office that is a realistic month of occasional physical problems, such as a room device, a printer, a network port and a hand-over, and it is a variable cost that stays at zero in a quiet month.

Option two: a scheduled preventive visit

Brocent's field IT dispatch service also covers scheduled monthly or quarterly preventive maintenance visits for smaller offices. For a twelve-person office this is often the more useful pattern. A visit at a fixed time each month lets someone walk the floor, check the meeting room end to end, test the printer, look at the Wi-Fi coverage, tidy the cabling, and hand over any laptops that arrived in the previous weeks. Problems that would have become a 9 a.m. emergency are found in a calm hour instead.

Using the same arithmetic, one scheduled two-hour visit per month at the published rates is USD 163. Treat that as a planning figure rather than a quote, because the scope of a preventive visit, and whether it is billed on the standard hourly basis, should be confirmed before you rely on it.

Why not an embedded engineer?

The published rate for a dedicated engineer in Singapore, entry level, monthly and without backfill, is USD 4,160 per month. Divide that by the USD 163 two-hour visit and you get roughly 25 visits, which is more than one a working day. A twelve-person office does not generate 25 site visits worth of physical work in a month. It generates a handful at most, plus a long tail of remote tasks that a help desk can absorb.

A dedicated person is also a single point of failure: no cover during leave, no colleague to consult, and a role that will drift into general office administration because the IT work is thin. A dedicated engineer makes sense when the site has enough volume to keep one person busy. If you want to see where that break-even sits for a larger site, a marine services case works through the dispatch-versus-dedicated question in detail.

The correct shape for twelve people is a mix: remote support in Singapore hours as the default, and a person on site when something physical needs doing. That is what on-demand dispatch and a scheduled visit provide.

HQ remote only, a local freelancer, or a local managed partner: how do they compare?

Three options come up in almost every conversation about a small regional office. They differ on the three things that matter most to the sales-ops lead: how fast you get a response in Singapore hours, whether support continues when one person is unavailable, and how much control HQ retains.

HQ remote support only

• Response in Singapore hours: Slow by construction. A ticket raised in the Singapore morning typically waits until the US morning, unless HQ pays for out-of-hours cover.
• Continuity: Good for anything HQ can fix remotely, since the team is stable and has the full context. Weak for anything physical, because nobody is there.
• Control: Complete. Everything stays inside HQ's tools and policies.

A local freelancer

• Response in Singapore hours: Often quick when they are available, and they can come in person.
• Continuity: The weak point. One individual means no cover during leave, illness or a busy period with another client. Knowledge lives in their head rather than in HQ's documentation.
• Control: Depends entirely on how much access HQ is willing to hand to an individual. Many HQ security teams are not comfortable granting admin rights to a sole trader, and reasonably so. The usual result is a freelancer who can plug things in but cannot fix accounts.

A local managed partner working inside HQ's tooling

• Response in Singapore hours: Designed for it. The remote desk covers the Singapore day, and a dispatch tier can put a person in the office.
• Continuity: A bench of engineers and a documented process, so a single absence does not stop the service.
• Control: HQ defines the role, the permissions and the boundaries. The partner works in HQ's tickets and tools under a scoped account, and everything is auditable.

For a fuller comparison of how a US buyer should evaluate several providers across Asia-Pacific, including how the commercial models differ, see this piece on APAC partner economics for US companies. The short version for a single small office is that the third option costs a little more than a freelancer and a lot less than an embedded hire, and it is the only one that scores well on all three dimensions at once.

How does the handshake with HQ work?

Most failed regional-support arrangements do not fail because the partner is bad. They fail because nobody wrote down who is allowed to do what. A short document, agreed with HQ IT before the first ticket, is worth more than any service-level table. It should cover four things.

Ticket routing

Decide where a Singapore request starts. The simplest pattern is that the Singapore user contacts the local desk directly, by phone, chat or a shared mailbox, and the partner logs it in HQ's ticketing system so HQ sees every incident. Requests that need identity or policy changes are tagged and routed to HQ's queue automatically. Everything else is resolved locally.

Escalation back to HQ

Define what is out of scope for the partner, and how to hand it over cleanly. A sensible list includes creating or removing accounts, changing group memberships, altering conditional-access or security policy, approving software outside the catalogue, and anything involving data access. For each, agree how the partner escalates, what information it sends, and what response time HQ commits to. An escalation that arrives at HQ with the symptom, the user, the time and what has already been tried is far more likely to be resolved in one exchange.

Who holds admin rights

Keep the rule simple: HQ owns the tenant-level administrator roles. The local partner receives a scoped role that allows it to do the routine work, such as resetting a password, unlocking an account, re-enrolling a device or clearing a stuck sign-in, and nothing beyond that. Grant access through named accounts, so every action can be attributed, and review the list every quarter. If the partner leaves, HQ revokes one set of accounts and nothing else changes.

What the local partner may and may not change

Write it as two short lists. May: replace a failed peripheral like-for-like, move a device between ports, restart and re-pair the meeting room device, coordinate with the building on Wi-Fi and internet faults, unbox and hand over a laptop that HQ has already prepared. May not: install software outside the catalogue, change security settings, buy hardware without approval, or create workarounds that bypass policy. The second list matters as much as the first, because it is what lets HQ's security team relax.

When these four items are agreed, HQ IT tends to become supportive rather than wary. The local partner is taking the awkward hours and the physical work off their plate while leaving the decisions with them.

How do new hires get ready when laptops ship from the US?

Onboarding is where the time zone gap costs most, because a new starter's first impression of the company's IT is formed in the first hour. There are two workable approaches, and both can be run through the local partner.

The first is to ship the laptop to the partner rather than to the new hire's home or the office reception. The partner can receive it, check it against the order, confirm it has been enrolled in HQ's device management tool, and hold it until the start date. Brocent's field dispatch service describes device provisioning as unboxing, imaging, configuration and handover to end users at remote locations, which is the sequence a small office needs. That way the delayed-courier problem becomes visible days ahead, rather than on the morning the person arrives.

The second is to have HQ pre-stage the device as far as it can. HQ enrolls the machine, assigns the policies and creates the account, then the local partner completes the physical side: unboxing, first sign-in with the user, multi-factor set-up, printer and Wi-Fi connection, and a short walk through the meeting room. The new hire is at their desk with a working machine before mid-morning, and HQ has not had to stay up late.

A short checklist helps whichever approach is used:

• Confirm the shipping date and tracking number well before the start date.
• Agree who receives the parcel and where it is stored.
• Have HQ create the account and licence in advance, and tell the local desk which permissions the role receives.
• Book a short hand-over slot on day one, with the new hire, the sales-ops lead and the local engineer.
• Record the serial number and the hand-over in HQ's asset system, so both sides agree on where the device is.

If the laptop is late, ask the partner whether a properly enrolled loan device can be arranged, which is a much better answer than borrowing a colleague's machine.

From visits to a per-user plan

Some offices are content with on-demand dispatch and a scheduled visit. Others prefer to make the cost predictable and put the whole arrangement, remote desk, dispatch and lifecycle tasks, on a single monthly line. That is where a per-user managed IT plan comes in.

Brocent publishes Singapore per-user pricing on its pricing page. The Established tier, which covers 5 to 300 employees, is listed at S$185.08 per user per month. As arithmetic on that published price, twelve users come to S$2,220.96 per month. That figure is for illustration; the live pricing page is the reference, and you should check what the plan includes before comparing it with pay-as-you-go dispatch.

The trade-off is straightforward. Pay-as-you-go dispatch is cheapest when the physical work is occasional, and it requires you to raise each request. A per-user plan costs more in a quiet month and less in a busy one, and it removes the friction of asking. Many small offices start with dispatch, learn what they actually use over two or three quarters, and then decide. Details of the plan structure are on the managed IT support page.

Frequently asked questions

Can a local provider work inside our HQ's tools?

Yes, and that is the arrangement to insist on. The local partner should use HQ's ticketing system, remote-access tool and device management console under a scoped, named account, rather than a parallel set of tools. The specifics, including which role is granted and how it is reviewed, are something HQ IT and the provider agree during onboarding.

Who owns admin rights?

HQ does. Tenant-level administrator roles, identity configuration and security policy stay with HQ IT. The local partner holds a limited role for routine tasks such as unlocking accounts and re-enrolling devices, with every action tied to a named user so HQ can audit it.

What does a visit cost in Singapore?

On the published indicative 2026 rates, as read on 30 September 2026, Singapore on-site dispatch is USD 85 for the first hour and USD 78 for each additional hour. That basis is Level 1 end-user-computing support, next-business-day, 9×5, in US dollars, tax exclusive, city centre, billed after the job with no prepayment and no contract minimum. A two-hour visit is therefore USD 163 by arithmetic. Check the live rate card before budgeting.

How fast can someone arrive in the CBD?

It depends on the service tier you choose. Under the published dispatch tiers, Normal Business Hours (8×5) gives a P1 response in 2 hours and a P2 response in 4 hours, with on-site attendance the next business day. Extended Hours (8×7) gives a P1 response in 1 hour and P2 in 2 hours, with on-site attendance the same day. The 24×7 Emergency tier gives a P1 response in 15 minutes and P2 in 1 hour, with on-site attendance in 4 hours. The indicative rate above is on the next-business-day basis.

Do we need a contract for 12 users?

Not for on-demand dispatch. The published rates are billed after the job, with no prepayment and no contract minimum. A per-user managed plan is a different commercial arrangement, and its terms are set out on the pricing and managed IT pages. If you have a specific requirement, contact the team and ask.

What happens when HQ changes policy?

HQ changes it, and the local partner follows. Because the partner works inside HQ's tools and under HQ's policy, a change to device compliance rules, the software catalogue or the sign-in requirements takes effect for Singapore in the same way as for any other site. The practical step is to make sure HQ IT tells the local desk about changes before they roll out, so the person answering the phone in Singapore is not the last to hear.

Can the same provider cover Kuala Lumpur or Jakarta later?

Field dispatch covers more than 100 countries, and Asia coverage includes Singapore, Hong Kong, Japan, India, Thailand, Vietnam and Indonesia, among others. On the same indicative basis as Singapore, the published dispatch rate for Malaysia is USD 65 for the first hour and USD 59 for each additional hour, and for Indonesia USD 46 and USD 39. That means an office opened later in either city can be added to the same arrangement, using the same handshake with HQ.

Where to go from here

A twelve-person Singapore office does not need an IT department. It needs remote support that runs on its own clock, a person who can be in the room when the problem is physical, and a clear agreement with headquarters about who decides what. HQ keeps identity, policy and tooling; a local partner covers the hours and the floor.

If you would like to see what that could look like for your office, start with the managed IT support overview, or look at the Singapore per-user pricing on the pricing page.