The principle that comes before the names
You will not find a wall of logos on this page, and that is a choice.
A list of prominent brands shifts attention onto the product, while the question that determines the outcome is a different one: which constraint that technology has to resolve in your company. Two businesses with the same number of workstations can need very different infrastructure, and the difference is not in the catalogue — it is in what an hour of downtime costs them.
The principle we follow is simple to state and uncomfortable to keep: the technology gets chosen after the constraint is understood, not before.
We are nobody’s sales channel
We supply hardware and software, but we have no sales targets to hit on a brand, and that changes the proposals in a verifiable way: the recommendation is often cheaper than the company was expecting, or the conclusion is that nothing needs buying at all.
In a channel tied to a manufacturer that almost never happens, and not through dishonesty: because anyone with a target on a brand sees problems in the shape that brand solves.
There is also a practical reason that shows up later. When a manufacturer changes licensing, prices or support policies — and it happens regularly — anyone tied to a single brand has to defend that choice. Anyone who is not redoes the calculation and offers you the alternative.
The areas we work in
The skills are divided by area, and the division matters more than any single certification: it means running your company never depends on one person being available.
- Systems and virtualisation — Microsoft and Unix/Linux environments, server virtualisation, consolidation and redundancy sized against the cost of downtime;
- Networks — design, cabling, equipment and segmentation, links between sites, wireless coverage designed from an on-site survey;
- Security — endpoint protection, firewalls, access control and incident response;
- Data protection — unalterable off-site copies with restore testing;
- Workstations and collaboration — centralised device management, productivity environments and telephony;
- Software — custom development and integration where no standard product covers the process;
- Compliance — GAPOFF, the compliance operations platform we built ourselves.
The four constraints that decide a technical choice
These are the questions we ask in every assessment, and the answers matter more than the product.
What does an hour of downtime cost? It is the number that determines how much redundancy is needed. Almost no company has calculated it, and once written down it makes obvious decisions that previously looked like opinions.
Which skills exist in the company? An elegant solution nobody internally can touch is one more dependency, not one fewer.
How much budget is there, really? Spread over how many years, and with what margin for the unexpected.
What is already there? The best solution in the abstract is rarely the best for a company that has already invested in something that works.
What we hand over, whichever technology we choose
Configurations, network diagrams, credentials and the history of work carried out stay documented and yours from day one, not handed over at the end as a courtesy.
It serves you, so you do not depend on us, and it serves the project: it makes a future migration a piece of planned work rather than a leap in the dark. It is also why a technical decision taken today closes no doors tomorrow.
The rest
See also the Xion method for the order in which we work and IT consultancy for the decision stage.
The first step
A consultant looks at the state of the infrastructure and says which constraints matter in your case, before naming any product. Free and without obligation.