Soluticom
Operator
Soluticom
Document
Clients
Sheet
1 of 1
Ref
clients
Coverage
EU
Section 00Position

Who we work with

We do not publish a wall of client logos. Most of the organisations we work with treat their infrastructure suppliers as internal information, and the ones that do not are rarely the ones worth quoting. What we can describe is the shape of the work.

References. Named references, including a direct contact who will take a call, are provided on request once a project is real — with that client’s consent, and normally at the shortlist stage rather than in a first email.

Section 01Sectors

Where the work comes from

Hosting and colocation

Providers refreshing a fleet, adding a hall, or standardising on one build across several sites. Usually repeat orders of an identical configuration, where the as-built document matters more than the price of any single line.

Software companies on their own hardware

Teams that have run the arithmetic on cloud spend and decided to own the base load. They need the specification questioned, not agreed with.

Industry and manufacturing

Plant systems, virtualisation clusters and on-premise storage where the constraint is downtime, not budget, and where a migration window means a production stop.

Public sector and research

Procurement against a published specification, with the documentation trail an audit will ask for. Slower, more paperwork, and entirely predictable.

Section 02Engagements

What a typical engagement looks like

Sizes vary, but the work falls into a few recognisable shapes. These are the engagement types we quote for — not case studies of particular customers.

  • Type A

    Single rack refresh

    Twelve to twenty nodes, top-of-rack switching, one storage tier. Specification and quotation in a week, build in two to three, one installation weekend, then a three-year support term. The most common job we do.

  • Type B

    Migration with rental overlap

    New platform bought, old platform kept alive, and rented capacity covering the months when both have to run. Ends with a decommission of the old estate and a credit for what it was worth.

  • Type C

    Compute build-out

    Accelerator nodes with the power, cooling and network design that has to exist before they arrive. Long lead times, staged delivery, and a schedule that is honest about which dates are confirmed and which are estimates.

  • Type D

    Estate survey and support takeover

    An inventory of hardware someone else supplied, an assessment of what is worth covering, and a spare pool built for what remains. Often the first job with a new client, because it is the one that costs least to get wrong.

Section 03Working with us

What you can expect

  • A written bill of materials before a price, and a price that names its source per line.
  • One counterparty for purchase, build, delivery and warranty.
  • An as-built document for everything we hand over.
  • A direct number for the person who did the build, not a ticket queue.
  • A refusal, in writing, when what you have asked for is the wrong answer.

Start a conversation