Diagnose before you automate
I don't start with AI. I start with what isn't working.
Most AI projects fail because they automate a broken process faster. I map how the business actually works, find the wasted effort and the disconnected systems, redesign the workflow, and only then build the AI, CRM, automation, dashboards or integrations that earn their place.
Growth shouldn't depend on manual work. Neither should it depend on tools nobody uses.
This is usually how the conversation starts
“Everything is manual and it doesn't scale.”
“Our systems don't talk to each other.”
“Our CRM is a mess and nobody trusts the data.”
“We bought AI tools and nothing really changed.”
“The team spends more time on admin than on customers.”
“We can't get a straight answer out of our own reporting.”
You don't need to know the solution. That's the part I help with.
What gets built
Once the workflow is right, the build follows.
Workflow redesign
Clearer ways of working before any tooling. Fewer steps, fewer handoffs, fewer places for things to go missing.
CRM and data
A CRM that reflects how you actually sell and serve, with data people trust and processes that keep it clean.
Automation
The repeated admin, data movement and chasing, removed. Human attention kept for the things that need it.
AI workflows
Research, analysis, content, summarisation, reporting and decision support, built into the work rather than bolted on.
Knowledge systems
Company information, processes and internal expertise made findable and usable, including by AI, instead of trapped in people's heads.
Integrations and dashboards
Connected tools and reporting that answers the commercial question rather than producing another PDF.
The framework
Diagnose, Redesign, Build, Upskill.
Diagnose
Map how the business actually works today. Where the effort goes, where the value leaks, where the systems break contact.
Redesign
Fix the process before the tooling. A simpler workflow often removes the need for the software you were about to buy.
Build
Implement the right mix of AI, CRM, automation, internal tools, dashboards and integrations, in priority order.
Upskill
Hand it over properly. The team knows how it works, why it works and how to change it when the business changes.
What changes
The goal isn't fewer people. It's a more capable business.
- Repetitive admin, duplication and manual steps removed
- Systems that connect instead of sitting in silos
- AI applied where it measurably helps, and nowhere else
- Human judgement kept in the loop on quality and brand
- Reporting that answers commercial questions
- Capability that stays in the business, not with a consultant
Questions
The things people ask before we start.
Do we need to be AI ready to start?
No. Most businesses I work with are not, and that's fine. The first stage is mapping how you work now. If the honest answer is that AI isn't the priority yet, I'll say so and we'll fix the thing that is.
Is this about replacing staff?
No. The goal is a more capable team, not a smaller one. Removing the repetitive work usually means the people you have can cover more valuable ground, not that you need fewer of them.
What tools do you build with?
Tool choice comes after the workflow is designed. I'm not tied to a vendor, so the recommendation is based on what fits your process, budget and the team's ability to run it after I've gone.
How is this different to hiring an automation agency?
An automation agency builds what you ask for. I start by questioning whether that's the right thing to build. The diagnosis and the commercial prioritisation are the part that saves money.
How long does a transformation programme run?
Diagnose and redesign is typically four to eight weeks. Build is phased and sequenced against the Now, Next, Later roadmap, so value lands early rather than at the end of a twelve month project.