Case studies

We work with client infrastructure, credentials and data, so a non-disclosure agreement is signed before work begins, always, not on request. We do not publish company names, logos or identifying details. Below are anonymised examples: industry, scale, task and a measurable result.

NDA
signed before work begins
6
examples from different industries
The numbers
the result is measured, not described
On request
references from current clients

Examples of our work

Every example is a real project. Only the details that would identify the company have been removed: the name, the city, the volumes and the specifics of what they make.

Discuss a similar task

A manufacturer, 140 workstations

Goods-in stopped grinding to a halt

Terminals kept losing the network between the warehouse aisles, and receiving a delivery stretched across a whole shift.

Wireless survey
A survey with the racking full, not empty
One network with seamless roaming
Ruggedised access points
Dropped sessions are gone
Goods-in was back within the shift target

A retail chain, 14 outlets

One stock figure across all channels

The tills, the website and the marketplaces each had their own records, and mis-picks were only found at stock count.

1C exchange
Stock and prices on a schedule, orders in real time
Connecting the marketplaces
Reservations so an item cannot sell twice
Manual reconciliation stopped
Discrepancies are visible immediately rather than at month end

A medical centre, 60 employees

The inspection passed with no orders issued

The processing of special-category personal data had to be brought into line with 152-FZ.

Assessment and threat model
The required protection level was determined
Document package
Governance documents, consent forms and rules for accessing records
Role-based access and logs
A doctor sees their own patients and every access is logged
An emergency project

A wholesale company, 45 workstations

Recovery within one day

Ransomware encrypted the file server and reached the network folder holding the backups.

The surviving backup was restored
Data loss was limited to part of a day
The backup scheme was rebuilt
An offline copy with independent access
A monthly check
Restores are tested and timed

A design bureau, 30 workstations

A move with no downtime

Changing offices without stopping work: heavy CAD files and a shared project archive.

The network before the furniture arrives
The provider order a month ahead, cabling installed in advance
The servers were moved at the weekend
With a backup before dismantling and start-up on Saturday
On Monday everyone sat down and worked
An engineer on site for the whole first day

A logistics operator, 80 workstations

Migration to registry software

A requirement on software origin when working with public sector counterparties.

Software inventory
Found paid-for licences that nobody used
A pilot in one department
Objections were collected before the full rollout
Two applications were kept
No equivalents, moved to isolated workstations

Why there are no names or logos

This is not an excuse and not a lack of clients. It follows from the nature of what we do.

We know too much

Supporting a company means access to its servers, accounting systems and data. Publishing whose infrastructure it is and how it is built is a bad idea for that client own security.

An NDA before work starts

The non-disclosure agreement is signed together with the contract, not when a client asks for it. It covers even mentioning the fact that we work together.

What we can offer instead of logos

On request we will arrange a conversation with a current client from your industry, if they agree to it. That is more honest than a logo on a website and more useful for your decision.

A logo on a contractor website says nothing about the quality of their work. It only shows that a contract was signed at some point, not how the service went or how it ended. A conversation with someone working with us right now tells you incomparably more.

How we measure the result

So that a case study does not become a story about things getting better, the metric is recorded before the work starts.

01

A survey before the start

We record the current state: how many requests, how long downtime lasts, where time is lost. Without that there is nothing to compare against.

02

Agreeing the metric

We decide in advance what counts as success: goods-in time, the number of repeat incidents, no regulatory orders.

03

The work

We work in stages with acceptance at each one. Interim results are visible along the way, not only at the end.

04

A repeat measurement

We compare against the starting point. If the metric has not moved, we say so plainly and work out why.

Frequently asked questions

No, and that will not change: the non-disclosure covers even the fact that we work together. But we can arrange a conversation with a current client if they agree, and that will tell you more than a wall of logos.

The most reliable way is the assessment. It is free, takes five business days, and the report shows our level straight away: what we found, how we described it and how we prioritised. That demonstrates competence better than any case study, because it is done on your own infrastructure.

Just ask us directly and we will answer honestly. If we have little experience in your particular field, that is not always a problem, because infrastructure is largely standard. But if the task requires industry knowledge we do not have, we will say so before the contract, not after.

Yes, using your template or ours, whichever suits. Many clients send the agreement before the first call so they can discuss their infrastructure and problems freely. We are used to that and think it is the right approach.

Tell us about your task

Describe the situation and we will tell you plainly whether we have done anything similar and how it ended. If needed, we will sign an NDA before discussing details.