IT Maintenance Services in Singapore: AMC Pricing, Inclusions & SLAs (2026)

Short answer: An IT maintenance contract in Singapore, often called an AMC (annual maintenance contract), is a yearly agreement that covers a set of equipment or a set of visits. It is not the same as managed IT. Before you renew, check five things: what is excluded, what "response" means, who holds the administrator passwords, what happens when the one engineer is away, and whether the contract measures outcomes or only visits. Then compare it with the two other ways to buy IT support: a block of prepaid hours, and a per-user managed plan with a written SLA.

What does an IT maintenance contract in Singapore usually cover?

In Singapore, "IT maintenance" is how many small and mid-sized businesses describe what larger firms call managed IT. In practice the term covers a wide range of contracts. The common patterns are:

• Equipment-based AMC. A yearly fee for a list of devices, such as servers, switches, firewalls and a number of PCs. The vendor promises repair or support for those items.
• Visit-based contract. A fixed number of visits per month or per year, often with a named engineer, to handle whatever has accumulated.
• Retainer with hours. A monthly or yearly fee that includes a number of support hours, with extra hours billed at a set rate.
• Hybrid. A small fixed fee for monitoring or backups plus time-and-materials for everything else.

None of these is wrong. Each is a good fit for some businesses and a poor one for others. The risk is not the type of contract, it is the gap between what the buyer assumes is covered and what the contract says. If you are also comparing providers, our guide to IT support services in Singapore covers pricing, SLAs and provider types.

What do AMCs quietly exclude?

The scope section is short and the exclusions section is where invoices come from. Read the exclusions first. Items that are commonly excluded or billed separately include:

• Software and cloud. Microsoft 365 administration, licence changes, email problems and cloud applications.
• New equipment and projects. Setting up a new laptop, moving an office, adding a branch.
• Out-of-hours work. Evenings, weekends and public holidays, often at a multiple of the normal rate.
• Security. Antivirus management, patching, backup monitoring and incident response.
• Third-party vendors. Calls to the internet provider, the line-of-business application vendor or the copier company.
• Parts and consumables. Replacement hardware, cables and batteries.
• Recovery work. Restoring data after a failure may count as a project, not as support.

A contract that covers "hardware" but not "the things that break most often in your office" will feel expensive at the first bill. Make a list of the last twelve months of problems and mark each one covered, excluded or unclear.

What does "4-hour response" really promise?

Response is not resolution. A response time normally means that someone acknowledges the ticket, or an engineer starts looking, within that period. It does not promise the fault is fixed. Before you renew, ask:

• When does the clock start and stop? At the call, the email or when the ticket is logged? Does it stop at acknowledgement, at remote connection or on site?
• Which hours does it apply to? Business hours only, or also evenings and weekends?
• Is there a restore target? Some contracts include one, many do not.
• What are the consequences of a miss? Often there are none.

For a warehouse or a counter that stops working when the system is down, the difference between a response and a resolution is the difference between a quiet morning and a lost day. For reference, Brocent's published dispatch SLA options are normal business hours (P1 response in 2 hours, P2 in 4 hours, on site the next business day), extended hours 8×7 (1 and 2 hours, same-day on site) and 24×7 emergency (15 minutes and 1 hour, on site in 4 hours). These are described on the dispatch and on-site rates page.

What is the single-engineer risk?

Many Singapore SME maintenance contracts depend on one person. That works well until the engineer is on leave, ill, leaves the business or changes priorities. The questions to ask:

• Who covers when the named engineer is away? A written answer, with a name or a team, not "we will try".
• Where is the knowledge kept? Network diagrams, passwords, licence keys and the history of changes should be in a shared system, not in one person's head.
• What is the escalation path? If the engineer cannot solve it, who can?
• How are tickets recorded? A ticket history lets you see how often the same problem returns.

A team-based provider reduces this risk by design, because coverage, documentation and escalation are part of the way it works. The point is not that a one-person vendor is bad, it is that the contract should say what happens on the day that person is unavailable.

Who owns your credentials and documentation?

