A conversation about backup internet options for small business that starts with a circuit name — “add LTE,” “the cable company can be the backup,” “they already have a second pair in the closet” — usually fails at the first shared entrance, not at the first SKU. A circuit name is a product label. It is not an option. If you do not write the work that must continue, the failure the second path is meant to survive, the traffic that is allowed in the degraded state, and who proves failover, the next familiar backup label still controls the buy.
This page is the first brief for that decision. It is not a carrier catalog and not a coverage map. It is the set of questions that turn a second invoice into a designed alternate path.
Why a backup label is not an option
Small offices often treat “backup” as a line item they can add to an existing quote. The quote then names a technology — fiber, cable, fixed wireless, a second SIM — and everyone assumes independence. That assumption is where the outage lives.
Two services can share a riser, a building entrance, a power feed, an edge firewall, or an upstream handoff and still look like two options on a proposal. Different brand names do not prove diversity. A wireless path that still depends on the same customer firewall or the same identity hop is not a second design. It is a second radio attached to the first failure.
An “always-on” checkbox has the same problem. Automatic shift is a pattern, not a written degraded state. Use the live note on why always-on failover is not a backup internet design when a slide has already replaced the brief, and the live note on why two circuits are not a redundancy design when a second invoice has been treated as proof.
What belongs on the options brief
Before anyone treats a circuit name as a shortlist, fill these rows:
- Work that cannot stop: payments, voice, identity, dispatch, cloud tools, and the access needed to restore service. A “keep the internet up” sentence is not that list.
- Degraded state: what continues, what pauses, and what “success” looks like to a user, not a link light. A copy of the primary megabit number is usually the wrong backup budget.
- Failure domain: last mile, building entrance, power, edge gear, upstream, wireless signal, and policy. Name the failure this option is meant to survive, and what it still shares.
- Security on the alternate path: firewall policy, identity, DNS, logging, and admin access that must survive failover. An unmanaged hole is not a backup option.
- Owner and test: who is alerted, who confirms the applications, who opens the carrier case, and when failback is proven. If no one owns the test, you do not have an option. You have a spare invoice.
- Commercial boundary: term, one-time charges, equipment, and what is still an estimate. A cheap monthly amount can hide construction, a landlord delay, or a path that was never surveyed.
The business internet redundancy and failover requirements worksheet is the companion for independence and failover evidence. The business internet quote-readiness checklist is the companion when the next step is a comparable request so unlike backup labels are not scored as one total.
How to read the usual small-business options
A second wired path is the right answer only when last-mile, entrance, and power are independent and the continuing traffic has a written budget. Fixed wireless or cellular is the right answer only when the named failure is one the radio does not share, and when failover has been timed against payments and voice. A “backup included” bundle can be a screening input. If it cannot name the degraded state, it is a package name, not an option.
Questions that belong in the first meeting
Ask the incumbent or a challenger to show, not describe:
- Which outage this backup path is meant to survive, and which shared facilities it still shares — not a coverage heat map.
- How priority applications behave after failover, including voice, payments, and identity, and what is blocked on purpose.
- How security inspection and logging stay in place on the alternate path.
- When the last failover test ran, what failed, who owns the next one, and how failback is proven.
If those answers are a circuit name and a promised monthly add-on, you do not have backup internet options for small business. You have a label.
What this page is not
This is not a carrier ranking, not a wireless product sheet, and not a claim that The Data Partner already designed anyone’s second path. Skip incentive talk, skip coverage maps as a substitute for a degraded-state brief, and skip any suggestion that a second SKU replaces a test. Write the rows. Then compare options. If you want a second set of eyes on the brief, start with a conversation.