Remote first, and what that actually means for a client
Working remotely where the job allows is not a compromise we ask clients to accept. It is how you get the person who is best at your problem rather than the one who is nearest.
Clients ask where we are based more often than almost anything else. It is a reasonable question and it is usually standing in for a better one: can you actually look after us, and how quickly can you get here if it matters.
We have staff around New Zealand and a partner network where we do not, and most work is done remotely. That is a deliberate design rather than a cost measure, and it is worth explaining what it buys and where it stops.
What it buys you
The right person instead of the available one. A firm serving one town assigns whoever is free. If your problem is an Odoo manufacturing configuration or a network segmentation design, you want the person who has done that, not the person who can be at your office by ten. Distance stops mattering the moment the work is not physical.
Faster on the things that are most common. The majority of what stops someone working is fixable remotely, and a remote fix starts in minutes rather than after a drive. Waiting for a van is often the slowest part of a local service.
Travel out of your invoice. Two hours of driving billed at an hourly rate buys you nothing. Removing that from the cost of routine work is not a discount, it is not charging you for something with no value.
Depth you would not get from a small local team. Nine service lines staffed nationally is a deeper bench than the same headcount serving one district.
Where it stops
We would rather be specific about this than imply everything is remote.
Installations are physical. Cabling, cameras, access control, racks and site connectivity all need someone there, and we go. Rollouts of new hardware, site assessments where the answer depends on the building, and commissioning work are all on site by nature.
There is also a category that is technically remote-capable and better done in person anyway. The first discovery on a complex operational site is one: walking a packhouse or a wharf with the person who runs it surfaces things that no amount of questioning over a call will. Segmenting an operational network is another, for the same reason.
We would rather turn up for those than pretend a call is equivalent.
The thing that makes remote work honest
Remote support is only better than local if the environment is set up so that most problems can genuinely be solved remotely. That means devices enrolled and reachable, monitoring in place, documentation current, and identity configured so access can be granted and revoked without somebody physically present.
That is the actual work behind the model, and it is why the first ninety days of an engagement matter so much. An environment nobody has documented cannot be supported well from anywhere.
The question worth asking instead of where we are
Not where is the office, but: when something breaks, who picks it up, how quickly do they start, and when work has to happen on site, who comes and how soon.
Those are answerable and checkable. A postcode is neither. We have deliberately not put a location on this site, because naming a town invites clients to work out whether they are near enough to be worth serving, which is the wrong question to be asking yourself about a firm that works nationally.
If you have a site that needs someone standing in it, tell us where and we will tell you plainly how we cover it.