The Backup Strategy Nobody Asks About Until They Need It

I run a small WordPress studio — webmaster.co.ua, 18 years, 235+ projects. Backups are the least glamorous line item in any proposal, and for years we treated them that way too — mentioned once, rarely explained, easy to skip. Then we had one bad incident, and it became the thing we now explain most carefully.

Clients assume backups exist by default, until the moment they don't. Nobody asks "do you back up my site" during scoping — it's assumed, the way people assume a car has brakes. That assumption is fine right up until a plugin update corrupts the database or a hosting migration goes wrong, and suddenly a missing backup isn't a technical oversight, it's the worst conversation you'll have with a client all year.

Hosting-provided backups are not the same as an actual backup strategy. A lot of budget hosting plans advertise "daily backups" that turn out to be a single rolling snapshot, overwritten daily, stored on the same infrastructure as the live site. If that infrastructure fails, the backup fails with it. We now treat off-site, versioned backups as a separate line item from hosting — because they solve a different failure mode.

The real test of a backup isn't whether it exists, it's whether you've restored from it. We didn't actually know our backup process worked until we were forced to use it under pressure. Now we test a full restore periodically, on a non-live environment, specifically so the first time we ever restore something isn't during an actual emergency.

Explaining this upfront changes how clients perceive incidents later. A client who knows backups exist and how recent they are reacts to a bad update very differently than one who's never thought about it — the first asks "how old is the last backup," the second panics. That difference in reaction is entirely a function of one five-minute conversation at project start.

If backups are a line you gloss over in your own proposals, it's worth making them explicit — not because clients will pay more for it, but because it's the cheapest trust you'll ever build, redeemed only once, at exactly the moment you need it most.