Succession planning. Disaster recovery planning. We should have these.
Not having them can lead to hasty, unwise decisions. They should include prioritising tasks and cascades/durations of fall over.
There's not necessarily reason they mean dropping anyone either. Even if exclusively looking at a financial impact there are costs of switching, costs that might be low for a server needing restoring to high for acquiring knowledge specific to your field or product, or a whole lot in between, for example.
Just have a plan. If you don't, be aware of potential for flawed decisions made in haste.
I also see similar WordPress themes appear on supposedly independent sites with individual authors. Similar down to the email sign-up popups.
I get that some WP themes are more popular than the bazillion available, but the consistency in look and feel between a Malaysian immigrant to New York cooking curries I know aren't that Malaysian and a stay at home mom in Ohio doing baking that may have been passed down by a great aunt that tweaked a King Arthur Flour recipe is often remarkable.
OK, I get you. I think we're coming from different angles. You're concerned about getting into a network, I'm concerned on not identifying identification.