IT services: when what a company already runs stops being enough

Infrastructure is not replaced because it is old. It is replaced when it stops being enough — and that always has a cause outside IT. A second site opens. Dozens of people join in a year. The company starts doing something it did not do before. Only then does somebody count the links, the licences, and how much of what actually runs is still covered by the current contract.

That cause sets the pace. A company that has signed a lease on a new hall has a deadline: on opening day the network works. A company with ageing hardware has no deadline and will not have one for two years. The first talks to you this quarter; the second asks for a quote and files it.

The window also closes faster than in project sales: a decision about day-to-day support is made low in the organisation and without a committee. It goes to the provider who got in touch while the problem was fresh, not to the one with the better rate card three months later.

• A new location or facility. The strongest signal here, and the only one with a hard date. A new plant, warehouse, office or branch means cabling, a connection, access points, workstations and accounts — all at once, all for one particular day. A company announcing it has a problem to solve before the first pallet arrives.
• Headcount growth. Every new person is a device, an account, a licence, a backup, and somebody who issues and revokes all of it. Slower than a new site, but more durable: this is what pushes a company past the point where one administrator stops keeping up and ad-hoc help stops being cheaper than a contract.
• Registry and PKD changes. An added activity code describes something the company was not doing before — online sales, manufacturing, work that means holding somebody else's data. That brings new systems and new risk. The entry is public and dated, so you see not only that it happened but when.
• Revenue growth. Late in other segments, on time here: infrastructure is bought out of money that has already arrived, not out of a plan. A company that has visibly grown usually runs an environment assembled for its previous size, and finally has the budget to tidy it up.

A sketch of a single entry, without a name — the names come from what a run finds against your own offer.

The company: a distributor with one warehouse, at the size where there is a full-time administrator but no IT department. Why it fits: the profile read from your site says you serve multi-site companies in this region, with warehouses and shift work — and this one is about to stop being single-site.

Why now: an announcement of a second facility with a stated opening date, and headcount growth confirmed across consecutive months. The evidence: every why-now sentence carries a link to the page it was read from, and a date — a sentence without a link never reaches the list. The company is identified by its entry in the public REGON register, which also carries the KRS number, never by anybody's name.

The entry carries a score and a rank; a run ranks at most 40 companies, so the list can be read in one sitting. The whole thing reaches you within an hour of the run being paid for — automatically, with no queue in between.

The profile is built from your own site: what you support, under what model, across what area, and at what size of environment the work pays for itself. That usually means companies large enough to have something to manage and somebody to decide about it, and small enough not to be building a department of their own. Geography matters here too: if you drive to the client, the radius is a criterion, not a preference.

The exclusions matter more than the criteria, because they remove most of what merely looks like a fit. Sellers here usually exclude: other IT service providers and integrators, who run their own environments; micro companies, where a support contract cannot pay for itself on either side; subsidiaries of international groups whose infrastructure is run centrally from abroad; companies with a large internal IT department; public institutions, unless you bid in tenders; and the clients you already support.

You see that profile and correct it before you pay, and before the expensive part — the market research — begins. The finished list is then checked against the profile's own exclusions by rule rather than opinion, and an entry that trips one is held back instead of landing in front of you.

Frequently asked questions

Nearly all of these companies already have an IT provider. What is the list for?

Because a support contract is rewritten when it stops matching the size of the business, not when it expires. A new facility, headcount growth or a new activity in the registry are the moments when somebody on the client's side prices the whole thing again anyway. The run shows you where such a moment has just happened, with a link to the source and a date.

Where do registry changes come from, and what do they actually tell me?

From the public REGON register, which also carries the KRS number. An added or changed PKD code says a company is starting to do something new, and it arrives with the date of the entry. The code alone is not a reason to call — it becomes one when the new activity needs something the current environment cannot support. That is why it always appears on the list next to whatever explains it.

Read next

• Buying signals
• ERP and CRM vendors
• Start a run