Email is the account that recovers every other account
Forget the website for a minute. Your bank, your payroll provider, your Google Business Profile, your domain registrar, Stripe, QuickBooks, Instagram: every one of them has a "forgot password" link, and every one of those links sends a reset to the same inbox.
Whoever controls that inbox controls your business. That's the whole argument.
Most owners I talk to in Phoenix treat email as a utility, like the water bill. Something that just works until it doesn't. But it's the one account that unlocks all the others, and it deserves about twenty minutes of actual thought. Here's the version of that thinking I'd give a friend.
Three setups, ranked
Nearly every small business email falls into one of these buckets. Worst to best:
- A free consumer address.
desertbloomlandscaping@gmail.comor the Yahoo equivalent. Free, familiar, and looks like a hobby to anyone reading an invoice. - A mailbox your web host threw in.
info@desertbloomlandscaping.com, running on cPanel webmail or whatever came bundled with the hosting plan. - Your own domain on a real mail provider. Same
info@address, but the mail lives at Google Workspace or Microsoft 365, in an account registered to you.
The free address has one real problem: there's no business behind it. If your Gmail gets locked, there's a recovery form, but no support line to call, no admin console, no "I'm the owner, let me back in." You're a consumer, and Google treats consumers as a volume problem.
So the answer to "should my business use Gmail or a custom domain email" is a custom domain. But which custom domain setup matters just as much, and that's where the middle option bites people.
Why the middle one is the most dangerous
A host-provided mailbox looks exactly like the professional option. Same domain, same signature, same business card. The difference is who owns the login.
If your designer set up your hosting under their account and tossed in an email address, your inbox is a line item on their bill. When they stop paying, or you have a falling out, or the agency gets acquired and the old plan gets migrated, the mailbox goes with it, along with years of customer correspondence nobody knew was attached to that plan.
Shared hosting mail servers are also, bluntly, bad at sending. They share an IP with hundreds of other sites, some of which are spamming, and your reputation is tied to theirs.
If you're not sure whether your mailbox is in this bucket, Who Actually Owns Your Website? walks through finding out. The fifth thing on that list, where your contact form submissions land, is this same problem in a different outfit.
Deliverability, in plain terms
Three DNS records have a lot to say about whether your invoices land in an inbox or a spam folder. They're called SPF, DKIM, and DMARC. You don't need to understand them. You need to know they exist and that someone has checked them.
The short version: SPF lists who's allowed to send mail for your domain. DKIM is a signature proving the message wasn't altered. DMARC tells the receiving server what to do when the first two don't match. Since early 2024, Gmail and Yahoo have required all three from anyone sending in volume (Gmail's line is 5,000 messages a day), and they expect SPF or DKIM from everyone.
I was on a six-person team at a venture-backed company while it grew from about 50 people to over 200, and the expensive version of this looks like a full-time deliverability team and a dedicated sending IP. Your business needs the three records set correctly, once, and then it needs nobody to break them. That second part is where things go wrong.
What happens to email during a website move
Here's how a business goes dark for a day.
The new site is ready. The designer moves your DNS to the new host. They copy over the records they recognize, and they don't recognize the MX record (where mail gets delivered) or the records behind SPF and DKIM. The site comes up beautifully. Email stops. Or worse, email keeps arriving but outbound mail starts bouncing, and you don't notice for three days because nothing looks broken.
Every rebuild I've done starts with exporting the full DNS zone before anyone touches anything, then checking it after. It takes ten minutes, and it's the step that gets skipped when the person moving your site is a designer first and a sysadmin never.
If the person who did your last move has stopped answering, What to Do When Your Web Guy Disappears covers how to get the keys back.
The staff departure case
Who has the password to info@? Your office manager, or the guy who set up the computers back in 2019?
On a real provider, a departure is a short admin job: lock the user out and give the replacement access to the mailbox. The history stays. On a consumer Gmail that someone else created, the departure is a negotiation, and if it ends badly you're locked out of your own customer history and every password reset that routes through it.
The fix is boring. One admin account in the owner's name, with recovery going to the owner's personal phone. Everyone else gets a user account under it. That structure costs nothing extra, and it means a departure is paperwork instead of a crisis.
The inbox you forgot was email
Your website's contact form delivers somewhere. Ask the same question: is that an inbox in your name, or is it your old designer's Gmail, or a plugin's default address nobody has checked since launch? A surprising number of the contact forms I look at are sending leads into a void. Why Your Website Needs a Form covers what a form should actually be doing for you. To see where yours goes, run a proper test: submit it from an address that's never contacted your business and watch where the message lands.
What it costs
Google Workspace Business Starter and Microsoft 365 Business Basic both start at about $7 per user per month as of late 2026, if you commit for the year. Google's month-to-month price is $8.40. For a five-person shop that's roughly $35 to $42 a month, and both come with an admin console and a human on the other end of a support ticket.
Compare that to one invoice that landed in spam and got paid 45 days late, or one week locked out of your inbox while you re-establish who you are to your bank. It's the cheapest insurance in your tech budget, and it's the line item most owners never think about until the week it matters.
If you're setting up or moving a domain, the free Domain-to-Launch checklist walks through the registrar settings, DNS, and the three mail records in order. And if you'd rather not guess whether yours are right, send me your domain and I'll look. No sales call attached.
Do this today
Go to MXToolbox, type your domain, and run the SPF and DMARC lookups. If either one comes back "record not found," you now know something your competitors don't know about themselves. Forward the result to whoever handles your tech, or send it to me, and ask one question: who owns the account this mail is coming from?