The IT Roadmap Nobody Owned: A Singapore Regional HQ's vCIO Story

The short answer: When a Singapore regional HQ's IT manager resigned, the company discovered its multi-year technology roadmap had never existed as a document — it lived in one person's head, and it left with him. A virtual CIO makes the roadmap an artefact the company owns, with a named person accountable for it, without the cost or hiring risk of a full-time CIO.

The company in this article is a composite drawn from a pattern we see repeatedly across Singapore-headquartered regional offices. It is not a named client. What is real is the service model described: a named vCIO and technology roadmap is included in every Brocent managed IT plan tier, not sold as a premium extra.

The Singapore regional HQ problem: too big to improvise, too small to hire a CIO

Singapore's role as an ASEAN regional headquarters produces a very particular kind of company. The HQ itself is small — fifteen to twenty-five people covering finance, supply chain, regional sales management and administration — while the operational footprint it governs is much larger: plants, distributors, sales offices and warehouses across Malaysia, Indonesia, Thailand, Vietnam and often further north.

The technology decisions made in that HQ are disproportionate to its headcount. Which ERP the region standardises on. Whether the Vietnam plant's network gets rebuilt this year or next. How Microsoft 365 licensing is consolidated across five country entities. What happens to the data when a distributor relationship ends. Whether the group's security posture is adequate for the customers now sending security questionnaires.

These are CIO-level questions. They are not questions a competent systems administrator should be expected to answer alone, and they are not questions a managed service provider answers by default either — most MSPs are contracted to keep things running, not to decide where things should go.

So the questions get answered anyway, informally, by whoever in IT is most senior and has been there longest. That works, often for years. It works until that person leaves.

The scenario: a resignation, and a roadmap nobody can find

The composite company is a Singapore-headquartered manufacturer with roughly twenty people at HQ and operations across four ASEAN countries. Its regional IT manager had been with the group for nine years. He was good — the kind of person who knew which vendor contract renewed in which month, which plant's switches were end-of-life, why the Indonesian entity was still on a separate tenant, and what the plan was for consolidating it.

He resigned in the ordinary way, with two months' notice and no drama.

The handover produced a folder: vendor contacts, licence renewal dates, network diagrams of varying age, and a list of open tickets. What it did not produce — because it had never existed — was the roadmap. There was no document that said *here is where our technology is going over the next three years, here is the sequence, here is what depends on what, and here is why*.

The COO discovered this in the second week of the handover, asking what she thought was a simple question: what were we planning to do about the Vietnam network refresh? The answer involved a budget conversation from eighteen months earlier, a vendor quote that had expired, a dependency on an ERP migration that had since slipped, and a judgement call about whether to wait for a lease decision on the plant. All of it was correct. None of it was written down.

His successor — hired externally, competent, three weeks in — could not inherit any of it. What she inherited was a running estate and a set of decisions she had no context for. Her first six months would be spent rediscovering, from vendors and from colleagues' memories, a plan that had already been made once.

What this actually costs, beyond the obvious

The visible cost is the rediscovery period. The less visible costs are worse.

Decisions become reactive. Without a sequenced plan, technology spend responds to whatever broke or whatever a vendor is pushing. The Vietnam refresh happens when a switch fails, not when it was scheduled. Consolidation happens after an audit finding, not before. Each individual decision is defensible; the aggregate is expensive and incoherent.

Nobody is accountable to the board for technology. In a regional HQ, the COO or the managing director ends up representing IT in group discussions, describing a plan they did not make and cannot defend in detail. When regional or global management asks why the technology budget is what it is, the answer tends to be a list of line items rather than a strategy.

Institutional knowledge concentrates instead of accumulating. The successor will, over three or four years, rebuild the same undocumented understanding her predecessor had — and take it with her when she goes. The company has hired the same knowledge twice and owns it neither time.

Vendor relationships become unbalanced. A vendor who has served the account for years knows the estate better than the person now managing it. That is not a conspiracy; it is just an information asymmetry, and it shows up in renewal pricing and scope.

Cross-border complexity goes unmanaged. A regional HQ's hardest technology questions are the multi-country ones: data residency across ASEAN jurisdictions, licensing structures across entities, standardising a support model when each country office has its own habits. These are precisely the questions that never get written down, because they are nobody's single job.

None of this is a failure by the departed IT manager. He did the work. The company simply never asked for it in a form it could keep.

Brocent's perspective: the roadmap should be a document the company owns

Brocent has run IT for companies across Asia since 2007, opened its Hong Kong office in 2016, and has been headquartered in Singapore since 2021. Working with regional HQs is a large part of what our Singapore business does, and this pattern — the strategy that leaves with a person — is one of the most common structural weaknesses we encounter.

