Do I need a paid licence for every address like info@ or billing@?

No. You need a licence for every person who signs in and sends. Addresses answered by one person can be aliases on that person's account, and Google Workspace allows up to 30 alternate addresses per user at no extra cost. An address several people answer is better built as a group with a Collaborative Inbox.

Can I keep my domain where I bought it and still use Google Workspace?

Yes. The registrar and the DNS host are separate roles. You can leave the domain registered where it is and simply publish the MX, SPF, DKIM and DMARC records wherever the nameservers point. The one thing to check first is which panel actually answers for the domain, because records added in the wrong place are saved but never served.

How long after setting up the domain can I start sending?

Mail routing usually works within a few hours of the MX change, but the authentication is not instant. Google's documentation notes you may need to wait 24 to 72 hours after turning on Gmail before the DKIM key is available, and it recommends waiting about 48 hours after SPF and DKIM are live before publishing DMARC. Plan the first real send after that, not before.

Business email with your own domain: the setup, in order

Say a twelve person accounting firm has been sending from info@sudominio.com for six years. The mailbox came bundled with the hosting plan, nobody remembers who configured it, and this quarter two clients swore the invoice email never arrived. It did arrive. It went to spam, twice, and by the time anyone checked, the folder had been emptied.

That is the shape of most of the business email work we pick up. The domain is fine. The company is fine. The mail was set up once, quickly, by whoever was closest to the hosting panel, and then it was never looked at again. This is the order we build it in when we start from scratch, and the order we rebuild it in when we inherit something that half works.

Why the mailbox that came with your hosting costs more than it looks

Shared hosting bundles email because bundling is cheap, not because the host is good at delivering mail. Three things follow from that, and all three show up in client work.

You send from an address you do not control. The outbound IP belongs to the server, and it is shared with every other site on it. Your sending reputation is partly the average of what strangers do with their contact forms.
Nobody owns the accounts. When someone leaves, there is often no way to suspend the mailbox, transfer it, or read what is in it, short of asking for the password.
Authentication is usually half done. The panel may publish an SPF record for you. Very few sign outbound mail with DKIM unless you go and turn it on, and almost none publish DMARC.

None of that is fatal at five messages a day. It becomes expensive the first time an invoice, a quote or a password reset does not land.

The real options, and what separates them

For a small business there are three shapes worth considering, and the differences that matter are not the feature grids.

Keep mail on the hosting panel. Cheapest on the invoice. You accept a shared reputation, thin recovery options and manual authentication.
A dedicated mailbox platform. Google Workspace, Microsoft 365 or Zoho Mail. You get an admin console, per user accounts you can suspend and transfer, and DKIM signing you switch on once.
A platform plus a separate sender for application mail. Your store, your CRM and your invoicing software send from your domain too. They need their own authentication whichever platform you pick.

Judge them on four questions. Who owns the sending reputation. Can an administrator lock an account in under a minute. Is the mail recoverable if the laptop is stolen. Can a third party sender be authorised without breaking everything else. Feature lists rarely answer any of those.

On cost, compare list prices against what an hour of nobody being able to send is worth to you. Google Workspace Business Starter is published at USD 8.40 per user per month on the Flexible Plan, list price checked on 28 September 2026 on the Google Workspace pricing page, with 30 GB of pooled storage per user; the Business editions are sold for up to 300 users. We do not quote our own figures here, and neither should anyone selling you a platform without seeing your domain first. What an engagement covers is on how we work.

Your domain: where it is registered and where its DNS actually lives

This is the step that costs the most wasted hours, and it is not technical. Where you bought the domain and where its DNS records are answered from are two different places, and they are often not the same company.

Before touching anything, we look up the domain's nameservers and confirm which control panel answers for it. Editing a TXT record at the registrar while the nameservers point at a third party DNS provider produces a record that is real, saved, and invisible to the internet. People lose entire afternoons to this.

Two habits worth keeping. Lower the TTL on the mail records a day before you plan to change them, so a mistake expires in minutes instead of hours. And write down the current records before you edit them, because the only reliable rollback is the one you can paste back.

Users, aliases and groups: what needs a licence and what does not

A common way to overpay is to buy a licence for every address the company wants to exist. You need a licence for every person who needs a mailbox. Addresses are cheaper than that.

