When is ISO 27001 worth it for a small business?
The honest test is commercial. If certification wins or keeps contracts, passes diligence you currently fail, or replaces a growing pile of questionnaires, it pays.
If nobody is asking and your risks are modest, start with Cyber Essentials and build the basics well. ISO 27001 will still be there when a customer requires it, and the work will count.
I give the same advice on readiness calls even when it costs me the engagement. A certificate bought too early often lapses unloved at the first surveillance audit.
What does proportionate ISO 27001 look like at up to 50 staff?
- Scope: the service your customers buy, from your single site or remote setup: credible, and trimmed to what you can defend.
- Policies: one information security policy plus a handful of topic policies people actually read.
- Risk: a simple documented method and a register your managers scored themselves.
- Controls: strong basics (MFA everywhere, tested backups, joiners/leavers discipline, supplier checks, patching), evidenced from the systems you already use.
- Ownership: one named person with a few protected hours a month; see who should own the ISMS.
What is the route to certification for a small business?
- Agree the scope and run a gap analysis against it.
- Build the risk register and treatment plan with your managers.
- Produce the Statement of Applicability and the slim policy set.
- Operate the controls and accumulate dated evidence (about three months).
- Internal audit and management review; fix what they find.
- Stage 1, then Stage 2 with an accredited certification body you booked early.
Timelines and phasing are detailed in my guides to how long ISO 27001 takes and what it costs. If you are weighing doing it yourselves against support, my consultant vs toolkit comparison prices the internal hours honestly; the charity case study shows the proportionate route in practice.