Strategy & AI audit
AI audit & baseline
Everyone's telling you what AI can supposedly do. The more useful question is smaller: which of it is worth doing in your business – and which isn't.
AI audit & baseline
01AI audit & baseline
The audit is a stocktake with a verdict. We look at how you actually work: which tasks keep coming back, where your knowledge sits (in people's heads, emails, folders), what your website can do and where things snag day to day. You walk away with an assessment you can't google: two or three steps worth taking first – with a straight recommendation on tools. Sometimes the answer is an AI application. Sometimes a leaner website. Sometimes: nothing yet.
The audit isn't a sales call in disguise. It's a perfectly good outcome to find you don't need an AI project (yet) – that's worth knowing too. And it doesn't replace expert advice: tax, legal and data-protection questions belong with the relevant professionals.
02Demo
Pick a business and look at its roadmap – anonymised, simplified examples, but this is what real results look like. Most important part: the last card.
03How it works
- 01
A short questionnaire, then a real conversation
Beforehand you answer a few questions about your processes, team and tools – that keeps the basics out of the meeting. In the session itself we talk about the day-to-day: what eats time, what grates, what keeps getting left. Usually that's already where it becomes clear where it's worth digging.
- 02
A look at your website, knowledge and tools
I look at what's there – your website, typical inquiries, sample documents, the tool landscape. Not everything, but enough to understand where your knowledge actually sits and what state it's in.
- 03
The verdict: effort against benefit, no hype
Every idea on the table is held against two questions: what does it really give you day to day – and what does it cost over time, including upkeep and running it. Plenty falls away here. That's the point of the exercise.
- 04
A roadmap: two or three steps, with reasons
You get a compact result: the prioritised next steps, each with a tool recommendation and a clear answer to who runs the thing afterwards. Including the list of what we deliberately do NOT recommend – with reasons.
- 05
Optional: a pilot to get going
If a step convinces you, we define it as a pilot: cut small, measurable, with a clear end. That's how the work starts without big-project risk.
04Stages
How deep the audit goes depends on where you stand. The entry point is deliberately small – often it's enough to settle the direction.
Entry: compact audit
One conversation, a quick review, a short report with the two or three biggest levers. Quickly done, useful right away.
Extended: full baseline
The complete audit: with the team's perspective, a map of where your knowledge sits, a prioritised roadmap and a verdict on tools.
Full build: guided rollout
The audit as a starting point: we build the first pilot together, the team learns to work with it, and after a few months we sharpen it up.
05Technical implementation
- The audit is deliberately lightweight – a consulting service, not a software project. Nothing gets installed and nothing gets rebuilt.
- The review draws on, depending on the case: website and search data (e.g. Search Console), sample documents and inquiries, a look at the tools already in place.
- AI helps with the analysis – for instance in working through sample material. The verdict stays handmade.
- The result is a compact document or a short presentation – talked through together if you like.
- The assessment always includes running costs: what a tool costs over time in upkeep, licences and attention – not just what it costs to build.
for context · This shows how something like this usually gets built – not how it has to be built for you. What actually fits is worked out in the project: around your existing setup, your team, and what stays easy to maintain.