Too Small for a Full IT Contract, Too Big to Wing It: A Hong Kong Boutique Agency's Token Story

A composite scenario, not a named client: an 11-person Hong Kong design agency had been getting IT help from "whoever's cousin knows computers" for three years, and it worked — until a laptop died the week of a client pitch and there was no one to call who actually knew the setup. This is what pay-as-you-go, token-based IT support is built for: continuity without a contract sized for a company you're not.

Hong Kong's Boutique Agencies Have a Real IT Need — Just Not a Standard One

Walk into most Hong Kong managed IT service provider (MSP) sales conversations as an 8-to-15-person creative agency, boutique consultancy, or small trading office, and the pitch you get back is built for a company you aren't. Standard managed IT plans are priced per user per month, and they're built around a specific assumption: enough employees, enough devices, and enough recurring tickets that a fixed monthly fee for 24/7 monitoring, patch management, a managed firewall, and a named virtual CIO makes economic sense against the volume of work.

At 11 people, that assumption doesn't hold. A boutique agency's IT need is real — laptops fail, Wi-Fi drops during a client call, someone falls for a phishing email, a new hire needs a machine set up in a hurry — but it's irregular. Maybe three or four things go wrong in a slow month, and maybe nothing does. Paying a fixed per-user fee every month for 24/7 network operations centre monitoring and continuous endpoint management is paying for infrastructure sized for a 50-person office, when what an 11-person office actually needs is: someone competent, on call, who already knows the setup, without a subscription running in the background whether anything breaks or not.

This isn't a hypothetical gap. It's the exact space between "we're too small for a contract" and "we're too big to keep winging it" that a lot of Hong Kong's smaller professional and creative firms sit in — and most IT support marketing simply doesn't address it, because the standard managed-services pitch has one dial (headcount × monthly fee) and no setting for "occasional, but real."

The Scenario: No Dedicated IT Relationship, No Institutional Memory

Picture an 11-person design studio in Hong Kong — five designers, two account managers, an office manager who also does bookkeeping, a couple of junior staff, and the two founders. For three years, IT has been handled the way it is at a lot of small agencies: whoever in the office (or in someone's family) is "good with computers" gets asked first. When that doesn't work, someone searches for a nearby repair shop or asks a freelancer they found through a referral.

It has, mostly, worked. Laptops get fixed eventually. The office Wi-Fi gets rebooted when it drops. Someone reinstalls Office when a license expires. None of it is elegant, but for three years nothing has gone wrong enough to force a change.

Then a senior designer's laptop dies — not slows down, not glitches, actually won't boot — three days before a pitch deck is due to a prospective client. The office manager calls the usual contact. He's traveling. She tries the backup option, a freelancer who helped once eighteen months ago; he doesn't remember what was installed on the machine, doesn't have any record of the studio's file structure or software licenses, and needs the better part of a day just to get oriented before he can start diagnosing the actual problem. The pitch deck gets rebuilt from a partial backup on someone else's machine, finished late, and the studio makes the meeting — barely. Nobody at the studio walks away from that week thinking the ad hoc approach is fine anymore. But nobody thinks a full monthly MSP contract, priced for a 50-person office, is the right fix either.

What "Ad Hoc IT Help" Actually Costs a Small Agency

The laptop failure is what makes the problem visible, but it isn't really the problem. The problem is what ad hoc IT support structurally can't provide, no matter how skilled the person you call happens to be:

Every incident starts from zero. Whoever you reach — a cousin, a freelancer, a different repair shop each time — has no record of what's installed, how the network is configured, what software licenses exist, or what's already been tried. They're troubleshooting a stranger's setup every single time, which means even a simple fix takes longer than it should, and a genuinely complex one can take days.

Help is unavailable exactly when you need it most. Ad hoc support means whoever you know happens to be free right now. There's no SLA, no guaranteed response window, and no backup contact if your usual person is traveling, sick, or has simply moved on to a different client. The moments IT problems tend to strike — the week before a pitch, the day before a launch — are the same moments a favor-based contact is least likely to be reachable.

Nobody owns security or backup discipline. With no ongoing relationship and no one accountable for the studio's IT posture between incidents, nothing gets checked proactively. Backups don't get verified until the day they're needed and don't work. Old software doesn't get patched until it's actively the entry point for a problem. There's no one whose job it is to notice any of this before it becomes an emergency, because nobody's job includes it.

A full MSP contract's per-user pricing doesn't make sense at this headcount. The flip side of the ad hoc problem isn't necessarily a standard managed IT contract — it's a contract built for a company several times this size, sold at a price point that assumes call volume this office will never generate. Paying every month for continuous monitoring infrastructure sized for dozens of endpoints, when the studio has eleven, isn't a fix for the actual problem — it's over-buying to solve a continuity problem that a smaller, correctly-sized commitment can solve on its own.

It's also worth being clear about what "irregular" actually means here, because it's easy to assume a small office's IT problems average out into something predictable if you just look at a long enough time window. They don't, in practice, because the issues that matter most at this size aren't the routine ones — they're the rare, disruptive ones that land at the worst possible moment. A studio might genuinely go six or eight weeks without anything breaking, then have a laptop die and a phishing attempt land in the same week a client renewal is due. Averaging that out into "roughly one incident a month" doesn't make the bad weeks less disruptive, and it's exactly the kind of variance a fixed monthly retainer is priced to absorb for a much larger client base — one an 11-person studio is, in effect, subsidizing without generating anywhere near the ticket volume to make that math work in its favor.

Brocent's View: A Monthly Contract Isn't Always the Right-Sized Commitment

The honest answer for a company at this headcount usually isn't "you need a full managed IT contract, just make the pitch work harder." It's that a monthly subscription is the wrong shape of commitment for irregular, real IT need — and the right answer is prepaid, pay-as-you-go support hours from a team that already knows your environment, purchased once, drawn down only when something actually happens.

That's what Brocent's Token Service is built for: it solves the actual problem this studio has (continuity — someone who already knows the setup, reachable within a defined response window) without solving a problem it doesn't have (round-the-clock network monitoring at eleven people, which is infrastructure this office simply doesn't need yet). It isn't a scaled-down managed IT plan. It's a different shape of commitment, sized to how often things actually break rather than to a per-user formula built for a much larger office.