This is the question that matters most when you want to leave. Administrator passwords, domain registrations, firewall configurations, licence portals and backup consoles should all belong to your business, with the vendor holding delegated access. Check:

• Who is the registered owner of the Microsoft 365 tenant, the domain and the internet account.
• Where the passwords are stored, and whether you can see them.
• Whether the documentation belongs to you and what format it is in.
• What a handover looks like if you end the contract, and whether it is free.

If any of these is unclear, fix it before renewal rather than at exit.

What are the three ways to buy IT support?

The same business can be served three ways. Here they are side by side.

• Annual maintenance contract (AMC).
• *Best for:* a fixed set of equipment that rarely changes, such as a server and a few network devices.
• *You pay:* a yearly fee per item or per contract.
• *Strength:* predictable cost for repair.
• *Weakness:* it covers things, not outcomes. Anything outside the list is billed extra, and users have no direct entitlement.
• Block of hours (prepaid hours).
• *Best for:* occasional or irregular needs, or a business with a capable internal person who needs backup.
• *You pay:* a prepaid pack of hours, drawn down as used.
• *Strength:* you pay only for what you use, and the hours can cover remote and on-site work.
• *Weakness:* the cost is open-ended if demand grows, and nobody is accountable for prevention. Brocent's Token Service works this way: one token equals one hour of on-site or remote support, with 12-month validity and a one-time goodwill extension each contract year through your account manager. See the Token Service page and the token pricing.
• Per-user managed IT.
• *Best for:* a business whose staff depend on IT every day and that wants a written SLA, monitoring, patching and a help desk.
• *You pay:* a monthly fee per user, set by plan.
• *Strength:* predictable monthly cost, someone accountable for prevention and a service desk that all staff can use.
• *Weakness:* you pay for users, not for equipment, so it can look more expensive for a business with very few users and a lot of equipment, and cheaper for the reverse.

How do the numbers compare in Singapore?

The comparison depends on three numbers: how many users you have, how many hours of support you actually use and how much equipment you rely on. The current Singapore prices for Brocent's managed plans are in the table below, which is read from the same source as the pricing page and updates when prices change.

Plans are named Startup, Established, Growth and Enterprise and are sized by company headcount. For a 40- to 70-person distributor, compare the plan that matches your headcount with the cost of your AMC plus the extras you paid for last year.

For occasional on-site needs outside a plan, Brocent publishes a dispatch rate for Singapore of US$85 for the first hour and US$78 for each additional hour, for Level 1 end-user support with next-business-day response (2026 H2 price book, USD, tax exclusive). A three-hour visit is therefore US$85 plus two hours at US$78, which is US$241 at those reference rates. If you expect more than a couple of such visits a month, a plan or a token pack is usually cheaper than paying a dispatch rate every time. The dispatch rates page is the source of truth.

How do you do the arithmetic yourself?

Use last year's real numbers, not the proposal:

• Total AMC cost last year, including every extra invoice for work that the contract excluded.
• Number of incidents and how many were resolved on the same day.
• Hours of downtime for the people who could not work.
• Cost of the plan that fits your headcount, from the table above, over twelve months.

If the AMC plus extras is close to or above the plan price, the plan is the better value, because it adds monitoring, patching, backup oversight and a help desk. If your headcount is very low, equipment-heavy and rarely changes, a lean AMC may still be right.

What should you do 60 days before the renewal date?

Most auto-renewal clauses give a short notice window, so start early. A practical sequence:

• Day 60: collect the facts. Pull the contract, last year's invoices and ticket history. List every incident, who fixed it and how long it took.
• Day 50: mark the contract. Highlight scope, exclusions, response terms, the notice period and the exit clause. Note anything you assumed was covered that is not.
• Day 45: ask your vendor in writing. Send the five questions from this guide and ask for the cover plan for absences, the credentials list and the documentation.
• Day 35: request two comparison proposals. Ask for the same structure from each: scope, exclusions, SLA with hours and clock rules, ownership of credentials, term and exit. Put the same equipment and user list in each request.
• Day 20: compare on last year's numbers. Use real incidents and real extra invoices, not the proposals' headlines.
• Day 10: decide and give notice. If you move, agree the overlap and handover dates before you cancel the old contract.

