How Long Does It Take to Implement ISO 27001?
What Does It Really Cost When Your Biggest Client Requires ISO 27001 and You Don't Have It Yet?
The email arrives on an ordinary Tuesday. Your biggest client, the one that accounts for a significant share of your revenue, has attached a new clause to the contract renewal agreement. They now require ISO 27001 certification. And they have set a deadline.
From that moment on, the clock starts ticking. The question that usually comes up in the next meeting is the wrong one. People ask, “How much will it cost?” The right question is something else entirely.
The Cost of “Not Yet” Is Not What You Think
The obvious interpretation is simple: we say no, we lose the contract, and we calculate the financial loss. The more expensive cost arises when the organisation says yes without fully understanding what it is committing to. It accepts the client's deadline without challenging it against the reality of what a proper ISO 27001 implementation requires. That is when the real problem begins, and it is usually invisible at the moment the agreement is signed.
Because an ISO 27001 certification rushed through to meet a deadline is not a certification. It is deferred debt. Controls designed to pass an audit rather than to work in practice. Documentation that describes a company that does not exist. An organisation operating exactly as it did before, now with a certificate on the wall saying otherwise.
The real cost is this: paying twice. The first time, to rush through certification. The second time, to correct everything that was left undone, often only after an incident, a surveillance audit, or a new client begins asking tougher questions.
The Three Timelines You Need to Map Before You Respond
When organisations receive this requirement, they tend to focus on a single date: the client's deadline. Everything is planned around that date. That is where the process starts to go wrong. There are three timelines to consider, not one.
The Client's Timeline
This is the date specified in the contract. It is fixed, external, and rarely takes into account what is actually required to implement an Information Security Management System. It was set by the organisation that needs the certificate, not by the organisation that has to build the system.
The Real Timeline for an Implementation That Works
It depends on the organisation's size, its existing level of maturity, and the current state of its operations. For most organisations, the process takes between 6 and 12 months and can extend to 18 months when starting from a low level of maturity. This is not a figure that can be invented in a meeting. It comes from a proper assessment.
The Shortcut Timeline
This is the temptation. Compress the second timeline to fit the first. Skip the assessment, copy templates, certify the façade. It is the path that appears to solve the problem but, in reality, simply transfers it into the future, with interest.
The job of the person leading this internally is not to choose the shortest deadline. It is to make the gap between these three timelines visible before commitments are made. Because once the agreement is signed, the client's clock starts calling the shots.
Where Does the Shortcut Start to Break Down?
It is worth being specific about what gives way when timelines are compressed beyond what is reasonable. The assessment gives way first. Implementation begins before anyone truly understands where the real gaps are. Leadership alignment gives way next. The board approves the budget but does not commit to the change itself. And without executive sponsorship, any transformation initiative eventually loses momentum. Change management gives way. Controls are implemented, but people do not use them because nobody prepared them for the new way of working. Operations give way. Because changing the way an organisation works takes far longer than changing a document.
The Cost That Rarely Appears in the Business Case
There is a cost that few people talk about: the personal cost. The person who receives the requirement and commits to the deadline is usually the same person who will be sitting in the room if the audit goes badly. Execution risk has a name. And it is often the name of the person who said, “Yes, we can do it.” There is another factor that changes the entire conversation. Across many implementation projects, the greatest cost of ISO 27001 is not financial. It is organisational. It lies in changing culture, behaviours and processes. In other words, money is rarely what causes these projects to fail. Time and alignment are.
What Sets Successful Organisations Apart
The organisations that emerge from this process stronger — not just certified — tend to do three things differently.
They Start with an Assessment, Not a Deadline
They understand where they are before promising where they will be. This allows them to negotiate the client's timeline using evidence rather than accepting it out of fear of losing the business. A deadline supported by a proper assessment is almost always more convincing than a rushed "yes".
They Involve Leadership Early
Not as people who simply approve a budget, but as leaders who recognise that this is a business decision with implications across the entire organisation. Certification is the outcome. Preparation is the work. Without this level of involvement, the project is likely to lose direction halfway through the journey.
They Choose Guidance Over Delivery
The difference between a consultancy that leaves a set of documents on your desk and a partner that walks the journey alongside your team is often the difference between passing the audit once and building something that still stands at the next one.
The question is no longer, “How do I obtain the certificate in time?” It becomes, “How do I become the kind of organisation this requirement assumes I am — and how do I do it without breaking anything along the way?”
Before You Respond to Your Client, Map the Journey
We have prepared a practical guide for professionals who are exactly at this stage: the person who has received the requirement and needs to understand the journey before making commitments. It explains what the requirement actually involves, how to structure the phases of an implementation that works, and where projects most commonly go off track.
ISO 27001 eBook