How Token-Based IT Support Actually Works

The mechanics are deliberately simple, and every detail below is exactly how Brocent's Token Service is documented — nothing here is an approximation.

You buy a block of prepaid hours, not a subscription. One token equals one hour of on-site or remote IT support. You purchase a pack of tokens up front for the zone (market) you need coverage in — Hong Kong, in this studio's case — with a minimum first purchase of 20 tokens per zone. There's no monthly bill, no per-user fee, and no ongoing commitment beyond the pack you've bought.

Tokens don't expire the moment the month ends. A token pack is valid for 12 months from the date of purchase, and if there's a balance left over when that year is up, a one-time goodwill extension is available through your account manager each contract year. You're not racing a calendar to "use it or lose it" every 30 days the way you might feel pressure to under a subscription.

Raising a ticket works the same way it would with any help desk. You send a request to Brocent's Global Service Desk describing the issue and its urgency. During normal business hours, tickets are handled under Same Business Day (4-hour or 6-hour) or Next Business Day response tiers depending on urgency; for anything that genuinely can't wait, a 24×7 emergency tier gives a 4-hour onsite response any time, including nights, weekends, and public holidays. On-site work is billed in whole-hour tokens (minimum 2 tokens in business hours, more outside them); remote support is billed in 15-minute blocks, four of which equal one token, so a 20-minute remote fix doesn't cost the same as a two-hour on-site visit.

There's a paper trail, not just a memory. Every completed job produces a signed service report documenting what was actually done, and you receive a weekly token balance statement plus a low-balance alert before you're at risk of running out unexpectedly. That written record is what an ad hoc arrangement can never produce — a documented history of every past ticket that the next person handling a request can actually reference, rather than starting cold.

An account manager, not a rotating cast of strangers, owns the relationship. While Brocent doesn't guarantee the identical individual engineer on every single dispatch (staffing a global service desk across 100+ countries means the specific technician assigned depends on availability and location), the account relationship — and the documented ticket history behind it — is what replaces the "whoever's cousin is free today" model with something an agency can actually rely on.

It's honestly sized, not a workaround. A monthly per-user MSP plan bundles in continuous monitoring and proactive management that makes sense once ticket volume is high enough to justify it. Token Service doesn't include that layer — it's specifically for offices whose IT need is real but occasional, which is exactly the studio in this scenario. As the studio grows and starts raising several tickets a week rather than a handful a month, that's the point where a fixed monthly plan starts to make more economic sense than continuing to draw down tokens — and that's a decision the studio gets to make deliberately, on its own timeline, not one an ill-fitting contract forces on it early.

Getting Set Up

None of this requires a lengthy sales process sized for a much bigger deal. A studio in this position would typically start with a conversation about ticket volume and urgency — how often things actually break, and whether any of it is genuinely time-critical — to figure out roughly how many tokens make sense for a first pack, then buy that first 20-token minimum for the Hong Kong zone. That conversation is also where a studio finds out, honestly, if it's already past the point where tokens make sense — if the ticket volume described sounds more like several issues a week than a handful a month, the more useful answer might be to look at a managed IT plan from the start rather than buy a token pack that would be exhausted within weeks. From there, managed IT support more broadly, and the underlying managed services that sit behind it, remain there for later if and when the studio's needs actually grow into them — but nothing about starting with Token Service requires committing to that path before it's real.

Frequently Asked Questions

How is this different from calling a freelancer?

The mechanics look similar on the surface — you reach out when something breaks — but the difference is what stands behind the relationship. A freelancer found ad hoc has no ongoing accountability to you, no documented ticket history, no defined response-time commitment, and no backup if they're unavailable. Token Service comes with a defined SLA (same-business-day or 24×7 emergency tiers, depending on urgency), a signed service report after every job, and an account manager who owns the relationship — none of which a one-off freelancer arrangement provides by nature.

