You bought the domain, you've got a Gmail you've been using in the meantime, and now you want you@yourcompany.com to actually work without paying an MSP $200/month. The honest answer: it's a Saturday-afternoon job, not a three-day project. Five steps a non-tech can do in order — and one honest answer for when the DIY path isn't worth it.
"Business email" means a real mailbox on your own domain (like you@yourcompany.com) routed through a provider that takes care of spam filtering, mobile sync, and the actual sending. Two-minute checklist before the longer guide:
1. Buy the domain (Namecheap, Cloudflare, Google Domains — anywhere cheap).
2. Pick a provider (Google Workspace or Microsoft 365 — same cost, different feel).
3. Add the provider's DNS records to your domain and create your first mailbox.
If not, walk through the five fixes below in order.
There are two providers worth considering for a small business and a long list of second-tier alternatives you'll regret. Both are around $6/user/month and both include mail, calendar, contacts, and mobile sync. The decision isn't about price or features — it's about which office suite your team already lives in.
Pick Google Workspace if your team already uses Gmail, Google Docs, or Google Drive. Pick Microsoft 365 if your team lives in Outlook, Word, and Excel. If neither, flip a coin: the migration cost between them is real but the daily-friction cost of using the "wrong" one is much larger over five years.
Where this usually goes wrong: a business picks the cheaper reseller they found on a comparison site ($3/user/month) and a year later discovers the reseller disappeared and there's no way to migrate out without losing every archived email. Stick with the two big providers' first-party plans.
Once you've signed up for Workspace or M365, the provider gives you a short list of DNS records to copy into your domain registrar. The records tell the rest of the internet "the mail for yourcompany.com lives at Google" (or Microsoft). Without these records, mail sent to your address bounces back to the sender.
The ones you'll paste in (most registrars hide this under "DNS" or "Advanced DNS"):
An MX record tells other mail servers where to deliver mail for your domain. Workspace gives you a value like smtp.google.com; M365 gives you something like yourcompany-com.mail.protection.outlook.com. Copy it exactly, including the priority number (it's the number before the host: 1 smtp.google.com).
A CNAME record (one for each provider) verifies you own the domain. The provider generates a long hostname like gv-abcdef1234.yourdomain.com — paste the full host and the target exactly.
Where it usually goes wrong: people paste the records into the wrong DNS section (some registrars have a separate "Email" tab that's actually for their own email service, not yours). If your MX record went into the wrong place, mail will still bounce after an hour. Move it, then wait ten minutes.
In the provider's admin console (admin.google.com for Workspace, the M365 admin center for Microsoft), "Add user," give them the address you want, and assign a temporary password. They'll be prompted to change it on first login.
After your real mailbox works, set up a catch-all route — every email sent to any address at your domain that doesn't exist (typos like info@yourcompany.com when you only made contact@) lands in one central inbox you control. This catches real leads that would otherwise bounce. The setting is under "Routing" or "Mail flow" in either provider — ask for "catch-all address" and point it at your real mailbox.
Where it usually goes wrong: businesses skip the catch-all and lose six months of inbound leads that were sent to addresses nobody owned. Set it up on day one, even if you only have one mailbox.
This is the step most small businesses skip — and then wonder why their customers' replies land in Gmail's spam folder, or why they can't send more than fifty emails an hour without getting blocked.
SPF is a single TXT record that says "only these servers are allowed to send mail claiming to be from my domain." Workspace publishes the value automatically; you'll add it as a TXT record (not an MX, not a CNAME) at your registrar. M365 gives you a similar value.
DKIM is a second TXT record that lets the receiving server cryptographically verify the message wasn't changed in transit. Same idea — the provider generates a long string, you paste it as a TXT record.
DMARC is a third TXT record that tells receiving servers what to do with mail that fails SPF or DKIM (none, quarantine, or reject). Start with p=none for the first month — that just collects reports — and tighten to p=quarantine once you're sure nothing legitimate is failing.
Where it usually goes wrong: businesses paste these as MX records or CNAMEs. They are TXT records. The "type" dropdown in your registrar matters more than the values.
The provider's webmail works out of the box. Getting it onto devices is where small businesses burn an afternoon.
On phones: don't set up IMAP manually — download the provider's official app (Gmail for Workspace, Outlook for M365). It handles the server settings, push notifications, and calendar sync automatically.
On laptops: same advice. Use the provider's desktop app or the browser version. Manual IMAP/POP setup is for the rare case where the device doesn't support the app — and even then, the provider's setup wizard walks through it.
On the office printer (for "Scan to email"): the printer uses a generic SMTP gateway. Both Workspace and M365 publish an SMTP relay for this exact use case. Paste the host, port 587, your full email as the username, and your app password (not your real password — the printer needs an app password).
Where it usually goes wrong: businesses use the printer's "Scan to email" feature with the provider's normal SMTP and it silently fails for a year. The printer is sending unauthenticated mail that the provider rejects. The SMTP relay is the fix.
If you've walked through the five steps and mail is still bouncing, landing in spam, or refusing to send, the rest of the rabbit hole — PTR records, IPv6 glue records, BIMI, advanced DMARC alignment, migration from a previous host — takes more time than it's worth for a single inbox.
Here's the honest answer: if your team has spent more than an afternoon on email setup this quarter, that's not an email problem. It's a process problem. The same way businesses automate invoicing or onboarding or reporting, the right move is a small done-for-you setup, not another week of DNS testing. (And if the device on your network that's giving you trouble today is the printer instead of the inbox, the same shape of fix lives at our printer-offline guide — five fixes, ten minutes, same tone. If the problem holding up the inbox is revenue cycle instead of mail flow, the same shape of fix lives in our invoice-chasing guide.)
We automate one business process for $89 — same-day fix or your money back. No retainer, no monthly fee. You describe what's broken, Nikita builds the fix.
Not sure what counts? See a real example: the Shopify-to-Sheets guide.
Start — $89OneFix is a small automation service for small businesses — we don't sell domains, mailboxes, or migration plans. If you'd rather keep troubleshooting, our refund policy doesn't apply (you haven't paid us anything yet). Back to onefix.tech.