A feature is useful only when staff can operate it, the customer path still works, and someone can recover the account or data. Boring is a compliment when money is moving.

• One person is the only manual.
• An outage plan that begins after the outage.
• A tool added because a demo looked smart.
• No export, backup, owner, support route, or replacement path.

• Write the five jobs that cannot stop.
• Name the owner and backup operator for each.
• Test offline, restore, recovery, and support steps.
• Remove features that create more work than value.

Start with the jobs customers notice first. For each one, a quiet setup answers four questions: who owns it, who runs it when that person is out, how it keeps working during an outage, and how it comes back after a mistake.

• Taking payments: a second reader or a phone-based option, offline payment rules read before you need them, and card readers on the staff network, not the guest Wi-Fi. See what to check when a card reader drops.
• Email: accounts in the business’s name, two people who can sign in as an administrator, and two-step sign-in with a backup method. See who should own business passwords.
• Booking: a regular export of upcoming appointments, and a known way to reach customers if the booking tool goes down.
• Files: one agreed home for shared files, a backup kept apart from the working copy, and a restore you have actually tried. See how to know files are really backed up.
• Phones: calls that ring the right people, voicemail someone checks, and the same number everywhere customers find you. See how to test a business phone number.

A new tool earns its place when it removes a step. Be wary when staff type the same details into two systems, when only one person knows how a setting works, or when a renewal arrives and nobody can say what the tool does. A yearly look at every paid tool catches most of these before they turn into a Saturday problem.

Change one thing at a time, outside busy hours, with a way back. Test the job the change touches, then write down what changed and what to check first if something breaks. A plain note today makes the next problem faster to understand.

We keep what works, connect what should talk, and build only when the business needs to own the tool. No confetti required.

Get a plain-English second opinion

Product features and rules can change. Use the linked source as the current word.

• CISA small and midsize business resources — Official steps for phishing, passwords, an extra sign-in check, updates, backups, and encryption.