How do you negotiate a better AMC if you decide to stay?

Staying is a reasonable outcome, and a renewal is the moment you have most leverage. Useful asks:

• Move common extras into scope. If Microsoft 365 questions and printer faults made up most of last year's extra invoices, ask to include them.
• Put the SLA in writing. Response hours, clock rules and a restore target for the systems that stop the business.
• Name the cover. A second person or team who knows your environment, with their contact route.
• Hand over the credentials list and a copy of the documentation now, not at exit.
• Shorten the term or add a break clause so that you are not locked in if service falls short.
• Agree a monthly or quarterly report of tickets, response times and recurring problems, reviewed with you.

A vendor that agrees to these is likely to be a good partner. One that resists them is telling you something about what the contract really covers.

How do block-of-hours packs work in practice?

A block of hours is a prepaid pool you draw down, usually in fixed increments. It suits a business that has a capable internal person and wants backup, or whose needs are irregular. Things to check in any block offer: what counts as one hour (remote and on-site equally, or different multipliers), whether hours expire and what happens to unused ones, who can raise requests, and whether the rate is lower for larger packs. Brocent's tokens count one token as one hour of on-site or remote support, are valid for 12 months and can be extended once per contract year through your account manager. The extension is a goodwill arrangement, not an automatic carry-forward, and not a refund.

When should a Singapore SME stay with an AMC?

Stay with an AMC when the estate is small and stable, the scope is clear, the exclusions do not matter to your operations, and the vendor has a documented cover plan. Move to managed IT when users depend on IT daily, when the extras make up a large part of the bill, when the contract measures visits rather than outcomes, or when you cannot say who covers the engineer's absence.

Case study: a building-materials distributor

*This is an illustrative example, not a named client.* A building-materials distributor in Singapore with about 55 staff, an office and an east-side warehouse, had an annual maintenance contract with a one-person vendor. At renewal the finance manager listed the previous year's issues. Most were Microsoft 365 and printing problems that the contract excluded, billed hourly. The warehouse system had been down for most of a morning while the engineer was on leave, and nobody could say who held the firewall password. The company asked three questions of every proposal: what is excluded, who covers absence and who owns the credentials. It moved to a per-user plan with a written SLA and kept the previous vendor for a few specialist tasks.

Frequently asked questions

What should an IT maintenance contract in Singapore include?

A written scope by equipment and service, an exclusions list, response and restore targets with the hours they apply to, a cover plan for the engineer's absence, ownership of credentials and documentation, a handover clause, and clear terms for renewal and exit.

Is a yearly contract cheaper than per-user managed IT?

Not necessarily. A yearly contract can look cheaper because the extras are billed later. Compare last year's total cost, including every extra invoice, with the plan price for your headcount.

What does a 4-hour response really promise?

Usually that someone will acknowledge the ticket or start work within four hours, not that the fault will be fixed. Ask when the clock starts and stops, which hours it covers and whether there is a restore target.

Who owns our administrator passwords?

You should. The tenant, domain and firewall accounts should be registered to your company, with the vendor holding delegated access. If they are not, ask for a transfer before renewal.

Can we keep our current vendor for some work?

Yes. Many businesses keep a specialist vendor for a line-of-business application or for a piece of equipment and move day-to-day support to a managed plan. Agree who handles what.

What happens to our documentation if we switch?

It should be handed over to you, in a usable format, as part of the exit terms. Ask for this in the contract and check that the documentation exists before you need it.

How long does a switch take?

It depends on the size of the estate and how well it is documented. A discovery and onboarding stage comes first, then a handover from the old vendor. Plan for several weeks and overlap the contracts so there is no gap.

Next steps

Read the plan details on the managed IT services page, check the dispatch figures on the dispatch rates page, and see how prepaid hours work on the Token Service page. For a comparison of managed IT and an in-house hire in Singapore, read managed IT vs in-house IT for Singapore SMEs. For a review of your current contract against these questions, talk to a consultant.