Workstations Specified for the Work, Not the Benchmark
Custom workstations, servers and office fleets for Vietnamese businesses: specification against your actual software, genuine components, assembly and burn-in testing, on-site deployment and warranty handled by us.
A workstation is not fast or slow in the abstract. It is fast or slow at the thing you do. A designer waiting on renders, an accountant with a 200,000 row workbook and an engineer running simulations need three different machines, and the one that wins a gaming benchmark may be the worst of the three for all of them.
iGlobal specifies hardware the same way we specify software: starting from the workload. We ask what applications run, how many files are open at once, how large the working set is, and whether the bottleneck today is the processor, the memory, the disk or the network. Often it is the one nobody was planning to spend money on.
We also build fleets. Twenty identical office machines deployed with the same image, the same warranty terms and the same spare parts on the shelf is a different exercise from building one powerful box, and it is the one that saves an IT team the most hours over three years.
Where hardware money usually goes wrong
The most common waste we see is a large budget spent on the processor while the machine still waits on a slow disk, or a generous amount of memory in a system whose real constraint was single-thread performance. The component that gets the attention is rarely the component that is holding the work up.
The second is the invisible part of the bill of materials. A power supply and a cooling solution are where a builder saves money quietly, and they are exactly the two components whose failure takes the rest of the machine with it or shortens its life without anyone noticing why.
The third is warranty in practice rather than on paper. Thirty-six months printed on a box means little if a fault means your designer is without a machine for two weeks while a claim travels. What matters operationally is who hands you a working replacement tomorrow morning.
- Staff waiting on machines several times a day, every day
- Mixed hardware with no two machines quite alike to support
- No spare parts, so one failure means one person idle
- Warranty claims that cross three parties and take weeks
How we build and deliver
Specification from your workload
We ask which applications matter, measure where the current machines actually wait, and size the build against that. The recommendation comes with the reasoning, so you can disagree with it.
Genuine components with traceable origin
Serial numbers recorded per machine, distributor invoices available, no refurbished parts presented as new. You get the actual bill of materials, not a tier name.
Burn-in before it reaches your desk
Every build runs sustained load, memory and storage tests for several hours. Components that fail early fail here, in our workshop, rather than in your office in week two.
Standard image and deployment on site
Operating system, licensed software, domain join, printers and backup agent are all configured before delivery. The user sits down to a machine that is ready for work, not a setup wizard.
Warranty we administer for you
You raise one ticket with us and we deal with the distributor. For fleet contracts we hold spare units so a failure costs an hour of swap time instead of a week of waiting.
Upgrade path planned from day one
Cases, power supplies and motherboards are chosen with headroom, so year three is a memory and storage upgrade rather than a full replacement of machines that still work.
How we deliver it
-
1
Workload assessment 2 to 5 days
We review the software in use, the size of the files people work on, and where the current machines are waiting. For fleets we sample a few representative users rather than surveying everybody.
-
2
Specification and quotation 2 to 3 days
You receive a full component list with model numbers and the reason each part was chosen, usually in two or three tiers so the trade-off between budget and benefit is explicit.
-
3
Assembly and testing 3 to 7 days
Build, cable management, firmware updates, sustained load testing and the standard software image. Each machine leaves with a test report and its recorded serial numbers.
-
4
Delivery and handover 1 to 3 days
On-site installation, data transfer from the old machine where needed, a short handover to each user, and the asset list given to your IT or admin team in a form they can maintain.
Who this is for
- Design, architecture and media studios needing render and editing performance
- Engineering and manufacturing teams running CAD or simulation
- Offices refreshing 10 to 100 machines who want one standard build
- Companies needing an on-premise server for ERP, files or backup
Why iGlobal
We tell you where not to spend
A specification that moves budget from the processor to storage because that is where your work is waiting earns us less margin and earns you a faster machine. We would rather have the second conversation next year.
Tested before shipped, every unit
Burn-in is not an upsell here, it is part of the build. Infant mortality in components is real and it is far cheaper to catch it in our workshop than in your office.
Hardware and software from the same partner
When the ERP server, the network and the workstations come from one team, a performance complaint does not turn into three vendors pointing at each other.
The best balance of cost, quality, and service
Component-level transparency on price, genuine parts with traceable origin, and a warranty process we run on your behalf. You can compare our bill of materials with anyone.
Three ways to do this, compared
| What you are comparing | By hand, on spreadsheets | Off-the-shelf software | With iGlobal |
|---|---|---|---|
| How the components get chosen | Whatever the shop has in stock that day | A fixed configuration you are not allowed to alter | Specified against the work the machine will actually do |
| A part fails in the second year | Argue with the shop about which part is at fault | The whole unit goes back and the machine is gone for weeks | That one part is replaced while the rest keeps working |
| Upgrading in three years | Buy an entirely new machine and move the files | A sealed case with nothing the owner may service | Documented at build time so the next upgrade is planned |
| Cost across three years | Hidden inside salaries, so it never appears in a budget | A predictable licence per user, plus the work it cannot do | Quoted per phase and reviewed with you before each one starts |
| Who holds your data | Scattered across files, inboxes and personal phones | On the vendor platform, exported on the vendor's terms | Your own database, exportable in full whenever you ask |
| When something breaks | The person who built the file, if they still work here | A ticket queue, often in another language and time zone | A named engineer in Hanoi you can reach the same working day |
The two middle columns describe approaches that genuinely work for some companies. Where they win, they win, and we have tried to say so.
What changes after deployment
The benefit people quantify first is waiting time. A designer who loses twenty minutes a day to renders and file loads loses roughly eighty hours a year, which is two full working weeks. Hardware is one of the few line items where the payback can be calculated honestly on a single spreadsheet.
The benefit the IT team notices is standardisation. When every machine in the office has the same board, the same image and the same spare parts behind it, troubleshooting stops being research. A problem solved on one machine is solved on all of them.
Over three years the planned upgrade path does the quietest work. Adding memory and a second drive to a machine chosen with headroom costs a fraction of replacing it, and it extends the useful life of the fleet past the point where most offices have already bought everything again.
- Measurable reduction in time staff spend waiting on machines
- One standard build, so support and spares get simple
- Serial numbers and an asset list your team can actually maintain
- Failures covered by swap, not by a week of waiting
Frequently asked questions
Is a custom build really better than a branded workstation?
For a mixed office fleet, a branded machine with next business day service is often the right answer and we will say so. Custom builds win when the workload is specific, when you want the budget concentrated on one or two components, or when you need an upgrade path that branded chassis do not allow. We quote both when the choice is genuinely close.
How is warranty handled if a part fails?
You contact us, not the distributor. We diagnose, and if the part is faulty we handle the replacement claim while you keep working. For fleet contracts we hold spare units on site or at our workshop so the user is back at work the same day rather than waiting for the claim to complete.
Can you supply servers as well as desktops?
Yes. Tower and rack servers for ERP, file storage, virtualisation and backup, specified with redundancy where it matters and without it where it does not. If you are weighing an on-premise server against cloud hosting, we will work through the three year cost of both rather than assume one answer.
Do you handle the operating system and software licences?
We can supply and install licensed operating systems and office software, and configure a standard image so every machine in the fleet is identical. Where you already have volume licensing we deploy against that instead of selling you licences you do not need.
What lead time should we plan for?
For components held in stock locally, one to two weeks from order to delivered and configured. Specialist parts such as professional graphics cards or high capacity enterprise drives can add two to four weeks on import, and we tell you that before you sign rather than after.
Related solutions
Talk to a senior consultant, not a call centre
Tell us what you are trying to fix and we will tell you honestly whether we are the right team for it.