Do unused tokens expire?

Tokens are valid for 12 months from the date you purchase the pack. If you still have a balance left when that year is up, a one-time goodwill extension is available each contract year through your account manager — it isn't a hard "use it or lose it" cutoff the moment the year ends.

What happens when we outgrow token-based support?

There's a genuine crossover point, and it's honest rather than a sales trigger: once you're raising more than roughly four tickets a month, a fixed per-user managed IT plan typically starts to cost less than continuing to burn through token packs, because at that ticket volume you're also getting real value from the 24/7 monitoring and proactive management a subscription plan includes. Below that volume, tokens usually remain the better-fit, lower-cost option. Either way, it's a decision to make when the numbers actually support it, not one a contract locks you into early.

Can tokens cover urgent same-day issues?

Yes. During normal business hours, Same Business Day response (4-hour or 6-hour, depending on the ticket) is available, and for anything that can't wait for business hours, the 24×7 emergency tier provides a 4-hour onsite response at any time — nights, weekends, and public holidays included. Emergency and after-hours work does draw down tokens faster than a routine business-hours ticket (the per-hour token rate rises in the evening, at night, on weekends, and on public holidays), which is worth factoring into how many tokens you buy up front if urgent issues are a real possibility for your business.

Is there a minimum purchase?

Yes — the first purchase in any zone (market) is a minimum of 20 tokens. That isn't a hidden catch; it's published up front, and it's a genuinely small commitment compared to a year of monthly per-user MSP fees. There's no ongoing minimum beyond that first pack — you simply buy another pack when your balance runs low.

What if we need more hours mid-month?

Because tokens are a prepaid balance rather than a subscription tied to a monthly billing cycle, you can purchase another pack whenever your balance is running low — there's no need to wait for a renewal date or a new contract term. The weekly token balance statement and low-balance alert exist specifically so you see it coming rather than finding out mid-emergency that the balance is at zero.

Ad-Hoc Help, a Full MSP Contract, or Token-Based Support: Which Actually Fits an 11-Person Agency?

Ad-Hoc Freelance Help

• Cost: Usually the cheapest option per incident, with no upfront commitment.
• Continuity: None. Every incident starts from zero with whoever you can reach.
• Availability: Whoever you know happens to be free — no SLA, no guaranteed response window, no backup contact.
• Security and backup discipline: Nobody owns it between incidents; nothing gets checked proactively.
• Best fit: A company that genuinely has IT needs so rare that even occasional discontinuity is an acceptable trade-off.

A Full Managed IT Contract

• Cost: A fixed monthly fee per user, priced against continuous monitoring and management infrastructure — the same price whether anything breaks that month or not.
• Continuity: Strong — 24/7 monitoring, a named virtual CIO, and proactive management by a team that already knows your environment.
• Availability: Defined SLA response windows and continuous coverage, built into the plan.
• Security and backup discipline: Owned continuously — monitoring, patching, and a managed security baseline included at every tier.
• Best fit: A company generating enough ticket volume (Brocent's own token-vs-plan guidance points to roughly 4+ tickets a month) that continuous monitoring and a fixed monthly fee are the more economical shape of commitment.

Token-Based Support (Brocent's Token Service)

• Cost: Prepaid, pay-as-you-go — you buy hours in advance (minimum 20 tokens per zone) and only draw them down when something actually happens; no per-user monthly fee.
• Continuity: An account relationship and a documented ticket history — every job produces a signed service report, so the next person handling a request isn't starting cold, even without a guarantee of the identical engineer every time.
• Availability: Defined SLA tiers — Same Business Day (4-hour or 6-hour) during business hours, and a 24×7 emergency tier with 4-hour onsite response for anything urgent.
• Security and backup discipline: Not included as continuous monitoring the way a managed plan provides it — Token Service is for responding to real, occasional issues, not for round-the-clock proactive infrastructure management.
• Best fit: A company whose IT need is real but irregular — too small for a per-user contract to make economic sense, too big to keep relying on ad hoc, favor-based help.

For an 11-person Hong Kong agency, the honest answer is rarely "you need a bigger contract." It's usually that the commitment needs to be a different shape entirely — sized to how often things actually break, backed by a documented history instead of institutional memory that walks out the door with whoever helped last time. That's the gap Token Service is built to close, not by scaling a managed IT plan down, but by offering a genuinely different kind of commitment, correctly sized from the start.

Brocent has been providing IT support and managed services across Asia since 2007, with its headquarters in Singapore since 2021 and a Hong Kong office serving the local market since 2016 — the same Global Service Desk, account-management structure, and SLA framework behind Token Service also underpins Brocent's full managed IT plans for companies that do reach the point where a monthly contract becomes the better fit.

If ad hoc IT help has stopped being reliable enough for your agency but a full monthly contract still feels like the wrong size, get in touch to talk through your actual ticket volume and find out whether Token Service, a managed IT plan, or something in between is the right starting point.