Free Strategy Call

Book Your Call

One call. Clear direction. Faster execution.

Case StudyLogistics·Resilience

How a logistics company kept 92% of shipments moving with its systems down.

A competitor was hit by ransomware and stopped shipping for 11 days. This company had no plan for the same day. Skillfi's fractional CISO built a manual fallback for dispatch and tracking, tested it at every hub and cut recovery time from days to hours. It's how our fractional CISO service works: ready for the bad day before it comes.

Time to recover core systems
3 days→9 hrs
92%Shipments moving in drill
3 hubsFallback tested
25 minTo switch to manual
01

Every truck depended on systems nobody had planned to lose.

The company moves freight and last-mile deliveries for retailers from three hubs. Dispatch, route planning, driver apps and customer tracking all ran on connected systems, and nothing worked on paper anymore.

Then a competitor was hit by ransomware and couldn't ship for 11 days. Two of this company's largest customers asked the same question: what happens if it's you? Nobody had an answer. A failed update the year before had stopped dispatch for most of a day, backups had never been fully restored, and the IT team guessed a real recovery would take at least three days.

3 daysestimated recovery
0tested manual fallbacks
2top customers asking

Our biggest customer asked what we'd do if our systems went down. The honest answer was: park the trucks and hope.

COO, client
02

Plan for the worst day, then practise it until it's boring.

Our fractional CISO led the work with IT and the hub managers. Hub fallback procedures were designed alongside a fractional COO, so they worked on a real loading dock, not just on paper.

Prioritise

Know what matters most

Every system ranked by how long the business could live without it, with recovery targets agreed by leadership.

Fallback

Keep trucks moving by hand

Printed route packs, offline load sheets, a phone tree for drivers and a simple way to update customers without the tracking system.

Recover

Bring systems back fast

Offline backups, a step-by-step restore order and restore tests run until core systems came back in under 9 hours.

The Engagement

5 months, step by step

From "park the trucks and hope" to a tested plan every hub can run. Here's how the engagement unfolded.

  1. Week 1–3

    Impact assessment

    Every system mapped and ranked by how long dispatch, delivery and billing could survive without it.

    24 systems ranked
  2. Week 3–6

    Backups & restore plan

    Offline backups set up, a restore order agreed and the first full restore test run. It took 61 hours.

    First test: 61 hrs
  3. Month 2–3

    Manual fallback

    Paper route packs, offline load sheets, driver phone trees and customer update templates built with each hub.

    8 runbooks
  4. Month 3

    Tabletop exercise

    Leadership, IT, hub managers and customer service walked through a ransomware morning, hour by hour.

    31 gaps fixed
  5. Month 4

    Hub drills

    Each hub ran a live shift on the manual fallback, one at a time, while restore tests continued in parallel.

    3 hubs tested
  6. Month 5

    Full outage drill

    All systems switched off for 6 hours across all three hubs. 92% of shipments still went out.

    92% kept moving
Inside the Outage Playbook

The first nine hours, planned

When systems go down, nobody has to guess. Every team knows its first move, and trucks keep leaving the dock.

0–30 minContain

Stop the spread

  • Isolate affected systems
  • Call the response team
  • Declare manual mode
30 min–2 hrsSwitch

Keep trucks rolling

  • Printed route packs
  • Offline load sheets
  • Driver phone tree
2–4 hrsInform

Customers hear it first

  • Pre-approved updates
  • Key account calls
  • Insurer & legal notified
4–9 hrsRecover

Systems back in order

  • Clean backups restored
  • Dispatch first, billing last
  • Data re-entered & checked
Every quarter: One drillA tabletop or a live hub drill every quarter, so new staff learn the plan and it never goes stale.
Month 2 · 8 runbooks Month 4 · 3 hubs drilled Month 5 · 6-hour drill
The Results

Ready for the bad day

Hours to recover core systems

IT team's estimate72 hrs
Tested restore plan9 hrs
020406080

Measured in a full restore test, not estimated.

Shipments moving in outage0%→92%
Hubs with tested fallback0→3
Time to switch to manual—→25 min
Missed windows, real 4-hr outage—→0
Cyber insurance premium—→−14%
CO

Two months after the drill, a supplier outage took our dispatch system down for four hours. The hubs switched to manual in minutes and we didn't miss a single delivery window.

COO, client
Your Turn

What happens if your systems go down tomorrow?

Our fractional CISO will build a response plan that fits your operations, test it with your teams and cut your recovery time from days to hours. Want the manual fallback built into how you operate? Add a fractional COO.

What we'd build for you
  • Impact assessment & priorities
  • Manual fallback runbooks
  • Tested backups & restore plan
  • Tabletop & live drills
Book a Strategy Call

30 minutes. No obligation.

Let’s Work Together

Contact Us

Sit back, relax. We will get back to you soon.

Related Case Studies