Most security reports are written for IT departments. If you built your system yourself, or someone in your team did, you probably don’t have one of those.
So ours is written for you. Every finding starts with what it means in everyday words, then what could actually happen, then what to do about it and how long that should take. You can read it in one sitting, hand it to whoever does the fixing, and show it to your insurer or a big customer.
What you get
A map of your system
How it really fits together, including the spreadsheets, connectors and outside services nobody has written down.
A list of who holds the keys
Every login your business depends on, who controls it, and whether anyone else could get in.
Findings in plain English
Each one rated red, amber or green, and marked as tested or simply seen, so you know how firm it is.
A road ahead
What to fix now, what’s worth doing later, and in what order. There are no invented deadlines: you start when it suits you.
A runbook
What to do when something goes wrong, and who to ring, written for whoever happens to be there.
Early warning
If we find something urgent, we tell you straight away instead of saving it for the report.
You don’t have to take our word for any of this. Read a full example report, written for a fictional builders’ merchant.
Who it’s for
You’re a good fit if your business has a system that was built quickly, by an owner, a keen member of staff or a freelancer, often with an AI tool, and that:
- holds customer or staff details, prices or orders;
- your team would really miss if it stopped tomorrow;
- nobody independent has ever looked at.
You don’t need to be technical. If you can tell us what the system does and who uses it, that’s enough to begin.
What it isn’t
It isn’t a formal, certified penetration test. If a customer or insurer asks for one by name, tell us and we’ll say so up front. It also isn’t a sales pitch for a rebuild. Most home-grown systems have earned their place, and our job is to help you keep yours safely.
It can’t prove that a system is perfectly safe either, and nobody honest will tell you it can. It shows you the risks we can find, in an order you can act on.
What it costs
It depends on how many systems are involved, so we quote each job. You’ll have the scope and the price in writing before anything starts, under our terms of business.
Questions
Will the audit interrupt our work?
It shouldn’t. We use test accounts where we can, and we ask for your go-ahead before any test that would create a record on your live system.
Who sees the findings?
Only you and the people you choose. Our findings are confidential, and we won’t name you as a client without your agreement.
Do you fix things as well?
The report tells you exactly what to fix, so that you or your own developer can do it. If you’d rather hand it over, we can agree that with you, or take the whole system on.
Last updated 6 November 2026.
