Area 17 · Data, AI and consulting

Consulting and audit

People come here before anything has been bought or signed. The hardware invoices are growing, every contractor has their own version of the truth, and there is nobody inside the company able to arbitrate. Our job is to translate what is happening into money and deadlines so it becomes clear what to tackle first and why.

2
services in this area
2-4 weeks
the usual time for the review
The document
with priorities and prices
None
obligation to continue

When people come for this

Bringing in outside experts is not worth it in every situation. Here is when it definitely pays off.

A large purchase or a launch

We check the choice before you pay. Otherwise you risk buying the wrong thing and redoing it at your own expense.

Changing contractor

We assess the state of things and the risks of a handover. Otherwise the system is accepted without documentation and you live with someone else's decisions.

The company is growing and branches are appearing

We prepare a development plan with headroom built in. Otherwise in a year everything hits the ceiling.

Costs are rising and the return is unclear

We revisit the spending and the priorities. Otherwise the money keeps going out of habit.

The contractors say different things

We compare the proposals on the table. Otherwise the choice is made on price rather than on the task.

Here we have a conflict of interest, and we are the first to say so. A contractor who first looks for problems and then sells the solution cannot be impartial by definition. We guard against that: the costs in the report are market rates rather than our own price list, and we do not object when a client takes the recommendations to another contractor.

How the review works

Most of the time goes on conversations rather than on inspecting servers. The root of the problems usually lies in how the company works, not in the specifications of the equipment.

01

Conversations with people

We interview the directors separately from the people who sit in the systems from morning to night. The gap between their accounts is often the main finding in itself.

02

We review the systems

We study the system diagram, the licence paperwork and the contract terms with your suppliers, and check how much knowledge lives only in one person's head.

03

We weigh it up and set the order

Every item gets two numbers: what the problem costs and what fixing it costs. The output is a sequence of actions rather than a wish list.

04

We go through the report in person

Sending the document is not enough. We sit down with the management and go through the report page by page, answering questions as we go.

Questions and answers

A survey takes inventory: what hardware, which licences, where the risks are. That is a technical census. This is about something else - choosing a direction - and we start from the company's plans rather than the state of the servers. Often one follows straight after the other.

That is usually how it starts. We talk to the owner or the finance director in terms of amounts and deadlines rather than acronyms. Everything technical goes into the appendices, where it belongs.

It happens. The most unpleasant case is when it becomes clear that the system paid for last quarter does not solve the problem. We will not soften it, but nor will we leave you alone with the bad news: we always offer several routes forward, including ones that salvage part of the investment.

We price by scale and depth: from two weeks to a month of work. The exact figure comes after the first call, when it is clear how many systems to review and how many people to interview.

Tell us what is going on

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