Users. One per human who signs in and sends. This is what you pay for.
Aliases. Google Workspace lets you add alternate addresses to an existing user at no extra cost, up to 30 per user. If billing and sales are both handled by the same person, they are aliases, not accounts.
Groups. A shared address such as info@ that several people answer is a group, not a mailbox. Turned on as a Collaborative Inbox, members can take a conversation, assign it to someone else and mark it complete, which is what a small team usually wanted from a shared account in the first place.

Set this up before you migrate anything. Deciding after the fact which of the eleven addresses were really people is slower than deciding first.

Authenticate on day one, not after the first complaint

Gmail's sender guidelines, in force since February 2024, require every sender to authenticate with SPF or DKIM, to have valid forward and reverse DNS for the sending domain or IP, to use a TLS connection, and to keep the spam rate reported in Postmaster Tools below 0.30 percent. Senders above 5,000 messages a day to Gmail must also publish DMARC and support one click unsubscribe on marketing mail. A new domain that skips this is not neutral, it is unauthenticated.

Four DNS records carry the whole thing. For a new Google Workspace domain, mail routing is a single MX record; older domains may still be on the five record set Google used before, and there is no urgency to change one that works.

; Mail routing, new Google Workspace setups
sudominio.com.            3600  IN  MX   1 smtp.google.com.

; SPF, one record per domain, no more than ten DNS lookups
sudominio.com.            3600  IN  TXT  "v=spf1 include:_spf.google.com ~all"

; DMARC, monitoring first
_dmarc.sudominio.com.     3600  IN  TXT  "v=DMARC1; p=none; rua=mailto:dmarc@sudominio.com"

DKIM is the one that is not copied from a guide, because the key is yours. In the Admin console it is under Apps, Google Workspace, Gmail, Authenticate email: generate a new record, choose 2048 bit if your DNS provider supports it, and keep the default selector prefix google unless the domain already uses it. Two details catch people out. Google's documentation says you may need to wait 24 to 72 hours after turning on Gmail before the key is available in the console, so this is not a same hour task on a brand new tenant. And if your DNS provider caps a TXT string at 255 characters, a 2048 bit key has to be split into several quoted strings inside one record value, not into several records.

DMARC goes last, and it goes out at p=none. Google recommends starting there so you can read who is sending as your domain before anything gets rejected, and waiting about 48 hours after SPF and DKIM are live before publishing it. Nothing about DMARC is configured in the Admin console; it is a DNS record and only a DNS record. Tightening to quarantine and then reject comes later, once the reports show you the full list of senders.

The SPF record has a hard limit worth knowing before you add your third sender: ten DNS lookups, counted across every include. Workspace plus a CRM plus an invoicing platform can reach it faster than you expect, and the failure is silent. We walk through the counting and the fixes in the SPF too many DNS lookups guide.

Signatures, devices and the day someone leaves

The parts nobody plans for are the parts that get called in as emergencies later.

Two step verification, enforced. Optional two step verification is off for exactly the people you most need it on. Enforce it with a short enrolment window and a documented recovery path for the owner's own account.
Recovery for the administrator. A super administrator locked out of the console with no recovery phone and no second admin is a multi day outage. Create a second administrator on day one.
Offboarding written down. Suspend the account, transfer the files, set a forward to whoever inherits the relationship, then release the licence. Deleting the account first loses the mail.
Signatures set centrally. Eleven people writing their own signature produces eleven versions of the company address. Set the template once at the organisation level.

If you already have mail somewhere else

Almost nobody starts from an empty domain. The sequence that keeps everyone working is the same whether the mail sits on cPanel, a personal Gmail account or an old Microsoft tenant: build the users and groups on the new platform first, copy the mail across while the old system is still receiving, and only then change the MX record. The cutover is the last step, not the first.

Two things to schedule around it. Mail can arrive at the old host for hours after the change while DNS caches expire, so leave the old mailboxes reachable rather than deleting them the same day. And every form, store and invoicing tool that sends using your domain needs re authorising against the new platform, because the MX change moves incoming mail and does nothing at all for outgoing. We wrote up the full sequence for the most common starting point in moving email off cPanel to Google Workspace.

How Guanacos Tech helps

We set up business email on a client's own domain end to end: the platform choice with the reasons written down, users, aliases and groups sized so you are not paying for addresses, the four DNS records published and verified, and a first read of the DMARC reports two weeks later to catch the sender nobody mentioned. If you would rather hand it over than learn a DNS panel, that is what Google Workspace consultants are for. A 30 minute call is enough for us to look at your domain and tell you what is actually missing.

Business email on your own domain: how we set it up so it works from day one