Key Numbers
Cost Breakdown
Internal Costs (often underestimated)
External Costs
Certification Timeline
Timeline depends heavily on scope. A 50-person SaaS company can certify in 6 months. A 500-person manufacturer may take 18.
What Companies Get Wrong
The five failure modes I see repeatedly - and they almost always trace back to early project decisions.
Certifying "the whole company" adds 12 months and $30K unnecessarily. Define the minimal scope that satisfies your customer requirements.
Companies buy tools before doing the risk assessment. You end up with controls that don't match your actual risk profile.
200-page policies nobody reads. ISO 27001:2022 expects evidence of operation, not documentation weight.
ISO 27001 requires management commitment. If the CEO isn't involved in the risk acceptance process, the certification won't survive the surveillance audit.
UKAS-accredited bodies are recognized globally. Non-accredited certification has no value with enterprise customers or in regulated industries.
When ISO 27001 Makes Sense
- Enterprise customers in finance, healthcare, or government require it for vendor onboarding
- You're bidding on EU public sector contracts (NIS2 increasingly references it)
- You want a structured framework for your security program, not just the certificate
- Your company is pre-IPO and wants demonstrable security governance
When It Doesn't (Yet)
- You're pre-Product Market Fit and security is mostly AWS defaults + MFA
- Your only customer segment doesn't ask about it
- You don't have 6 months of focused internal bandwidth