N
Capability 08

Custom AI Tools

Not every project has to start with a system. When a single task costs time regularly — collating details, sorting texts, preparing a list — a self-contained tool can be built for it. That can be a more solid start than a presentation: the assumptions about your process are tested on a real task before a system is built on them.

Contributes to

A capability is a means. The linked areas describe what it is used for.

Scope

What specifically gets built.

Every line is a commitment about future work — none of it is a claim about completed projects.

One task, one interface, one result
On your own data, not on general knowledge
The result as a file or straight into the system that needs it
Traceable: what the result was derived from
Set up so it can later become part of a larger system
Technology

The decisions behind it.

Categories rather than vendor names — which product is used depends on your existing systems.

  • The scope is deliberately kept small: as soon as a tool grows, it should be planned as a system
  • A fixed ceiling on running costs and on the number of requests — part of the scope, not a later fix
  • The AI system in use can later be swapped for another — you are not tied to any provider
Out of scope

What is not included.

So that no time in the intro call is spent on an expectation I do not meet anyway.

  • No tool without a named task and a named user
  • Not a substitute for a system when several people are involved in the process
  • No collection of small tools in place of one application

These eight capabilities are means, not offerings. Which of them are used follows from the process — not the other way round. If you are not sure which ones you need, that is the normal case and not a problem.