AI Consulting & Training
Where AI actually helps, and where it does not.
An honest audit of where AI would save your team real hours, training so staff can use it properly, and a roadmap that sequences the work - including the parts we would tell you to skip.
Scoped against the work you already do
How we think about it
Most AI projects fail for the same reason: nobody wrote down what the thing had to be right about. We start with the process you already run, find the two or three places where a model measurably beats it, and say plainly where it does not — usually more of the list than people expect. You get a scoped plan and a team that can run it, not a pilot that quietly stops being used.
The advice is only useful if someone can build the thing afterwards, and the team scoping it is the team that would.
What this covers
The work, specifically.
- 01
AI readiness audit
Which processes are worth automating, which are not, and what it would cost either way.
- 02
Staff training
Practical sessions on ChatGPT, Claude and the tools your team will actually open.
- 03
Custom GPTs and assistants
Internal assistants built on your documents, with access rules that respect who should see what.
- 04
Implementation roadmap
Sequenced by payback, not by what is easiest to demo.
- 05
Prompt libraries and SOPs
Written procedures so results are repeatable when the enthusiastic person leaves.
Need AI Consulting & Training for something specific?
Tell us what you're trying to ship and we'll say plainly whether this is the right service for it — including when the answer is no.
How it runs
The same four steps, whatever we're building.
No account-manager relay. The lead on your project is someone who builds, and they stay on it from the first call to the last deploy.
Scope
A week of hard questions. We map what you actually need and say plainly which parts we'd cut.
Prototype
Something real in front of you early, not a document about it. Opinions get cheaper.
Build
Two-week cycles, a demo at the end of each. You see progress, not status reports.
Hand over
Documentation, a walkthrough, and the keys. Support if you want it — never as a hostage.
Questions
The things people ask before they enquire.
It depends on scope, but we will give you a number before you commit to anything. Most engagements start with a paid discovery — a fixed fee, a week or two — which ends in a written scope and a real budget. If the budget does not work, you leave with the scope document and no obligation to continue.
A typical first ship is around six weeks. Larger builds run in two-week cycles after that, each ending in a demo of something that actually runs. You will know within the first cycle whether the timeline is holding, rather than finding out near the deadline.
The people you meet. The lead on your project is someone who builds, and they stay on it from the first call to the last deploy. There is no account manager relaying messages between you and an unseen team.
You own everything — code, assets, accounts, domains. We hand over with documentation and a walkthrough, and your team can run it without calling us. If you would rather we stayed on for maintenance or a next phase, that is a separate agreement, not something buried in the original contract.
Yes. Most of our work is remote, and we keep a few hours of overlap with your working day for calls. Timezone has not been the hard part; unclear scope has.
Where it meets the others