The answer is sometimes do nothing.
When a board instruction starts with ‘do something with AI’, compare it with process change, conventional software and stopping.
Bring us the problem.
Kingsbury decides whether AI belongs in a piece of work, builds the system if it does, and leaves your team able to run it without us.
Open Work 001Live
Should AI be involved here?
Three of the seven questions. Nothing leaves your browser unless you ask for the report.
Latest
All writingBuilt by Kingsbury
Open Work 001 · Should AI be involved here?
Seven questions that decide whether a piece of work deserves AI before a product, model or vendor is chosen.
Use it.
Open Work 002 · What is the smallest pilot that can settle the decision?
Turns an idea into a bounded pilot with a threshold, evidence, an owner and permission to stop. Exports a one-page contract.
Use it.Work
All workCopilot Studio, SharePoint2026
A coach for the reports nobody had time to review.
A business whose senior reviewers were its scarcest people. The coach is grounded on the company's own report standards in SharePoint and gives an author structured feedback against them before a reviewer ever sees the draft. Update the standard and the coach follows; no retraining, no vendor in the loop.
Left behind: a coach in daily use, a written standard the business had never fully articulated, and a test set they re-run whenever the standard or the model changes.
Heavy industryCopilot Studio2026
HR policy and IT service desk, answered from the source.
Two agents built to settle one question: could the platform carry the organisation's front-line questions without a new system. One answers HR policy from the policy documents. The other handles first-line IT requests. Both shipped with build guides and UAT sets so the internal team could take them live.
Left behind: a platform decision backed by evidence rather than a vendor pitch.
Lift servicesPower Apps, offline-first2025–26
Job management that works in a lift shaft.
Field engineers lose signal exactly where the work is. The app takes the job with them, captures checklists and PPM submissions offline, and syncs to the back office when the connection returns. Taken through UAT, into production and through live defect resolution rather than left at demo.
Left behind: software the engineers use every day and a team that runs it.
How engagements work
- Advisory
One decision, resolved in writing, before you commit to a programme, product or supplier.
- Fractional
Senior direction beside the accountable owner while priorities, governance and supplier choices continue.
- Delivery
A bounded change built, put into use and handed over with its reasoning.
Most engagements start with Advisory. The others are separate decisions, made when the first one is clear.
Decide. Make. Transfer.
Every engagement runs in this order. Most stop after the first step.
- Decide
Inspect the work, alternatives, data, incentives and consequences. AI earns a place—or it leaves.
- Make
Put a working tool, agent or changed process into the hands of the people responsible for it.
- Transfer
Leave the reasoning, evaluation practice and operating capability with the team. Good work reduces dependence.
Who you're talking to.
Kingsbury is run by Kevin Ingrey. You deal with him from the first conversation to handover.
Before Kingsbury, Kevin was CTO at Tisski, a Microsoft partner acquired by Node4, where he ran a practice of around seventy people, including twenty architects, and built its AI practice from nothing. Before that he was Principal Technologist at QUANTIQ. Most of that time was spent on the unglamorous end of enterprise systems: Dynamics 365 implementations, public-sector procurement, and the governance that decides whether something is allowed to go live.
More about KevinBook a first conversation
Forty minutes, no cost, no preparation. Bring the problem, not the solution. If the answer is "don't", you'll hear it in the call.