Skip to main content
No disaster recovery plan

Your systems go down on a Tuesday morning. When do you get back up?

Most print, embroidery, and decoration businesses don't have a business continuity disaster recovery plan. Not because they don't care — but because DR feels like something for enterprise IT teams. Until the server fails, the hosting goes down, or ransomware locks every screen. Then the cost of not having a plan becomes very visible, very quickly.

Or book a call directly
PROBLEM SCHEMATIC — UNTESTED RECOVERYA backup is not a recovery planTHE RESTORE PATHfound out on the worst dayLIVE SYSTEMproduction dataBACKUPruns nightlynobody checksRECOVERED?never rehearsedbackup runs— yesrestore tested— neverwho knows how— one personThe nightly job proves data was copied. Not that the business comes back.
— Does this sound familiar?
You don't have a written plan for what happens when critical systems go down
You assume your hosting provider or software vendor handles backup and recovery
Recovery from a previous outage took days, not hours
There are backup processes documented somewhere — but you're not sure they still work
You couldn't answer 'how long can we afford to be offline?' without guessing
Key operational data exists in only one place
The last time you tested a restore, it didn't work
— Why it happens

The root causes

Understanding why the problem exists is the first step to fixing it — and knowing whether you're looking at a system problem or a process problem changes everything.

01

DR is postponed until it happens

Disaster recovery planning always feels like a problem for next quarter. The business is running, the system is working, and there are more immediate things to fix. The cost of that deferral only becomes visible when the system stops.

02

Assuming the vendor handles it

Most software vendors and hosting providers have uptime guarantees — but those rarely cover your specific data, your specific recovery sequence, or your specific acceptable downtime. Their backup is not your DR plan. Backup and disaster recovery are different things. A backup stores your data. A disaster recovery plan defines how you restore operations — which systems come back first, in what order, within what time target. Cloud backup is not a DR plan.

03

No one is accountable for recovery

In businesses without a dedicated IT role, the question 'who is responsible for getting us back online?' doesn't have a clear answer. Come outage day, everyone assumes someone else is handling it.

04

Cost of downtime is invisible until it happens

Lost orders, halted production, missed despatch deadlines, overtime to catch up, and reputational damage — none of these appear on a balance sheet until the outage is over. By then the cost has already been incurred. For a small manufacturer, the RTO (recovery time objective) and RPO (recovery point objective) are rarely defined — which means nobody knows how much downtime is acceptable until they are in the middle of it.

— How I help

What happens when you call

I assess your current technology stack, backup architecture, and recovery capabilities — then give you a practical DR plan built around your actual business. Not a 50-page IT document. A clear, prioritised set of actions covering what to protect first, how fast you can realistically recover each system, and what it would cost to reduce that recovery time. Plus a simple test schedule so you know the plan works before you need it.

Let's talk about what's happening

The first call is free. 60 minutes. No sales pitch — just a direct conversation about your situation.

One day on site
Written report in 5 days
3× Clarity Guarantee
No vendor agenda
Book a free call Or book a call directly
Get this fixed

Retained operational oversight

A fractional CTO who owns your continuity plan — tested, current, and ready before the crisis, not during.

See how it works
Further reading

From the blog