Our position is straightforward: technology strategy for a company of this size should be a named person's accountability and a written artefact the company owns. Not one or the other. A document with nobody accountable for it goes stale within a quarter. An accountable person with nothing written down is the situation described above.

That is why a named virtual CIO and technology roadmap is included in every tier of our managed IT plans rather than positioned as a premium upsell. A company at this size needs the strategic layer at least as much as a larger one does — it simply cannot justify a full-time hire for it.

A few things about how we run it are worth stating plainly, because "vCIO" is used loosely in this market.

It is a named individual, not a rotating account function. Our vCIO profiles are real Brocent executives with actual specialisms — IT solutions strategy, information security, multi-country HR and compliance, supply chain systems, infrastructure, Microsoft 365, and AI and R&D among them. A regional manufacturer's roadmap is assigned to someone whose background fits the questions it will contain.

The roadmap is a deliverable, not a conversation. It is written, versioned, sequenced and held by the customer. Our standard plans include customer-owned documentation and credentials as a matter of policy, and the roadmap belongs in that category: if you leave us, you keep it.

It is distinct from the account manager and from the vCISO. The account manager owns service delivery — tickets, SLAs, escalation. The vCIO owns direction. Where a company needs a dedicated fractional security executive rather than security as one topic within the roadmap, that is a separate vCISO engagement, quoted per environment.

It sits on top of a delivered service, not beside it. A vCIO who does not see your actual ticket volume, patch compliance and incident history is writing strategy from a slide deck. Ours works from the operational reality of the same managed IT support plan that keeps the estate running.

What a vCIO engagement looks like for a regional HQ

For a company like the one in this scenario, the first year has a recognisable shape.

An estate and decision inventory, early. Not a technical audit — those exist separately — but an inventory of the decisions currently in flight, the ones deferred, and the ones nobody has realised are due. In the composite company, that exercise surfaced the Vietnam refresh, the Indonesian tenant, an ERP dependency, and three vendor contracts renewing within nine months that nobody had diarised.

A written multi-year roadmap with sequence and dependencies. The value is less in the individual items than in the ordering: what has to happen before the ERP migration, what can only happen after the plant lease is settled, what is cheap to do now and expensive to defer. This is the artefact that did not exist.

Regular strategic reviews tied to the business calendar. Quarterly is typical, aligned to budget cycles rather than to IT's own rhythm, so that technology asks arrive when finance is actually able to consider them.

Board- and group-ready framing. A regional HQ frequently has to justify technology spend to a parent company in another country. Part of the vCIO's job is putting the roadmap into terms that survive that conversation — business outcomes and risk, not equipment lists.

Continuity across staff changes. This is the point of the whole exercise. When the incoming IT manager started in the composite scenario, the roadmap was the first document she read, and the vCIO was the person who walked her through why each decision had been made the way it had. Her ramp-up became weeks of context rather than months of archaeology.

Multi-country coordination as a standing topic. Data residency, licensing across entities, and a consistent support model across four countries are not project work; they are ongoing positions the roadmap has to hold and revisit.

Because the vCIO is included in the plan rather than billed separately, the practical question for most companies is not what it costs but whether they are using the one they already have. Plan pricing is published per user per month on the pricing page, and the strategic layer is part of it at every tier.

What actually goes into the roadmap document

"Roadmap" is a word that can mean almost nothing, so it is worth being concrete about what a useful one contains for a company of this shape.

A current-state statement per country. Not a full asset register, but enough that a new IT lead or a parent-company reviewer can see what each entity runs, where it diverges from the group standard, and why that divergence exists. In the composite scenario, the Indonesian entity's separate tenant had a legitimate historical reason that nobody had written down, which meant it kept being rediscovered as a surprise.

Decisions in flight, with owners and trigger dates. The Vietnam network refresh was not stalled because anyone had decided to stall it. It was waiting on a lease decision that had no date attached, so it simply never resurfaced. Naming the dependency and the date is most of the work.

A sequence, with the reasoning preserved. The ordering matters more than the list, and the reasoning matters more than the ordering. Anyone can rebuild a list of things that need doing. Nobody can reconstruct why the ERP migration had to precede the tenant consolidation once the person who worked it out has gone.

Standing multi-country positions. Data residency across ASEAN jurisdictions, licensing structure across entities, and the group's support model are not projects that close. They are positions that need to be held, reviewed and occasionally changed, and they belong in a document rather than in an email thread.

A budget shape, not a budget. Roughly what the next three years cost, split between run and change, in terms a parent company's finance function recognises. Precision here is false comfort; direction is what gets a conversation started.

Three ways a regional HQ handles IT strategy

Strategy held informally by one senior person

