How So Many of Us Ended Up on Google
Nobody sits down at the kitchen table on the first day of their business and decides to run the whole thing through one company. It happens one sensible choice at a time... a free email address because you needed one by Tuesday, a shared folder because a client sent you a link, a calendar because it was easily accessible on your phone.
A few years later, that same company holds your email, your files, your calendar, your client forms, and the login to half the other apps you use. You didn't choose a tech stack so much as grow one, the way a junk drawer fills up without anyone ever deciding it should.
That isn't a personal failing, and it isn't an accident on the companies' side either. Understanding how it happened makes it much easier to decide, calmly, which parts you'd like to keep and which you'd like to loosen.
How a tech stack quietly builds itself
Three forces do most of the work:
Free is the easiest yes. When you're starting out and every dollar counts, a free email account and free cloud storage feel like the responsible choice. Most beginner advice says exactly that, and recommends pairing free Google or Microsoft tools to keep things simple.
Connected is convenient. Once you're in one ecosystem, everything inside it works together beautifully. Your calendar reads your email, your forms land in your drive, and your documents share themselves with one click. Leaving any single piece starts to feel like unplugging a whole wall of appliances.
"Sign in with Google" is one click away. Every new app offers it, and it saves you from inventing yet another password. Each time you click it, though, another door in your business opens with the same key.
None of these choices were wrong, and I'd make several of them again. They add up to something worth seeing clearly, though, because together they build a business that leans its full weight on one account.
The convenience is real, and so is the cost
To be fair, though, one ecosystem genuinely is simpler. Fewer logins, fewer bills, and fewer things to learn matter a lot when you're running a business on a few hours a week.
The cost shows up in a single phrase from the engineering world: single point of failure. That's any one piece which, if it breaks, takes everything connected to it down too. When your email, files, calendar, client forms, and app logins all hang off one account, that account is your single point of failure.
Most days it's invisible. It only becomes visible on the day an account gets locked over a failed payment, a misfiring fraud check, or a hacked password, and suddenly you can't reach your inbox, your client files, or any of the apps you signed into with that one key. The question isn't whether a big company is trustworthy. It's how much of your business you'd lose in an afternoon if one account went dark.
The quiet protections
You don't need to leave an ecosystem to make it less fragile. Three small changes shrink the damage a single lockout can do.
Use your own domain for email. When your address is you@yourbusiness.com and you control the domain, you can point it at a different email provider and keep the exact same address, so clients never notice a thing. With a free Gmail or Outlook address, the address itself belongs to the provider. Any provider can still lock you out, including the privacy-friendly ones, but your own domain means the lockout costs you an inbox rather than your identity.
Close a few "Sign in with" doors. For the apps that matter most, switch to a regular email login with its own password (a password manager makes this painless). That way one locked account doesn't lock you out of everything else.
Keep a copy somewhere else. A regular export of your files and email to a drive you own means a lockout costs you access for a while, not your entire library and history.
If you do switch to your own domain, keep it at a registrar separate from your website host, with auto-renew and two-factor login turned on. The domain becomes the new key to your business, so it deserves its own lock.
Your one move: name your single points of failure
Go back to the tech stack map from Day 1 and circle any account that other things depend on. That usually includes your main email, your cloud storage, and whichever login you use for "Sign in with."
For each circled account, write one sentence that starts with "If this got locked tomorrow, I'd lose..." and finish it honestly. If the sentence runs long, that's your clearest place to start, whether that means moving to your own domain, closing a few sign-in doors, or simply scheduling a monthly backup.
You're not trying to rebuild your business this week. You're just making sure you know where the load-bearing walls are.
Where we go from here
Most small business stacks weren't designed; they accumulated, one reasonable choice after another. Seeing that clearly is what turns a vague unease about Big Tech into a short list of things you can actually do something about.
The next post (Day 3 of the email course) looks at what's being collected while you work, from the data your tools gather about you to the analytics you might be running on your own visitors without thinking much about it.
If you'd like a quick snapshot of where your own business stands, take the How Private Is Your Business? self-check, and join the free 5-day email course Your Private Business. And if writing that "I'd lose..." sentence surprised you, I'd love to hear about it.
