Case studies

Representative engagements

Client names are withheld under commercial confidentiality. The engagements below are described by scope, constraint and outcome so you can judge whether the shape matches your own requirement.

01Network hardware

400G spine refresh for a regional colocation operator

  • Colocation operator
  • Southeast Asia
  • Live production fabric
  • Staged over one cutover window
  • Fabric class400G
  • Data halls2
  • Link failures at cutover0

The constraint

A colocation operator needed to lift its interconnect fabric to 400G across two halls, but the original bill of materials mixed transceiver codings that would not link against the installed switch platform.

What we did

We rebuilt the BOM against the actual platform inventory, replaced the mis-coded optics with validated equivalents, checked the optical power budget for the longest inter-hall run, and staged delivery so cutover consumables landed ahead of the switch chassis.

Outcome

A single validated BOM, compatibility confirmed in writing before purchase, and staged delivery that matched the cutover sequence instead of filling the loading bay in one drop.

What was supplied

  • 400G transceivers
  • Inter-hall single-mode links
  • Validated compatibility matrix
  • Cutover consumables
02AI tokens

Consolidating model spend for a regional software company

  • Software product company
  • Regional, multi-country teams
  • Existing workloads in production
  • Migrated without a service pause
  • Billing relationships4 → 1
  • Invoice currencyUSD
  • Usage attributionPer-project

The constraint

A product team was running four separate provider accounts on personal and corporate cards, with no per-project cost attribution and a finance team unable to reconcile foreign-currency charges.

What we did

We moved model access onto a single supply arrangement with consolidated USD invoicing, provisioned separate keys per project, and worked through which workloads could drop from a flagship model to a smaller tier without a quality regression.

Outcome

One invoice instead of four card statements, usage attributable to the project that incurred it, and a documented model-tier decision for each workload rather than a default to the largest model.

What was supplied

  • OpenAI-compatible endpoint
  • Per-project API keys
  • Consolidated USD invoicing
  • Real-time usage visibility
03AIDC advisory

Matching an AIDC requirement to a powered site

  • AIDC end-customer
  • Singapore and Malaysia
  • Defined capacity and timeline
  • Advisory engagement, no supply
  • Scoping approachDemand-first
  • Verified before shortlistPower + land
  • Counterparty introductionsDirect

The constraint

An end-customer needed regional AI data centre capacity on a defined timeline. Several sites were nominally available, but power availability, grid timing and land control did not line up with the requirement.

What we did

We worked through the demand specification first — capacity, density, cooling approach, timing and location constraints — then used our project and energy network to surface sites where power and land control were genuinely in place, and introduced the parties with the standing to transact.

Outcome

A shortlist grounded in verified power and land position rather than marketing availability, with introductions made directly between the demand side, the project party and prospective investors.

What was supplied

  • Written demand specification
  • Site and power qualification
  • Land control verification
  • Counterparty introductions

These case studies are representative of the scope and type of work we undertake. Commercial terms, client identities and figures are withheld or generalised under confidentiality obligations.

Also in scope

Requirements we take on regularly

Smaller than a case study, but the same process. If your requirement looks like one of these, it is a normal week for us.

  • Mixed-vendor optics matching

    Identifying validated transceiver equivalents for switch platforms already in production, with the compatibility position stated in writing before purchase.

  • Cluster cabling bill of materials

    Building the DAC, AOC and structured cabling list from rack layout and distance, rather than scaling a template from another site.

  • Switch refresh shortlisting

    Comparing H3C and Ruijie platforms against port count, uplink speed, buffer behaviour and budget, with the trade-offs written down.

  • Model cost review

    Working through which workloads genuinely need a flagship model and which run acceptably on a smaller tier, measured on your own prompts.

  • Token access for regulated buyers

    Moving model spend off personal cards onto a Singapore contracting entity with USD invoicing and per-project keys.

  • Site and power qualification

    Checking whether nominal capacity at a proposed AIDC site is supported by real grid timing and land control before it reaches a shortlist.

Your requirement will not match these exactly.

That is expected. Describe the constraint you are working against and we will tell you whether we are the right party for it.