• What you get: Fast decisions, deep context, and no overhead — for as long as that person stays.
• What it costs: Nothing visible, which is exactly why it persists.
• Where it breaks: On the day of a resignation. Nothing is transferable, the successor restarts from zero, and the company pays again for knowledge it thought it had.
• Who it suits: Almost nobody, deliberately — but it is where most regional HQs actually are.

A full-time CIO or regional IT director hire

• What you get: Genuine ownership, full-time attention, and a person in the room for every decision.
• What it costs: A senior salary and package, plus recruitment time and the risk of a mis-hire in a small market.
• Where it breaks: Justification. At fifteen to twenty-five HQ staff the role is hard to defend to a parent company, tends to get filled at a more junior level than intended, and re-creates the single-point-of-knowledge problem in a more expensive form.
• Who it suits: Groups large enough that technology decisions are continuous rather than periodic.

A named virtual CIO with a documented roadmap

• What you get: A named, accountable strategic voice; a written, versioned, customer-owned roadmap; regular reviews tied to the budget cycle; and continuity that survives any individual's departure. Included in every Brocent managed IT plan tier.
• What it costs: Part of the managed IT plan, priced per user per month, rather than a separate senior headcount.
• Where it breaks: It is not a substitute for a day-to-day IT lead. Someone still has to run operations locally — the vCIO decides direction, not tickets. And it works considerably better where the same provider also delivers the managed service, because strategy written without operational data is guesswork.
• Who it suits: Regional HQs and mid-sized groups that need CIO-level judgement periodically rather than continuously.

Frequently asked questions

What does a vCIO actually deliver, concretely?

A written multi-year technology roadmap with sequencing and dependencies; a standing inventory of decisions in flight and decisions due; scheduled strategic reviews aligned to your budget cycle; and framing of technology spend in terms a board or parent company will accept. The test of whether a vCIO engagement is real is simple: at any point, can you open a current document that says where your technology is going and why?

How is this different from a managed IT account manager?

The account manager owns delivery — ticket flow, SLA performance, escalation, service reviews. The vCIO owns direction — what the estate should look like in three years and in what order to get there. They are different questions and, in our model, different people. A service review that only covers ticket volumes is not a strategy conversation, however useful it is.

How much does a vCIO cost compared with hiring a full-time CIO?

A named vCIO and technology roadmap is included in every tier of our managed IT plans, so the comparison is not really a like-for-like price. The alternative is a senior full-time salary plus recruitment cost and hiring risk, for a role that a fifteen-to-twenty-five-person HQ typically struggles to justify to its parent company. Plan pricing is published per user per month on the pricing page.

How many hours a month is a typical engagement?

It is structured around a review cadence and the decisions in flight rather than a fixed hour count. Quarterly strategic reviews are the usual baseline, with more contact during periods of concentrated decision-making — a migration, an office opening, a budget cycle, a change of IT staff — and less when the estate is stable. If you need a continuously present executive rather than a periodic one, that is a different engagement, and we will say so.

Does the roadmap survive if we change managed IT providers later?

Yes. Customer-owned documentation and credentials are standard in our plans, and the roadmap sits in that category. It is your document. We think that matters commercially as well as ethically: a provider who keeps your strategy hostage is describing their own lack of confidence.

Is this useful for a company our size?

If technology decisions in your HQ affect operations in more than one country, yes. The size that struggles most is precisely this one — large enough that decisions have real consequences across borders, small enough that a full-time CIO cannot be justified. Below roughly ten HQ staff with a single-country footprint, a good IT lead plus a competent provider is usually sufficient.

What happens during the transition if our current IT lead leaves?

That is the scenario this is designed for. Because the roadmap is written and the vCIO has continuity, a departure becomes a staffing change rather than a strategic reset. In practice the vCIO briefs the incoming lead on the roadmap and the reasoning behind each sequenced decision, which compresses onboarding from months to weeks.

Can we start with a vCIO without moving our managed IT to you?

We would rather be honest than accommodating here. Strategy written without visibility into real ticket data, patch compliance and incident history is a slide deck. We do engage that way occasionally, but the roadmap is materially better when the same provider sees the operational reality — which is exactly why we include the vCIO in the plan rather than selling it separately.

Where to go from here

The composite company in this article did not have a technology problem. Its estate ran, its team was competent, and its outgoing IT manager had made good decisions for nine years. What it had was an ownership problem: the most valuable thing IT produced — judgement about sequence and direction — was never captured in a form the company could keep.

That is a fixable gap, and fixing it is not primarily a spending decision. For most Singapore regional HQs, the first step is simply establishing whether a current, written roadmap exists, and who would be able to explain it if the person who wrote it were unavailable tomorrow.

If the honest answer is that it lives in somebody's head, that is worth changing before the resignation letter arrives. Our vCIO programme is part of every managed IT support plan, and the practical starting point is a conversation about what decisions your HQ currently has in flight. Get in touch and we will scope it.