If your bids still go out from a personal Gmail or Yahoo address, this guide is for you. A company address on your own domain looks more professional, but the bigger win is control: the email belongs to the business, not to one person’s login.
This is the order to do things in, not every click. Each step has to be finished before the next one makes sense:
Five steps, in order
- 1
Own the domain
Make sure the company can renew the name and recover the registrar login. Registering a domain doesn’t create inboxes. - 2
Choose an email host
Based on the apps you already use, who will run it, and the budget. - 3
Decide the addresses
One mailbox per person, one name pattern, and role addresses like bids@ or billing@. - 4
Do the three DNS steps
Prove you own the domain, route mail to the host, and publish its authentication records. - 5
Test both ways
Including a role address, before a customer ever sees the address.
Creating a business email starts with what the company owns
A domain and an email host are two different purchases. The domain is the name after the @ sign. Registering it doesn’t create any inboxes. The inboxes live with an email host you choose separately. So getting a business email isn’t “buy a name and stop.” It’s “own the name in a way the company can recover, then attach a host.”
That means two logins. The registrar login renews the name and controls where it points. The email host login creates mailboxes and decides who administers them. Both need a recovery path that doesn’t run through the personal inbox the business is trying to leave behind.
Turn on auto-renew. If the domain lapses, every address on it goes with it. The rest of this checklist is our recommendation:
Ownership checklist
- The company’s name on the registrar account, where the registrar allows it.Recommended
- Auto-renew turned on, so a missed card doesn’t take the name down.
- Recovery details and a second sign-in factor that aren’t the personal inbox you’re moving away from.Recommended
- At least two people who can reach a domain administrator account.Recommended
- A written note of which email host you use.Recommended
Both big providers treat domain changes as admin work. Microsoft says adding a domain takes a Domain Name Administrator, not a regular user, and Google requires the Domain settings administrator privilege. Neither requires a second person. That part is our advice.
Here’s why it matters. Picture the owner on a job with no signal when a renewal notice or an admin reset comes in, and the only recovery path is a personal inbox they can’t reach. If the owner is the only one who knows the registrar password, and it lives in that inbox, fix that before buying a single mailbox.
Choose the email host for how you already work
Pick the host based on three things: the apps your office already uses, who will run the admin side, and the budget. Google Workspace and Microsoft 365 are the usual choices, and neither is automatically right for contractors. If your office already lives in one of them, that’s a strong reason to stay.
“Apps you already use” means the documents, chat and email your office and field team open every day, not a feature contest. “Who runs it” means the person who’ll hold the admin account after launch, not whoever enters the card number on day one. Comparing Google Workspace and Microsoft 365 for an office-and-field team is its own guide.
Budget is a separate question from owning the domain. Owning the name says nothing about what the mailboxes cost. That depends on the plan and on how many people need a mailbox. We cover what Google business email costs separately.
Give each person a mailbox, then add role addresses
Decide the addresses before anyone touches DNS. Give each person their own mailbox, keep one name pattern, and add a few role addresses for jobs rather than people. For a made-up company at example.com, that might look like:
- owner@example.com for the owner
- alex.estimator@example.com for the estimator, and a mailbox of their own for the field lead, not a shared login
- bids@example.com and billing@example.com as role addresses
A role address can be set up a few ways, and they behave differently. An alias forwards mail to someone’s mailbox. It isn’t a team inbox. A shared mailbox or a distribution list are different again. Choosing between them is its own decision: shared mailbox or distribution list.
Two questions to ask whoever sets it up: can people outside the company email the shared address, and where do copies of sent messages end up? Once an admin has given someone access, they open the shared mailbox in the version of Outlook they use. We walk through adding a shared mailbox in Outlook separately.
Prove the domain, route mail, and authenticate
These three DNS steps come only after ownership and addresses are settled. The exact records differ between Microsoft and Google, depend on what else sends email as your domain, and change over time, so a table copied from a blog will eventually be wrong. Use your provider’s current instructions for each step.
Prove you own the domain
In Microsoft 365, a Domain Name Administrator adds the domain and proves ownership before any service records go in, using whichever method the admin center shows that day (see Microsoft’s guide to adding a domain).
In Google Workspace, you copy a verification value from the Admin console and confirm it. That value is unique to your account, so never paste one from somewhere else. If you bought the domain through Google’s partner when you signed up, it may already be verified (see Google’s domain verification guide).
Route mail to your provider
With Microsoft, changing the mail routing (MX) record sends all new email for the domain to Microsoft 365, so create the mailboxes first. Changing the record doesn’t move old email. That stays with the old host unless someone migrates it. Microsoft’s DNS records guide says to use whatever the admin center displays, and warns that incorrect DNS can cause email outages.
With Google, the order is: create the user accounts, publish Google’s MX record, remove any other MX records, then activate Gmail (see Google’s MX record guide and Gmail activation steps). Old or incorrect MX records left in place can stop email working properly. Google publishes how long changes can take to be recognized, but treat that as a guide, not a promise.
Publish the authentication records
Authentication records (SPF, DKIM and DMARC) tell other mail systems your messages are genuine. Microsoft’s DNS guide covers SPF and DKIM and points on to DMARC. If you already have an SPF record, merge the new entry into it rather than adding a second one.
Google lists SPF, DKIM and DMARC as recommended after the MX record. Its SPF guide explains that the record lists every service allowed to send as your domain, not just your mailbox host. A website contact form or another tool that sends as your domain counts too. For DKIM, you generate a key, publish it, then turn authentication on. Some partner signups handle this for you.
Test both ways before a customer uses the address
Don’t put the new address on a bid until you’ve tested it. From a personal account, send a message to bids@ and to someone’s own mailbox. Then reply from each. One direction isn’t enough: if mail arrives but replies don’t leave, or replies leave and never arrive, the address isn’t ready. Hold off on printing it on proposals or the website until both directions work.
A successful test is a good sign, not a guarantee that every future message will land in the inbox.
Before the first customer email goes out, also:
- Confirm a second person can recover both the registrar and the email admin, and write down who.
- Turn on your provider’s second sign-in factor.
- Name one ongoing administrator, with a company mailbox, rather than a password saved only in the old personal inbox.
Security comes next
Once the address works, the next step is protecting it. Email security best practices for contractor teams covers the basics. For messages with sensitive details, see how to send a secure email in Outlook or Gmail.
If you’d rather have someone else handle the registrar and email host side, see our business email support for contractors.