
Business Email on Your Own Domain
Google Workspace gives you Gmail on your own domain — the interface your team already knows, on an account the company owns rather than the individual.
The address is the smallest part of what you are buying, and it is the part everyone focuses on. What actually changes how a business runs is who owns the mailbox when someone resigns, whether accounts@ is a group or a password four people know, and whether anyone can add a new starter without asking one specific person.
Four decisions to make first
- badgeYour address formatHard to change once it is on business cards
- groupsHow shared addresses workA group, delegation — or a shared password
- blockWhether to run a catch-allUsually more spam magnet than safety net
- person_offWhat happens to a leaverFive minutes in advance, an argument on the day
Six things a business address gives you that a free one does not
Looking more professional is the reason most businesses give for moving. It is the least important item on this list, and the only one they notice on day one.
The company owns the mailbox
This is the one that actually matters, and it is invisible until it bites. An address on your domain belongs to the business, so when someone leaves you keep their correspondence, reassign their address and hand their files to a successor. A personal account walks out of the door with the person.
Addresses that are not people
accounts@, orders@, support@ — shared addresses that route to whoever should see them, and keep working when that changes. Most small businesses run these as a mailbox with a shared password, which is the arrangement this page is largely about replacing.
An admin console behind it
Someone can add a starter, remove a leaver, reset a password, transfer files and see what is configured. Without that you have a collection of individual accounts rather than a company system.
Security you can actually enforce
Two-step verification required rather than suggested, recovery that does not depend on one person's phone, and control over which third-party apps can reach your mail.
Retention that is a decision
How long mail is kept, and whether it survives someone deleting it, becomes something you set rather than something that happens. In regulated work that is not optional.
A domain that can be protected
SPF, DKIM and DMARC exist to stop other people sending mail that looks like yours. You cannot publish them for an address you do not control.
How accounts@ should actually work
Nearly every business has an address several people need to reach, and nearly every business starts by sharing a password. Here are the three arrangements side by side, including the one you are probably using.
| Arrangement | Cost | How it works | The catch | When to use it |
|---|---|---|---|---|
| A shared password | Free | One mailbox, several people, one login everybody knows. | No way to tell who sent or read anything. Removing one person means changing a password everyone uses. Two-step verification becomes impractical, so the account is usually the weakest in the business. A leaver keeps access until somebody remembers. | Never, once there are more than about two people. This is the arrangement we most often replace. |
| A Google Group | No extra licence | The address is a group; mail is delivered to the members' own inboxes, or to a shared collaborative inbox they work from. | It behaves differently from a mailbox, and teams used to Outlook shared mailboxes notice. Threading and assignment work, but not identically to what they left. | Most shared addresses, most of the time. Costs nothing and gives you per-person access and removal. |
| A licensed account with delegation | One licence | A real mailbox that named people are granted delegated access to. They read and send from it while signed in as themselves. | It consumes a seat, so ten of these is ten licences. | Where a shared address is genuinely a working mailbox with its own filing, or where the team needs it to behave exactly like the Outlook shared mailbox they are used to. |
The practical rule: start every shared address as a Google Group, because it costs nothing and gives you per-person access. Move it to a licensed account with delegation only where the team genuinely needs it to behave like a mailbox of its own.
Five decisions that are awkward to undo
None of these are technical and all of them are easier to get right at the start than to change once addresses are printed, indexed and sitting in a thousand supplier records.
Decide the format before the first account
firstname@, firstname.lastname@ or initials — pick one and apply it. It sounds cosmetic until you have two people called Anil and no convention, or until a customer cannot guess anyone's address. Changing it later means every business card, signature and supplier record is wrong.
Separate people from functions
People get their own address. Functions get a role address that survives them. If orders go to ravi@ rather than orders@, the business stops for a week when Ravi does — and that is a business continuity problem wearing a technical disguise.
Use aliases rather than extra accounts
A person can receive at several addresses without paying for several licences. A second spelling of the company name, a legacy address from a rebrand, a departmental address that one person currently handles — all aliases, all free.
Decide the catch-all question deliberately
A catch-all delivers anything sent to your domain, including every typo and every address a spammer invents. It is usually more useful switched off, with specific aliases for the misspellings that genuinely occur.
Write down what happens to a leaver
Suspend or delete, transfer the files to whom, forward the address for how long, and who tells the customers. Decided once, in advance, it is a five-minute process. Decided on the day, it is an argument.

