Opening abroad: the IT chapter almost nobody budgets for

Market entry plans cover the legal entity, the tax position, the warehouse and the first hires. Almost none of them say who configures the network the day the equipment arrives, or which country that person is in. It is a small line item in euros and a large one in delays.

The scene that repeats itself

A Spanish or Czech company decides to open in Mexico, in Ohio, in Rotterdam. The plan is a good one: legal form chosen, local tax adviser retained, unit leased, two people hired, a three-year sales forecast. The opening date is in the calendar and customers have been told. Then, three weeks out, somebody asks who is going to install the network.

This is not a footnote. A six-person commercial office needs, in order to work on day one: a data line ordered and live, a comms cabinet with its router and switch, wireless coverage across the whole floor, a firewall configured to head-office rules, IP telephony with local numbering, and six laptops carrying the corporate build with access to the ERP, to mail and to shared files. None of that is technically hard. All of it, done 8,000 kilometres away and in another time zone, is.

Why it costs more abroad than it looks

You cannot courier an engineer — Equipment ships; two hours of somebody standing in front of a cabinet does not. And those hours cannot be planned precisely: the local carrier slips, the outlet is in the wrong place, a patch cable is missing. Whoever is on site has to be able to come back tomorrow.

Appointing a local supplier takes time of its own — Many will ask for an incorporated entity or a local tax number before they can invoice — precisely the thing still going through registration. And comparing three quotes in a language you do not speak, with no references and from a distance, is the kind of decision that ends up being made in a hurry.

Equipment crosses borders — Shipping ten pre-configured laptops from head office looks like the easy path until duties, customs clearance and warranty appear — and warranty is usually national. Buying locally is often better, but then the machines have to be configured locally.

Who you are handing the keys to — Whoever installs the network gets inside the systems, and with them the payroll, the customer list and the company mail. Obligations around personal data differ from country to country, but underneath whichever rules apply the question is the same everywhere: who are these people, what will they be able to see, and what do they commit to doing with it. Get it in writing before anyone plugs anything in.

What the delay costs

None of these four points sinks a project. Together they move an opening by three to six weeks. And an opening that moves drags the hiring, the first order and — if you are lucky, only this — your standing with the customer who already had the date in their calendar.

The local-hands model

The industry has a name for the answer: hands and feet. Instead of sourcing a supplier country by country, you contract a firm that maintains a field-engineer network spread across the world and dispatches whoever is closest, with their toolkit, laptop and console cables. One contract, one point of contact, the work done on site and in the local language.

What surprises people new to the model is the lead time: about a week of notice is usually enough to have a qualified engineer at the door in almost any city with an airport. You do not need to open a branch for that.

It is not the answer to everything. If the operation is going to be large from the start, or the business is technology-intensive, your own team in-country pays off sooner. The model covers the stage at which your own structure is not yet justified — which is usually the longest one.

Where it fits best

The pilot opening — One office, six people, and no way of knowing yet whether that becomes sixty in two years or closes. Standing up your own IT function for that does not pay.
Multi-site rollouts — Retail, logistics, points of sale. Fifty stores with the same installation repeated is a coordination and time-zone problem, not an engineering one.
What comes after — The part nobody plans: the switch that dies on a Tuesday in August at the subsidiary, with the systems manager three time zones away and nobody on site who can open the cabinet.

Six questions before you sign

Is there real coverage in this specific country? — "Global presence" is not an answer. The question is whether there is an engineer available in that city, and with how much notice.
What service level is committed in writing? — The usual tiers are four-hour response, eight-hour, next business day, or scheduled visits. They price differently, and buying the fastest "just in case" is money thrown away. What matters is that it is written down and says what happens when it is missed.
Who is liable when something breaks? — Where there is subcontracting — and there almost always is — who carries the responsibility towards you, and with what cover.
Which certifications do they hold, and are they current? — ISO 9001 for process quality and ISO 27001 for information security are the reasonable minimum when someone is going inside your systems. ISO 20000 adds service management. Ask for the certificate and its expiry date, not the logo on the website.
What will they have access to, and what do they sign about it? — They are going inside your systems. A serious supplier will tell you unprompted which of their people get access, with what permissions and when those are revoked — and will put it in writing. One who improvises the answer has not done this before.
What language does the engineer on site actually work in? — It sounds minor. It is not, when you are explaining down a phone line which cable goes where and the office opens on Monday.

Where this belongs in a market entry plan

At ZuzanaOPP we see IT infrastructure as a line item in the plan, with an owner and a date, alongside incorporation and the first employment contract. Not because it is the most expensive part — it rarely is — but because it has the least flexible deadline: the day the office opens, either the network is there or it is not.

In practice that means three things. That the line item enters the calendar at the start, not three weeks out. That the six questions above get asked by us, in the supplier's language and with the three quotes side by side. And that delivery is handled by someone who has already done it in that country.

Who delivers

IT Global Services — For that last part we partner with IT Global Services, a firm specialising in IT infrastructure deployment and support: networking, wireless, firewalls, IP telephony, cabling, end-user computing and cloud.

Coverage and lead times — They maintain a field-engineer network spread across the world, with centres in Europe, the United States and India and support 365 days a year, and they work to the four standard service tiers, so each site buys the one it needs rather than the most expensive by default. They have delivered in Spain, Czechia, Poland, Germany, France, the Netherlands, the United Kingdom, Mexico, Brazil, China, South Korea, Singapore and Canada, among others.

Certifications and volume — They hold ISO 9001 for process quality, ISO 27001 for information security and ISO 20000 for service management — precisely the three certifications we suggest asking for above. On the company's own published figures, the network exceeds 90,000 certified engineers, with more than 7,500 network deployments and 3,200 wireless deployments delivered.

Preparing an opening? Write to info@zuzanaopp.com and we will go through this part with you before it becomes urgent. Where it makes sense, we coordinate the technical side ourselves.

ZuzanaOPP works with IT Global Services as its commercial representative in Europe.