Enterprise delivery credentials
NCA registration
Registered cybersecurity service provider

ISO/IEC 27001
ISO/IEC 27001 certified
The discipline
Continuity is a business question that IT recovery sits inside
We do not have an office in Saudi Arabia
We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.
Disaster recovery answers a technical question: how do we bring the systems back. Business continuity answers the commercial one that contains it: which parts of the business must keep running, for how long can each stop, and what do we do in the meantime. The instrument that grounds the answer is the business impact analysis — sitting with the people who run each process and with finance, and pricing stoppage honestly: what does an hour without order intake cost, at what point does a payroll delay become a legal problem, which customer commitments carry penalties by the day. Those numbers do the deciding. They tell you which processes deserve an expensive standby arrangement, which can wait a week, and which need no plan beyond a phone number.
Run without that analysis, continuity planning produces the familiar artefact: a thick binder that protects everything equally, which is to say nothing in particular, written to satisfy an audit rather than to be opened during a disruption. Run from the analysis, the plan inherits proportion — most of its attention on the handful of processes whose hours are expensive, brief and honest about the rest — and it earns the right to be short, which is the property that decides whether it gets used.
The blind spots
The dependencies continuity planning forgets until the day they matter
System dependencies get mapped because they are visible. These four are found the hard way, in the middle of the disruption — unless the analysis goes looking for them first.
The person who is the process
One finance officer who alone knows the payment release steps; one engineer who holds the credentials in his head. If a process stops when a named individual is unreachable, that name belongs in the plan — with a trained deputy and written steps, decided before the vacation, the resignation or the emergency.
The supplier who goes down with you
The logistics provider, the payment processor, the single supplier of the critical input: their disruption is your disruption, arriving without any of your systems failing. The analysis asks, per critical process, which third parties it stands on, what their committed recovery looks like, and what the workaround is if the answer disappoints.
The door that will not open
A building closed by fire, flood or order; a badge system that is itself down; the operations room nobody can reach. Physical access is a dependency like any other — which work can move elsewhere, where the elsewhere is, and what genuinely requires standing in that room are questions with much better answers on a quiet Tuesday.
The channels that fail together
When the network is down — or, in a cyber incident, deliberately untrusted — the email and chat the plan assumes may be unavailable or unsafe. Contact lists that exist off the estate, an agreed out-of-band channel, and printed copies of the crisis pages sound quaint until the first hour of the one day they are the entire plan.
The build
From impact analysis to a plan people can run half-asleep
Each step earns the next: the analysis earns the priorities, the priorities earn a short plan, and only a short plan earns a real exercise.
Price the stoppages
With process owners and finance, each critical process gets an honest cost per hour or day of stoppage and a maximum tolerable outage — the number every later decision is argued from. A ranked list of processes with tolerances attached.
Map what each process stands on
Systems, yes — and people, suppliers, premises and communications, walked with the owners until the map includes the dependencies that never appear in an architecture diagram. A dependency map that names names.
Write the plan short
Per scenario, a playbook of a few pages: who declares, who decides, the first ten actions, the workarounds, the contacts. The reference material lives elsewhere; the playbook is what gets opened at 2 a.m. Playbooks people can hold in one hand.
Exercise it for real
A tabletop with the actual role-holders first, then live tests of components — the alternate site, the out-of-band channel, the deputy running the process alone. Every exercise ends in a list of what the plan got wrong, which is the point of holding it. A plan corrected by rehearsal, and people who have done it before.
Tie updates to triggers
The plan is updated when the organisation changes — a reorganisation, a new critical supplier, a system replaced, a key departure — not on an anniversary. An annual date checks the plan; the triggers keep it true. A plan that still describes the organisation it protects.
Our role
What we facilitate in continuity work and what your leadership owns
- 01
The analysis, kept honest
We run the impact workshops and push back on the two chronic distortions — every process claiming to be critical, and every tolerance set by optimism — because a flattering analysis produces a plan that fails politely.
- 02
Plans written for the worst hour
We draft the playbooks with the people who would execute them, in their language, at the length a crisis permits — and we cut everything that reads well in an audit and uselessly at 2 a.m.
- 03
Exercises that tell the truth
We design and facilitate the exercises so they probe the plan's claims rather than confirm them, and we write up what broke without varnish — because an exercise that flatters the plan wastes the one chance to fix it cheaply.
How much continuity to buy — which standby arrangements, which redundancies, which risks to carry uncovered — is a spending decision for your leadership; our work is to make sure it is taken against priced stoppages and a rehearsed plan rather than against a guess.
Common questions
What buyers ask
Is business continuity planning the same thing as IT disaster recovery?+
No — disaster recovery is one component inside it. DR answers a technical question: how the systems and data come back, in what order, within what targets. Continuity answers the surrounding business question: which processes must keep running, what each hour of stoppage costs, and how the organisation operates during the gap — including disruptions where the systems are fine and the problem is a person, a supplier or a building. The relationship runs one way: recovery targets should be derived from the business impact analysis, not invented inside IT. An estate with excellent DR and no continuity plan has rehearsed the middle of the story and left both ends to improvisation.
How short can a continuity plan be and still satisfy auditors?+
Shorter than most organisations believe, because the trick is structure, not omission. What has to be short is the playbook — the pages someone opens mid-crisis: roles, the first actions, workarounds, contacts, a few pages per scenario. Behind it sits the full apparatus auditors want to see: the impact analysis with its methodology, the dependency maps, the exercise records, the maintenance log. The binder that fails is the one that merges these layers, burying the crisis steps inside the evidence. Separated, each layer does its job: the auditor reads depth, the person at 2 a.m. reads a checklist, and the exercise records prove the checklist has been run by the people named in it — which persuades an auditor more than any page count.
How often should a continuity plan be exercised, and does a tabletop count?+
A tabletop counts, and for a new plan it is the right first exercise: cheap, safe, and remarkably effective at exposing wrong phone numbers, ambiguous authority and steps that assume a system that will not be there. But a rehearsal programme that stays at the tabletop level never tests the physical claims — that the alternate arrangement works, that the deputy can actually run the process, that the out-of-band channel reaches people. A reasonable rhythm for most organisations: a tabletop for the priority scenarios each year, one live component test in the same period, and an unscheduled exercise after any material change to the organisation. More telling than frequency is what happens afterwards — an exercise that produces no corrections was designed to succeed, and a plan that is never corrected is quietly expiring.
In this cluster
Next step
Start with the impact analysis
A scoping conversation that picks the two or three processes whose stoppage would hurt most, as the starting point for an impact analysis your leadership will recognise itself in.
