Bespoke software & technical consultancy NTKOLimited · Wembley Begin a conversation
Plum-veined marble desk surface with a silver keyboard at its edge, lit softly from the side

NTKO Limited · Wembley, England

Software made to measure, and measured twice.

We are a small engineering practice. We build bespoke software for organisations whose work does not fit an off-the-shelf product, and we give independent technical advice to those deciding what to build, buy or retire. Few projects at a time, one accountable engineer on each, and nothing handed over that we would not be comfortable maintaining ourselves.

Begin a conversation Draft a commission brief

A practice, not a production line

Most software problems are not technically difficult. They are difficult because the requirement is unclear, the data is untidy, and nobody has had time to say what “done” means. That is the part we are good at.

NTKO takes on a deliberately limited number of commissions. Each one is led from first conversation to handover by an engineer who writes the code, so the person who heard your problem is the person solving it. We work in plain language, put estimates in writing, and explain the tradeoffs behind every recommendation. If something you ask for would make the system harder to own, we say so before we build it, not after.

Our clients tend to be operations leads, founders and small technical teams in the UK who need a capable outside pair of hands: someone to design and build a specific tool, untangle an inherited one, or give a sober second opinion on a plan.

The first discipline

Bespoke software

Internal web applications, client-facing portals, data tools and integrations, written for the way your organisation actually works. We design the data model first, because almost every later problem traces back to it, then build in small, reviewable increments you can use as they arrive.

  • Replacing a spreadsheet process that has outgrown itself
  • Back-office applications for case, order or job handling
  • Secure areas where your customers submit and track things
  • Connections between the systems you already pay for
How commissions work

The second discipline

Technical consultancy

Independent advice for decisions that are expensive to get wrong: whether to build or buy, whether an existing codebase can be rescued, what a sensible architecture looks like at your scale, and how to brief a supplier so you get what you need.

  • Codebase and architecture reviews with a written report
  • Build-versus-buy assessments for a specific need
  • Specification writing before you go to tender
  • A technical ear for non-technical directors
Consultancy in detail

What you actually receive

“Bespoke software” can mean anything. Here is what a typical NTKO commission puts in your hands, in writing and in a repository you own:

A written specification
Short, readable, agreed before building starts. It names the users, the jobs they do, the data involved and the things deliberately left out.
Working software, increment by increment
Deployed to a test environment you can reach, so you judge progress by using it, not by reading status reports.
Source code and infrastructure notes
In a repository under your organisation’s account, with instructions another competent developer could follow.
A handover document
How the system is put together, where it is hosted, what it costs to run, what to watch for, and the known limitations.
An agreed aftercare arrangement
Either a defined period of fixes and small changes, or a clean exit. Your choice, stated up front.

We would rather tell you in the first week that something should not be built than tell you in the twelfth that it cannot be finished.

This is the principle behind our first conversation, which is always free of charge and always ends with a candid view, even if that view is that you need someone else.

Where we fit, and where we do not

A good fit

  • A clearly bounded problem that existing products do not solve well
  • An organisation willing to give a few hours a week of a decision-maker’s time
  • Systems that need to be maintainable for years, not demo-ready for a week
  • Teams who value written reasoning over sales presentations

Better served elsewhere

  • Large programmes needing a dozen developers from day one
  • Work where an existing product would honestly do the job
  • Round-the-clock operational support or on-call cover
  • Hardware, regulated medical or financial advice, or certification audits

How a commission runs

  1. Conversation

    An hour, by video or telephone arranged by email. You describe the problem; we ask about users, data, constraints and what has been tried. No charge, no obligation.

  2. Specification

    A short paid piece of work producing the written specification, an architecture sketch and a fixed or ranged estimate. You can take it to another supplier if you wish.

  3. Increments

    Building in one- or two-week increments. Each ends with something you can use and a brief written note: what changed, what is next, what we need from you.

  4. Handover

    Deployment to your chosen hosting, documentation, a walkthrough with whoever will own the system, and transfer of every credential.

  5. Aftercare

    A defined arrangement for fixes and adjustments during working hours, or a clean exit with everything you need.

The method, in full

Before we meet

How ready is the idea?

Eight things that make a first conversation productive. Tick what is already true for you; the note underneath changes with your answers.

0 of 8 in hand

Tick what is already true. None of this is required to talk to us; it simply tells you how much of the first conversation will be discovery.

Standards of workmanship

We hold ourselves to a short list of habits, and we will show you evidence of each in the work itself rather than ask you to take them on trust.

  • Readable code. Named for what it does, consistently formatted, with comments where the reason is not obvious.
  • Automated checks. Tests around the parts that handle money, permissions or irreversible actions, run on every change.
  • Accessible interfaces. Keyboard-usable, labelled, legible, tested against the WCAG 2.2 AA criteria we can reasonably check.
  • Personal data treated with care. Collected only where needed, access controlled, retention discussed with you, not assumed.
  • Honest estimates. Ranges where there is uncertainty, and early notice when a range is about to be exceeded.

Read the workmanship page

Close crop of plum marble veining under cool light
Illustrative image

After handover

Software is looked after, not abandoned

Every system needs adjustment once real people use it. Aftercare at NTKO is a written arrangement: what counts as a fix, what counts as a change, how quickly we respond during UK working hours, and how either side can end it. If you already have a technical team, we can instead hand over completely and stay available for questions for an agreed period.

Aftercare and support

Questions we are often asked

Do you work with organisations outside London?
Yes. We are registered in Wembley and work remotely with organisations across the UK. Meetings happen by video call; where a site visit genuinely helps, we arrange it in advance.
Can you take over software someone else built?
Often, yes. We start with a paid review so that neither of us commits before knowing what the code, hosting and documentation look like. Sometimes the honest answer is that a careful rebuild of one part is cheaper than patching it.
Do we own the code?
Yes. Code is written into a repository under your account and the intellectual property is assigned to you on payment, as set out in our terms for each commission.
Will you sign a non-disclosure agreement?
Yes, before any detailed conversation if you prefer. Please do not send confidential material until it is in place.
Can you guarantee a delivery date?
We commit to dates we can defend and tell you as soon as one is at risk. Where a date is fixed by an external event, we shape the scope to fit it rather than promising everything.

Tell us about the problem, not the solution.

A few paragraphs are enough: what happens today, what goes wrong, and who is affected. We reply within two working days with either questions, a suggested time to talk, or an honest referral elsewhere.

Begin a conversation supp@ntkolim.link