Yes, if you already own a domain, or are about to. An address like name@yourbusiness.com tells a customer they are writing to a business, it stays yours when an employee or a provider leaves, and with three small settings in place your messages reach the inbox instead of the spam folder.
A free address is fine for the first week of a business. After that, it starts to cost you in ways that do not show up on any bill: replies that never arrive, quotes that look less serious than they are, and an inbox that belongs to whoever created it. Here is what changes when you switch, and what the switch actually involves.
What is wrong with a Gmail address for a business?
Nothing is wrong with Gmail as a tool. The problem is the address.
- It looks temporary. A quote from yourbusiness@gmail.com and a quote from hello@yourbusiness.com can be identical, but the second one reads like it came from a company that will still be there next year.
- Anyone can make a similar one. If you are smithplumbing@gmail.com, someone else can register smith.plumbing@gmail.com tomorrow and write to your customers. A domain is yours alone, so an address on it cannot be copied in the same way.
- It does not match your website. A customer reads yourbusiness.com on the van, the card and the site, then gets a reply from a different name. Small mismatches like that are exactly what people notice when they are deciding whether to trust you.
Who owns the address when someone leaves?
This is the part owners usually find out too late.
A free account belongs to the person who created it. If your first employee set up the shop inbox on their own phone, with their own recovery number, the address is effectively theirs. When they leave, you either negotiate for the password or start again, and every customer, supplier and directory that had the old address keeps writing to it.
On your own domain, you are the administrator. You can create an address for a new person on their first day, take it back on their last, and point their mail to someone else so nothing is lost. The address maria@yourbusiness.com can outlive Maria's job without anyone needing her password.
The same logic applies to the domain itself. If the domain is registered in the name of a former designer, your email depends on them too. Who owns your website explains how to check whose name it is in.
Does your own domain help your emails reach the inbox?
It does, as long as the domain is set up properly.
Large mail services check whether a message really comes from the domain it claims to come from. Google's own email sender guidelines (support.google.com, "Email sender guidelines") state that since 1 February 2024 every sender writing to personal Gmail accounts must authenticate with SPF or DKIM, and that bulk senders need SPF, DKIM and DMARC.
In plain words:
- SPF is a public list of the servers allowed to send mail for your domain.
- DKIM is a signature on every message that proves it was not changed on the way.
- DMARC tells receiving servers what to do with a message that fails both checks, and can send you reports about who is using your name.
All three are short text records in your domain settings. Your mail provider gives you the exact values, and they take a few minutes to add when you know where to look. Without them, your quotes and invoices are more likely to land in spam, and anyone can send mail that pretends to be you.
What do you need to set it up?
Three things:
- A domain you control, ideally the same one your website uses. If you have not chosen one yet, .ca or .com walks through the choice.
- A mail provider. The common choices are Google Workspace and Microsoft 365, which give you the familiar Gmail or Outlook apps with your own address. Many hosting plans also include basic mailboxes. For most small teams, Workspace or Microsoft 365 is the easier one to live with, because the apps, the calendar and the phone setup are the ones people already know.
- The DNS records that connect the two: MX records that tell the world where your mail goes, plus SPF, DKIM and DMARC.
Mail providers charge a monthly fee per mailbox, so the cost depends mostly on how many people need their own inbox. The rest is a one-time setup.
How many addresses do you actually need?
Fewer than you think.
- One mailbox per person who writes to customers in their own name.
- Shared addresses as aliases, such as info@, orders@ or bookings@, delivered to whoever handles them. An alias is a second name for an existing inbox, so it usually does not need a mailbox of its own.
- One address on the website. Pick the address customers should use and put that one everywhere: the contact page, your Google Business Profile, invoices and social profiles.
If three people need to see the same requests, a shared alias or a group is easier than three people logging into one account with one password.
How does email connect to your website?
More closely than most people expect, and this is where launches go wrong.
Your domain holds the settings for both. The records that point the domain to your website sit right next to the records that deliver your email. Move the domain carelessly, or let someone "reset the DNS" during a redesign, and the website goes live while the email quietly stops. Nobody notices until a customer phones to ask why you never replied.
Your website also sends email: every contact form, booking request and order confirmation. Those messages should be sent through your own domain, with the same authentication, or they end up in spam just like a badly set up inbox. Why contact form emails are not arriving covers that side in detail.
When I build or move a site, I read the existing mail records before touching anything, copy them across exactly, and send a test message both ways after the switch. It is a short check, and it is the one that protects the part of the business that actually brings in work.
How do you switch without losing mail?
Plan it as a short project, not a weekend surprise.
- Set up the new mailbox first and check that sending and receiving both work.
- Import your old messages and contacts. Google Workspace and Microsoft 365 both have import tools for this.
- Keep the old address open and forward it to the new one for a few months, so late replies still reach you.
- Change the address everywhere customers see it: website, Google Business Profile, invoice template, email signature, social profiles, supplier accounts.
- Tell your regular customers once, in a short message from the new address.
The old address does not need to disappear on day one. It just needs to stop being the one you give out.
When can a free address wait?
If you have no domain and no website yet, and you are still testing whether the business works, a free address is a reasonable start. Make it one you would not mind a customer reading, set it up with your own phone number for recovery, and plan to move once you register a domain.
What I would not do is register a domain, build a website on it, and keep answering customers from a free address. At that point the hard part is done, and the email is the last step.
The short version
- Use an address on your own domain once you have one.
- Make sure the domain and the mail accounts are in your name, with you as the administrator.
- Add SPF, DKIM and DMARC records, so your mail is trusted and nobody can easily pretend to be you.
- Keep the mail records in mind whenever the website moves.
- Switch in steps, and keep forwarding the old address for a while.
Email setup and moving the mail records safely are part of every site I build, and what each type of project includes is on websites. If your site and your inbox are already tangled together and you are not sure what touches what, send me your site and you will get a fixed price and a launch date the same working day.