Problem-first AI adoption

AI reveals your system of work.
We fix what it reveals.

Start with the problem: AI can magnify strengths and weaknesses in how your organisation works. Good practice can go further; unclear decisions, unreliable information and delays can grow too. We help your leaders and workforce build the baseline, investigate where AI could help, and engineer systems where the evidence supports them.

Why listen to us

We treat AI as an engineering and organisational system, not a novelty or a collection of tools.

Twenty-five years of software delivery: DevOps, platform engineering, distributed systems, and engineering leadership, building real products on .NET, Azure, GitHub, and Azure DevOps. Independent of every AI vendor, so tools are judged on evidence and outcomes, not allegiance. And we run our own consulting practice on governed AI agents: live client work, not a demo.

Traceable

Trace changes and the evidence behind them so people can inspect what an agent did.

Honest

Check the result against the requirement. An agent's confidence is not proof that its work is correct.

Accountable

Define who can approve, stop and recover the work. Responsibility stays with people.

Where you are

Start where it hurts.

None of these? Tell me what's actually happening and we'll work it out together.

Official Kendall Partner

Start with the problem. Build the capability to act on it.

We are an official Kendall Partner. The Kendall Framework supports organisational AI adoption through leadership alignment, workforce literacy, opportunity discovery and context management. We bring that problem-first approach to your organisation, with engineering support when the work calls for it.

What Kendall brings

The discipline: problems validated before tools, the knowledge your AI needs written down and owned, and named accountability for keeping it true.

What we add

We investigate what is holding the work back, compare AI with other interventions, and help implement the change the evidence supports. For agent systems, that includes permissions, verification, recovery and human responsibility.

Kendall Framework, Context Block, Context Warehouse, Context Operations, AI Bill of Materials and Context 360 Sprints are marks of The Kendall Project.

Start free

The Engineering AI Adoption Guide

Our guide applies the Kendall Framework to engineering and technical leadership, with a separately labelled NKD Agility operating layer.

A problem worth AI investment is an operating gap you can evidence: a named owner, a reproduced failure, a measurable cost - stated in the language of operations (throughput, cycle time, error rate, cost, customer outcome), not the language of tool capability.

The discipline is not to make language rigid. It is to make the language that matters stable enough to reuse: canonical definitions, certified terminology with named owners and review dates.

Excerpts from the current guide's problem and language principles.

Openly licensed. Read it, run it with your own people, never talk to us. If that is all your organisation needs, that is a good outcome and we mean it.

When you want us in it

What changes when we work together.

Come in at the level your situation demands, not the level a salesperson suggests. Published rates, no time tracking, and if an engagement fails to meet the agreed standard we refund the fee.

A shared baseline for your organisation

Leadership training helps people examine AI decisions across the organisation. Workforce training gives everyone a baseline for using AI, checking its output and recognising when human judgement is needed. Fixed price, agreed before work starts.

For your leaders
For your workforce

You know which problems are worth it

A prioritised, evidenced list of where AI creates value in your organisation, and an honest “don't” where it doesn't. Priced per problem investigated, and you keep the validated context whether or not anything gets built.

How discovery works

Agent systems with explicit controls

Build with your engineers, on your estate: limited permissions, traceable changes, verification and recovery, with responsibility assigned to people. Ongoing support is capacity, not hours.

How we build

The thinking behind this

AI adoption and agentic engineering insights

DevOps
Article

AI exposes that coding was never the main bottleneck in software delivery; real constraints are in system flow, team practices, and organisational …

Artificial Intelligence
Engineering note

Explains how generative AI and PowerShell scripts automate and improve blog post tagging and categorisation in Hugo, with human oversight and …

Leadership
Article

Explores the distinct roles of human and AI agency in adaptive systems, emphasising human-led strategy and accountability versus AI-driven tactical …

All insights

The next step

Before you buy anything, it's worth a conversation.

Tell me what you rolled out, what you expected, and what actually happened. I'll tell you what it will take, or that you don't need us. Either way you leave knowing more than you arrived with.

Frequently Asked Questions

Questions we hear before every AI conversation.

If your question isn't here, ask us directly.

Adoption alone does not identify the constraint. Coding may be faster while work waits for review or release; rework may have increased, or the tool may not suit the task. Compare coding, waiting, review and correction before deciding what to change.

No. We are vendor-neutral and problem-first. We investigate what you need before recommending an intervention. That may involve AI, or it may mean changing how the work gets done without adding an AI system.

Examine ownership, context, technical feasibility and operating costs against the value of the problem. Restart when there is a credible next test with success and stopping criteria. Stop when the evidence does not justify further investment. A real problem alone does not guarantee success.

Yes. We use AI agents in our consulting practice and can show a sanitised walkthrough. Written instructions set expectations; permissions, checks and human review address particular risks. Instructions alone do not enforce obedience, and an agent’s claim of completion is not verification.

As checked on 14 September 2026, Article 4 requires providers and deployers within scope to support AI literacy development in context. Training can contribute; a certificate alone does not prove compliance. See our Article 4 explanation for the current legal source, and have your legal or compliance lead assess your organisation’s scope.

Training and workshops are fixed-price and agreed before work starts. Discovery is priced per problem investigated, so you control the scope. Ongoing support is a capacity retainer, not billed hours. Our rates are published, expenses are actuals with no markup, and if an engagement fails to meet the agreed standard we refund the fee.

That depends on the work and the team’s existing capability. We examine skills alongside tests, permissions, delivery checks and recovery. The first step may be training, an engineering improvement or a limited experiment. Workforce literacy is a separate baseline for everyone across the organisation.

Not sure what your AI adoption actually needs?

Tell me the problem you want to solve, what you've tried and what happened. We can examine the next step, whether that is training, investigation or technical work. If the guide and your own people are enough, I'll say so. If we work together and the engagement fails to meet the agreed standard, we refund your fee.