Workflows

The Business Email Setup Most Small Business Owners Get Wrong

Most small business owners know they should have a professional email address. Fewer realize the setup behind it can cause problems: email going to spam, a domain that's easy to impersonate, and replies that still come from a personal Gmail account.

The Business Email Setup Most Small Business Owners Get Wrong

Most small business owners know they should have a professional email address. Plenty have taken the step of registering a domain and setting up something that looks the part: [email protected] instead of [email protected].

What fewer owners realize is that how that email address is configured matters as much as what it says.

The Visible Problem: What @gmail.com Signals

When a prospect receives a proposal, an invoice, or a follow-up from a Gmail address, they notice. They may not say anything. But it registers as a data point about how established this business is.

A professional email address on your own domain is a baseline credibility signal. Like having a business phone number instead of a personal cell, or a business address instead of a home address, it tells clients this is a real operation.

Most business owners understand this eventually. Some are still on Gmail because they haven't gotten around to fixing it. Others think they already have. (Why Your Business Email Shouldn't Be @gmail.com covers the credibility side.)

The Less Visible Problem: The Forwarding Address Trap

A common approach when a small business owner decides to look more professional: register a domain, create [email protected], and forward it to an existing personal Gmail account.

The address looks right and email arrives normally, so it seems solved. It isn't quite.

When you reply to a client from a forwarding setup like this, you aren't sending from [email protected]. You're sending from your personal Gmail account, because that's the account you're actually in, and your replies show that address as the sender.

More importantly, a setup like this usually has no email authentication on the domain: no SPF record listing which servers are allowed to send for you, no DKIM signature proving your messages are legitimate, and no DMARC policy saying what should happen when a message fails those checks.

To a receiving mail server, your domain is an unverified sender. Your emails are more likely to go to spam. And your domain is easy to impersonate: anyone can send emails that appear to come from you, and nothing on your domain tells the receiving server to block them.

You won't see any of this. It happens in other people's inboxes and mail server logs, and you usually find out only when a client says they never got your email.

What SPF, DKIM, and DMARC Actually Do

These terms show up in every email help page and almost never get explained clearly. Here's what they mean for a small business owner:

SPF (Sender Policy Framework): A record on your domain that lists which mail servers are authorized to send email from it. When a receiving server gets a message claiming to be from your domain, it checks this record. If the sending server isn't on the list, the message gets flagged.

DKIM (DomainKeys Identified Mail): A cryptographic signature attached to your outgoing emails. It lets receiving servers verify that the message was actually sent by you and wasn't changed in transit.

DMARC (Domain-based Message Authentication, Reporting, and Conformance): A policy that tells receiving servers what to do if a message fails SPF or DKIM checks: deliver it anyway, quarantine it, or reject it outright. It also provides reporting so you can see when someone is trying to send email that impersonates your domain.

None of these need ongoing maintenance. They're DNS records and server settings: set them once and they keep working in the background. Until they're set, your domain goes without them, whether or not you ever see the effects.

Most small business email setups are missing one or more of these records. Many are missing all three.

What a Properly Configured Business Email Looks Like

A properly set up business email platform (Google Workspace and Microsoft 365 are the two most common for small businesses) handles all of the fundamentals.

Your email address sends and receives from your own domain, consistently, from all devices. When a client replies to you, they're replying to your business address, not to a personal account sitting behind a forward.

SPF, DKIM, and DMARC are configured on your domain. Your email is authenticated, and your domain is protected.

A catch-all address is in place, so emails sent to any address at your domain, regardless of whether that specific address exists, arrive somewhere instead of bouncing back to the sender. If a client misremembers your address, or uses an old one from a past form submission, the message still reaches you.

Inbox filters and rules route incoming mail automatically, so messages from clients, vendors, newsletters, and automated notifications end up where they belong instead of competing for attention in one crowded inbox.

A professional signature is attached to every outgoing message: your name, title, business, and contact information, consistently formatted.

That's the minimum for business email, and it isn't hard to get to.

Why This Is Worth Fixing

The case for fixing your email setup goes past appearances, though the credibility part is real.

Emails that go to spam don't get read. Follow-ups that aren't authenticated are more likely to be filtered. A domain without DMARC protection is an easy target for anyone who wants to impersonate you. And a forwarding setup that sends replies from a personal Gmail address confuses clients and leaves your business records scattered as the business grows.

Most owners who check their email setup find it isn't quite what they thought. The fix isn't complicated. You just have to know what to set up.

If you want to see how this plays out in practice: I recently came across a business owner whose missing DMARC record turned out to be just the surface of the problem. When I traced it, the same misconfiguration showed up across most of his franchise network. It came from a hosting provider's default account setup, which never included authentication records. The full case study is here: One Spam Folder. Three Layers of Cause.

If you'd rather not touch DNS records yourself, the email fix is this whole setup, done for you.

Enjoyed this? Get more practical tips in your inbox.

Every so often I send a short note about something I fixed for a small business, or a tool worth knowing about.