Cases

We receive server passwords and access to client databases, so we always sign a non-disclosure agreement rather than waiting to be asked. There will be no names, no logos and no recognisable details here. What is left: the industry, the size, the essence of the task and the number at the end.

NDA
signed before the first access
6
projects broken down
Numbers
results in numbers, not in words
On request
we will introduce you to a current client

Six projects

Behind every example is real work. The only things removed are those that would identify the company: the name, the city, the turnover and the specifics of the product.

Discuss a similar task

Manufacturing, 140 workplaces

Goods-in stopped grinding to a halt

The handhelds kept dropping off the network deep among the racks, and receiving one delivery ate up a whole shift.

A radio survey
Measured with the racks full, not in an empty hangar
One network with a seamless handover
Access points in sealed enclosures
Sessions stopped dropping
Goods-in fits into a single shift again

A retail chain, 14 locations

One stock figure across all channels

The registers, the website and the marketplaces were counted separately, and mismatches only surfaced at stocktaking.

Sync with 1C
Stock and prices on a schedule, orders instantly
Connecting marketplaces
Reservation so an item cannot be sold twice
Manual reconciliation stopped
A discrepancy shows up the same day, not at the end of the month

A medical centre, 60 staff

The inspection passed with no orders issued

Work with health data had to be brought into line with the requirements of the law.

A survey and a threat model
We identified the set of measures needed
A document set
Orders, consent forms and the procedure for access to records
Role-based access and logs
A doctor sees only their own patients, and every record opened is logged
An emergency project

A wholesale company, 45 seats

Recovery in one day

Ransomware went through the file server and reached the network folder with the archives.

We brought up the surviving copy
Only part of a working day was lost
We rebuilt the backup scheme
A copy kept off the network, with its own password
A check every month
We restore the archive with a stopwatch running

A design bureau, 30 seats

A relocation without downtime

A relocation without stopping work, with heavy design files and a shared drawing archive.

The network was ready before the furniture
The request to the provider a month ahead, the cable laid in advance
The servers moved over the weekend
The backup was taken before dismantling, the start-up on Saturday
On Monday people simply sat down and worked
The engineer spent the whole first day in the office

A logistics operator, 80 seats

Moving to trusted software

Public sector customers demanded proof of where the software came from.

A software inventory
We found licences that were paid for but sitting unused
We trialled it in one department
Objections were caught before the general switchover
Two applications were left untouched
There is no replacement, so we moved them to separate machines

Why there are no names here

It is not about excuses or a shortage of clients but about the nature of the work itself.

We know too much about the client

Support means server passwords, access to accounting databases and access to data. Saying publicly whose infrastructure it is and how it is built harms the client first of all.

An agreement before the first access

The non-disclosure agreement comes in the same package as the contract rather than being signed on separate request. The ban also covers any mention that we work together.

What we offer instead

On request we will put you in touch with a current client from your industry, provided they do not mind. That is more honest than a picture on a website and far more useful when choosing.

A logo on a contractor's website says nothing at all about quality. It proves only that a contract was signed at some point. How the support went and how it ended cannot be read from a picture. Fifteen minutes with someone who works with us today tells you incomparably more.

How we measure the result

So the story does not boil down to «it got better», the number is recorded before the work starts.

01

We measure before we start

We record how things stand now: the number of tickets, the length of downtime, where the time leaks away. Otherwise there will be nothing to compare against later.

02

We agree on the number

We agree in advance what counts as a win: the handover date, the number of repeat failures, an inspection with no findings.

03

We do the work

We work in stages and you sign off each one. Interim results are visible along the way, not only at the finish.

04

We measure again

We compare with where things started. If the number has not moved we say so plainly and find out why.

Questions and answers

We will not, and that position will not change: the ban covers even mentioning that we work together. What we can do is put you in touch with a current client if they agree. That conversation is worth more than a wall of logos.

The surest way is to order a survey. It is free, takes five working days, and the report shows the level straight away: what was found, how it was described and in what order the fixes were proposed. A check on your own setup says more about competence than any stories.

Ask us outright at the first conversation and we will answer honestly. Limited experience in your field is not in itself a problem: infrastructure in most companies is built along similar lines. But if the task hinges on industry knowledge we do not have, we will say so before signing, not after.

Yes, on your template or ours, whichever suits. Many send it before the first call so they can speak about their problems freely. We are used to that and consider it sensible.

Tell us what your task is

Опишите положение дел, и мы прямо скажем, делали ли похожее и чем оно закончилось. Соглашение о неразглашении подпишем до разговора о подробностях.