The short answer
Google Workspace support covers setting up your domain and mailboxes, migrating from another mail provider, configuring SPF, DKIM and DMARC so your mail is delivered, and sorting file ownership in Drive. We manage it for Australian businesses from Brisbane and answer in 1 to 3 hours.
What we look after
Setup.
Domain verified, mailboxes and groups created, mobile devices connected, aliases where you need them.
Migrations.
From Microsoft 365, an old IMAP host or a pile of personal Gmail accounts, with mail and calendars brought across.
Mail authentication.
SPF, DKIM and DMARC published and checked, including every third party tool that sends as you.
Drive structure.
Shared drives set up so company files belong to the company.
Security settings.
Two step verification enforced, admin roles limited, forwarding and delegation audited.
Groups instead of licences.
Generic addresses handled without paying for a user who doesn't exist.
Backup.
Third party backup of mail and Drive, covered in cloud storage and backup.
Email deliverability, or why your client never got the quote
Mail doesn't bounce, so nothing warns you. It lands in a spam folder, and the first evidence is a client saying they never got the quote. Three DNS records decide most of it.
SPF is a public list of the servers allowed to send email for your domain. A receiving server checks the message came from something on that list. If your accounting software, your CRM and your newsletter tool all send as you, all three have to be in it.
DKIM is a signature. Your provider signs outgoing mail with a private key and publishes the public key in your DNS, so the receiver can verify the message is genuine and unaltered. SPF says the right server sent it. DKIM proves the message itself.
DMARC tells receiving servers what to do when a message fails, and adds the part that makes the other two mean anything: the domain that passes has to match the From line your recipient sees. Set it to none, quarantine or reject, and it reports back everything sending as your domain.
Why a marketing platform breaks this.
Put your address in a campaign tool's From field and the mail leaves that platform's servers, not Google's. Your SPF doesn't list them, nothing signs with your domain's key, and the receiver sees unauthenticated mail claiming to be you. It goes to promotions at best and spam more often, and the damage carries over to the quote you type by hand next morning. Every platform publishes the records it needs, added by whoever controls your DNS. Google and Yahoo now enforce this on bulk senders.
Check your own domain.
Read the TXT record on your domain starting with "v=spf1", look up _dmarc.yourdomain.com.au and see whether anything exists at all, then confirm DKIM signing is switched on in your admin console rather than merely available. Any free mail record checker does all three. Blank DMARC is the usual result.
Shared drives versus My Drive.
Files in a personal My Drive belong to that person, not the business. When someone leaves and the account is deleted, ownership has to be transferred deliberately or the files go with it, links break, and the client folder built over four years turns out to have lived in a departed manager's Drive. Shared drives are owned by the organisation. Membership changes, files stay.
How we take it on
We audit what's running
Accounts, licences, admin roles, mail records, forwarding rules and where the files actually live.
We fix deliverability first
SPF corrected, DKIM enabled, DMARC published on a reporting policy so we can see who's sending as you before tightening.
We sort structure and access
Shared drives created, permissions cleaned up, generic addresses moved to groups.
We support it
Starters, departures and problems, answered in 1 to 3 hours through managed support.
Who this suits, and who it doesn't
It works for businesses on Google Workspace with nobody owning the admin console, teams whose campaign email keeps landing in spam, and offices where important files sit in one person's Drive.
It's a poor fit if you need on site IT for a large staffed network, or your business runs on Microsoft applications, in which case Microsoft 365 is the honest answer.
Why hand this over
We hold the DNS as well.
Mail authentication is DNS work. When one team manages your domain and your mail, publishing a record takes minutes instead of a fortnight of emails to whoever built the site.
We respond in 1 to 3 hours.
Email failures stop the whole office, which is where a real number beats a promise about being responsive.
Australian support with your account manager on it.
One person who knows how your account is configured, rather than a help centre article and a form.
"Our email works fine, why touch DNS?"
Working and being delivered are different things. Mail that quietly lands in spam still looks like it sent. The check takes ten minutes.