Consultancy
A sober second opinion, in writing
Independent technical advice for decisions that are expensive to reverse. We are not selling you a build when we advise, and we say so in every report.

Engagements
- Codebase review
- We read the code, configuration and hosting of an existing system and report on its condition: what is sound, what is fragile, what is risky, and what we would do first. Typically one to two weeks.
- Architecture review
- For a planned or growing system: whether the structure fits the expected load, team size and budget, and what simpler alternatives exist.
- Build or buy assessment
- For a specific need, we compare candidate products against a bespoke approach, including total cost over several years, lock-in and the work of adapting your process.
- Specification and tender support
- We help you write a requirement that suppliers can price fairly, then help you compare their responses.
- Technical adviser on retainer
- A few hours a month of access for a director or board who want an independent technical view on proposals and suppliers.
What a report looks like
Every consultancy engagement ends with a written report, usually ten to twenty-five pages, structured so that the first page alone is useful to a non-technical reader. It states the question, our answer, the evidence and the tradeoffs, followed by detailed findings for your technical staff. We present it in a call and answer questions.
Independence
If we recommend that you buy a product, we receive nothing from its vendor. If we recommend a build, we state clearly that NTKO could be one of the suppliers, and we encourage you to get comparison quotes. A review never assumes we will be hired to fix what it finds.