A one page summary
What is wrong, what it is costing, and what to do first. Readable in the time it takes to make a coffee.
Engagement 01
The audit
One week inside your setup. A written document you keep, with every finding evidenced, costed, fixed and ranked. It is the way in to everything else, and it stands on its own if you never go further.
What it reads
Everything, not just the part that is bothering you. The symptom is rarely where the problem is.
Website
Structure, speed, what it says, what it asks for, and whether anyone can find it.
Advertising accounts
Google and Meta. Structure, tracking, wasted spend, and whether the account is even approved to run.
CRM and pipeline
Where enquiries land, who follows up, what falls through, and what the data is actually worth.
Email and domain
Deliverability, authentication, the templates going out, and the inbox nobody checks.
Phones and Microsoft 365
Call routing, voicemail, licences, shared mailboxes, and the settings that have never been reviewed.
Documents and templates
Proposals, invoices, onboarding packs. What the client sees, and whether it matches the standard you charge for.
Ecommerce
Shopify and the like. Product pages, checkout, fulfilment notifications, and the theme debt underneath.
Automation
The manual steps between all of the above, and which of them a machine should be doing.
What you get
One document, written for you, not for me.
Every finding, ranked
Ordered by what it is worth to fix, not by what is easiest or what I would most like to sell you.
Four parts to each finding
Evidence, cost, fix, rank. No finding ships without all four, so nothing in the document is an opinion.
A recommended order of work
What I would do first if the setup were mine, with what each step depends on. You can hand this to anyone.
If the setup is fine, the audit says so. It is not a sales document for the restructure, and a clean report is a good outcome.
What a finding looks like
- EvidenceA screenshot or an export of the thing itself. Not a description of it.
- CostWhat it is costing you now, in money, time or risk. Stated plainly, with the working shown.
- FixWhat to change, specifically enough that anyone competent could do it, not just me.
- RankWhere it sits against every other finding, ordered by what it is worth, not by what is easy.
How the week runs
-
01
Access
On day one I ask for read access to the accounts and systems. I ask for your time only where a login cannot be shared.
-
02
Reading
The middle of the week is spent inside the setup. You will not hear much from me, which is the point.
-
03
Writing
The document is written by the end of the week. Every screenshot taken, every cost worked through, every fix specified.
-
04
Walkthrough
We go through it together, in plain language. You decide what, if anything, happens next.
What it does not include
Making the changes. That is the restructure, and it is quoted separately, after you have read the audit and decided what you want done.
It also does not include pretending. If a finding is minor, it is marked minor. If a system is fine, it says fine.
Who should not buy it
- Anyone who wants the rebuild without the read.
- Anyone who had an independent audit in the last few months and has not acted on it yet. Act on that one first.
- Anyone who needs a decision by Friday.
