Marketing Leadership · · 4 min read

What Three Unrelated Outages Tell a CEO About Vendor Dependence

By Scott Hashisaki, Fractional CMO & Growth Executive

Microsoft 365, FAA air traffic communications and Chase online banking all went down in five days. Three questions every CEO should ask about vendor dependence.

Between Thursday and Monday, three of the most relied-on systems in the country stopped working.

On Nov. 12, Microsoft 365 users lost Outlook, Teams and Copilot for hours after servers became unexpectedly unavailable. On Nov. 13, the FAA halted departures nationwide after a contractor's router upgrade at a remote Arkansas facility overloaded the air traffic control network, according to Transportation Secretary Sean Duffy. On Nov. 16, Chase customers couldn't reach online banking because of what the bank called a technical issue, and some Zelle payments with other banks stalled with it.

None of these were connected. None were reported as attacks. That's what makes them useful to a CEO: they're ordinary failures, the kind every business is exposed to every day.

Three questions are worth asking your leadership team this week.

1. Where is our single point of failure?

In every one of these outages, one component stopped and took everything downstream with it. Most growing companies have the same shape. One email platform. One phone system. One CRM receiving every web lead. One payment processor.

That isn't automatically wrong. Consolidation is efficient. But you should know exactly which single failure would stop revenue, and for how long you could tolerate it.

2. How concentrated are our vendors, really?

Many businesses think they have redundancy because they use several tools. Then you trace them and find they all sign in through the same identity provider, run on the same cloud, or route through the same carrier. Five logos, one dependency.

Ask for a one-page map: each customer-facing function (calls, forms, email, scheduling, payments) and the vendor underneath it. The overlap usually surprises people.

3. Who owns the fallback plan?

This is the question most companies can't answer. IT owns the systems. Operations owns the process. Marketing owns the lead flow. When something breaks, everyone assumes someone else has the backup plan.

Name one owner. Give them a short written plan for each critical function: what we switch to, who flips it, and what we tell customers. Then test it once, on a quiet day, before you need it.

The real lesson

You can't prevent Microsoft, the FAA or your bank from having a bad day. You can decide in advance how much of your business stops when they do.

That's a leadership decision, not an IT ticket. If you'd like an outside view on where your revenue depends on a single vendor, [let's talk](/contact).