// consulting

Independent technical advice, with the reasoning attached

IT consultancy is this company's registered principal activity — EMTAK 62201, filed with the Estonian Business Register. Architecture review, technical due diligence, build-versus-buy analysis and delivery diagnosis.

An advisory engagement here produces a document, not a slide deck with a recommendation on the last page. We read the system, the constraints and the commercial situation, then write down what we found and what we would do — with the reasoning, so that you can disagree with it on the merits rather than on trust.

The questions that bring people here are usually blunt ones. Is this platform worth extending or should it be replaced. Is this vendor proposal technically sound or expensively vague. Why does delivery keep slipping when everybody is working hard. What would it take to survive the audit that is coming.

We hold no reseller agreement and take no vendor commission or referral fee, which means "buy nothing, fix the process" is an answer we can afford to give. It is more common than you might expect.

Distributed services. Independent deployables behind one contract, with an event backbone where coupling would otherwise return.

Distributed services — components

  • Clients
  • API gateway
  • Identity service
  • Orders service
  • Billing service
  • Event backbone
  • Service databases
  • Observability

Distributed services — connections

  • Clients connects to API gateway
  • API gateway connects to Identity service
  • API gateway connects to Orders service
  • API gateway connects to Billing service
  • Orders service connects to Event backbone
  • Billing service connects to Event backbone
  • Identity service connects to Event backbone
  • Event backbone connects to Service databases
  • Event backbone connects to Observability

How we approach it

Agree the question before answering it

Half of advisory work is finding out what is actually being asked. We write the question down and get it confirmed before spending your budget on the wrong one.

Read the primary sources

The repository, the pipeline, the incident history, the tickets and the people doing the work — not a summary of them. Second-hand descriptions of a system are how a review reaches a confident wrong conclusion.

Separate finding from opinion

What we observed, what follows from it, and what we would do are three different sections. You should be able to accept the findings and reject the recommendation.

Hand over something usable

A written report in language your board and your engineers can both read, and the underlying notes if you want them. You own it — including the right to show it to a competing supplier.

Working principles

  • The scope of an advisory engagement is days or weeks, with a defined end. We do not sell open-ended retainers.
  • A recommendation to change nothing is a valid outcome and gets written down as readily as any other.
  • We disclose any interest that could look like one, in writing, before an engagement begins.
  • We do not accept commission, rebate or referral fees from any vendor we might mention.
  • Findings are ranked by consequence, not by how alarming they sound.
  • Everything is written on the assumption that your auditor or your acquirer will eventually read it.

Outside the scope of this work

  • We are not a certification body and cannot make anyone compliant with a standard by writing a report.
  • We are not lawyers and nothing we write is legal advice, including on data protection.
  • We do not act as an accredited auditor for any framework, and we do not sign audit opinions.
  • We do not provide consumer technical support, account recovery or device unlocking — those are not consultancy, and we do not do them at all.

// catalogue

The services in this area

Each one lists its deliverables, its typical technology and — deliberately — what it does not cover.

IT Consultancy & Technology Advisory

The registered activity this company has filed since 2015: independent technical advice for organisations deciding what to build, what to buy and what to stop.

  • Architecture review
  • Technical due diligence
  • Threat modelling
  • C4 modelling
  • ADRs
Read the detail

Dedicated Engineering Capacity

Named engineers working inside your process, on your backlog, under a written contract — for organisations that need capability rather than a finished project.

  • TypeScript
  • React
  • Node.js
  • PHP
  • Java
Read the detail

No prices on this page, or on any other

Advisory engagements are scoped in days and quoted in writing after the question is agreed. We publish no day rate here, because a rate without a scope tells you nothing you can plan against.