A free Gmail account and a Google Workspace one
They look almost identical to use, which is why the difference is so easy to dismiss. The interface is the same. What sits behind it is not.
| Free Gmail account | Google Workspace | |
|---|---|---|
| The address | yourname@gmail.com | you@yourcompany.com, on a domain you own |
| Who owns the account | The individual. It leaves with them. | The organisation. Reassigned or transferred when someone leaves. |
| Admin control | None. Every account is independent. | Central console — add, remove, reset, transfer, set policy. |
| Shared addresses | A shared password, in practice. | Groups or delegated access, per person and revocable. |
| Enforcing security | Each person decides for themselves. | Two-step verification enforced organisation-wide. |
| Retention and recovery | If they delete it, it is gone. | Retention policy, and recovery of a deleted account's data within a window. |
| Storage | Fixed free allowance, shared with photos. | Per-user allowance that scales with the edition, pooled across the organisation. |
| Support | Help pages and forums. | Google support, plus your partner. |
Signs you have outgrown what you have
If none of these describe you, there is a reasonable argument for leaving things alone, and we would rather say that than sell you something. If several do, the cost of waiting is no longer zero.
- warning
Staff are using personal accounts for company correspondence, and nobody can see it
- warning
A shared address has a password that four people know and nobody has changed
- warning
Someone left and took supplier relationships or customer history with them
- warning
You cannot enforce two-step verification because half the accounts are not yours
- warning
Mail to customers is landing in spam and no one can explain why
- warning
There is no way to add a new starter without asking one specific person
- warning
A client or partner has started asking how you control access to data
An address nobody receives is not an address
Owning a domain lets you publish three DNS records that tell the rest of the internet which mail genuinely comes from you. Without them your mail is more likely to be filtered, and anyone can send messages that appear to be from your company.
SPF
Declares which servers may send as your domain.
DKIM
Signs your outgoing mail. Not enabled by default — it has to be generated and published.
DMARC
Tells receivers what to do when the other two fail, and reports who is sending as you.
All three are configured as part of the setup rather than left as a follow-up. The longer version, including how to move DMARC to enforcement without stopping your own invoices, is on our migration page.
Business email — common questions
helpWhat is business email, and why not just use Gmail?
expand_more
Business email is email on a domain you own — you@yourcompany.com rather than yourcompany@gmail.com. With Google Workspace you get the Gmail interface people already know, but the account belongs to the organisation rather than to the individual. That single difference is what gives you an admin console, shared addresses that are not a shared password, enforceable security, retention, and the ability to keep someone's correspondence when they leave. A free Gmail account gives you the mail and none of the rest.
helpHow should shared addresses like info@ or sales@ work?
expand_more
Almost never as a mailbox with a password several people know. There are two proper options. A Google Group costs nothing extra and delivers to members' own inboxes or to a shared collaborative inbox — right for most shared addresses. A licensed account with delegated access costs a seat but behaves like a real mailbox with its own filing, which suits a genuinely busy shared address or a team migrating from an Outlook shared mailbox. Either way each person signs in as themselves, so you can tell who did what and remove one person without disrupting everyone.
helpDo shared addresses need their own licence?
expand_more
Usually not. Most are configured as groups or aliases, which do not consume a paid licence, and licences are per person rather than per address. This is one of the more common reasons a first quote comes back larger than it needs to be — a business counts its addresses instead of its people. A licensed account is only needed where the shared address really is a working mailbox in its own right.
helpCan one person have more than one email address?
expand_more
Yes, and it costs nothing extra. Aliases let a single licensed account receive mail at several addresses — a second spelling of the company name, an address kept from a rebrand, or a departmental address that one person currently handles alone. Only actual people need licences.
helpWhat address format should we use?
expand_more
Whichever you pick, pick it before you create the first account and then stick to it. firstname@ is friendly and runs out quickly. firstname.lastname@ scales and is what most people expect. Initials are compact and unguessable, which is occasionally the point and usually a nuisance for customers. The format matters less than the consistency — changing convention later means every signature, business card and supplier record in circulation is wrong.
helpShould we have a catch-all address?
expand_more
Generally no. A catch-all accepts mail sent to any address at your domain, which sounds like a safety net and works out as a spam magnet, because it guarantees delivery for every address a sender invents. The better arrangement is to switch it off and create specific aliases for the misspellings that genuinely occur — which you will discover in the first month of proper logging.
helpWill our email still work on phones and in Outlook?
expand_more
Yes. Gmail works in any browser and has apps for Android and iOS, and mail, contacts and calendar sync to the built-in apps on both. On Windows, Outlook can be kept working against a Google Workspace account if part of your team genuinely needs it — though that is better treated as a transition aid than a permanent arrangement, for reasons we set out on the Microsoft 365 migration page.
helpHow long does it take to set up business email?
expand_more
The technical work is a matter of hours for a small team — verify the domain, configure DNS and MX records, create accounts and groups, publish the authentication records. What sets the actual timeline is deciding the address format, which shared addresses exist and who should reach them, and what happens to a leaver. Businesses that answer those in one sitting are live quickly; the rest are waiting on themselves, not on us.
helpWhat about mail landing in spam?
expand_more
That is almost always domain authentication rather than content. SPF, DKIM and DMARC tell receiving mail systems that your mail genuinely comes from you, and DKIM in particular is not switched on by default — the key has to be generated and published deliberately. We configure all three as part of the setup rather than leaving them as a follow-up nobody owns.
helpWhat does business email cost in India?
expand_more
Google Workspace is licensed per user per month, with India list prices starting at the Base tier and rising with storage and features rather than with the number of addresses. We invoice in INR with GST against your GSTIN. Because shared addresses and aliases usually do not need their own licence, the real cost is generally lower than a first count of addresses suggests. Full current figures are on our Google Workspace pricing page.
Related pages
Google Workspace Email Security
SPF, DKIM and DMARC — so the mail you send actually arrives.
Google Workspace Implementation
Structure, policy, security baseline and rollout — built once and documented.
Gmail Migration for Business
Moving mailboxes across, and the six things that never migrate.
Google Workspace Pricing in India
List prices in INR, what GST adds, and what drives the final figure.
Set up business email properly
Tell us how many people need an address and which shared addresses you use today. We will come back with a licence count based on people rather than addresses, an address structure, and a fixed-scope quote in INR.
- check_circle
Licence count based on people, not on how many addresses you have
- check_circle
Shared addresses configured as groups or delegation, never a shared password
- check_circle
SPF, DKIM and DMARC published as part of the setup
- check_circle
A written process for what happens when someone leaves
We set this up for businesses across Kerala and the rest of India. Or call +91 99467 89916 or email admin@techgeum.com.