Strategy & AI audit

AI audit & baseline

Everyone has a view on what AI can supposedly do. The more useful question is a smaller one: which parts of it are worth doing in your business – and which aren't.

You'll get …

  1. 1

    Clear priorities, not AI noise

    The two or three steps to take first in your business – weighed up for benefit and effort, each with its reasons.

  2. 2

    A verdict on the tools

    A recommended tool for each step, and a clear answer on who runs it afterwards – upkeep included.

  3. 3

    What isn't worth doing (yet)

    The things you can safely leave alone are listed too – again with reasons. "Nothing for now" can be the answer, too.

01Intro

The audit takes stock and then gives you a verdict. We look at how you work: which tasks keep coming up, where your knowledge lives (in people's heads, emails, folders), what your website can do and where things get stuck day to day. You come away with an assessment: the two or three steps worth taking first, each with a recommended tool.

The audit isn't a sales pitch in disguise. It may turn out that you don't need an AI project (yet) – and that's worth knowing too. Nor does it replace professional advice: tax, legal and data-protection questions belong with the relevant experts.

02How it works

  1. 01

    A short questionnaire, then a conversation

    First you answer a few questions about your processes, team and tools, so we don't spend the meeting on the basics. In the session itself we talk about day-to-day work: what eats up time, what's frustrating, what keeps getting put off. That's usually enough to show where it's worth digging deeper.

  2. 02

    A look at your website, knowledge and tools

    I look at what you already have – your website, typical inquiries, sample documents, the tools you use. Not everything, but enough to see where your knowledge lives and what state it's in.

  3. 03

    Weighing effort against benefit

    Every idea on the table is tested against two questions: what does it do for you day to day – and what will it cost over time, including upkeep and running costs? A lot of ideas fall at this stage. That's the point of the exercise.

  4. 04

    A roadmap of two or three steps, with reasons

    You get a concise result: the next steps in order of priority, each with a recommended tool and a clear answer on who runs it afterwards. Plus a list of what we deliberately do NOT recommend – with reasons.

  5. 05

    Optional: a pilot to get started

    If one of the steps convinces you, we set it up as a pilot: small in scope, measurable, with a clear end point. That way the work gets going without the risks of a big project.

03Stages

How far the audit goes depends on where you are now. The entry level is deliberately small – and it's often enough to settle the direction.

Tier 1 · from €880

Starter: compact audit

One conversation, a quick review and a short report on the two or three biggest levers.

Tier 2 · from €2,200

Next step: full baseline

The full audit, including the team's perspective, a map of where your knowledge lives, a prioritised roadmap and a verdict on tools.

Tier 3 · custom

Full build: guided rollout

The audit as a starting point: we build the first pilot together, your team learns to work with it, and after a few months we fine-tune it.

04Demo

simulation · curated examples

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.

05Technical implementation

  • The audit is deliberately lightweight – a consulting service, not a software project. Nothing gets installed and nothing gets rebuilt.
  • Depending on the case, the review covers website and search data (e.g. Search Console), sample documents and inquiries, and the tools you already use.
  • AI helps with the analysis – for example in working through sample material. The judgement itself is still done by hand.
  • The result is a concise document or a short presentation, which we can go 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.

06Related building blocks

See all use cases