Google Workspace after AI is bundled: when is Business Plus still the wrong plan for a 220-person Australian company

01What bundled AI changed, and what it did not

Bundled AI removed one of the strongest reasons to step up to a higher Workspace bill. Google states that, from January 2025, AI capabilities that were previously sold through Gemini add-ons started rolling into Workspace Business and Enterprise plans, including Gemini in Gmail, Docs, Meet, Drive and other services Google Workspace Updates, Gemini AI features now included in Google Workspace subscriptions.

That means a 220-user buyer should stop treating AI as the differentiator between Standard and Plus. Google’s current public pricing page already shows AI messaging inside the Business editions, with Standard including Gemini in Gmail, Docs, Meet and more, and Plus including the same class of built-in AI assistance while adding eDiscovery, 5 TB pooled storage per user, 500-person meetings, Vault, Secure LDAP and advanced endpoint management Google Workspace pricing.

So the economics changed, but the architecture question did not. Business Plus is still only worth the uplift if the extra compliance, storage, meeting or endpoint controls are genuinely required across most of the estate. If they are not, bundled AI has actually made overbuying easier to spot, because the old AI add-on justification is gone.

• AI is now bundled into Workspace Business and Enterprise plans, not a separate Gemini purchase for most buyers.
• Business plans remain limited to 1 to 300 users Google Workspace Help.
• Business Plus still charges for non-AI extras: Vault, eDiscovery, bigger storage pools, larger meetings, Secure LDAP and advanced endpoint management Google Workspace pricing.

02For 220 users, what are you really paying extra for?

At list price on Google’s public page, Business Standard is USD 14 and Business Plus is USD 22 per user per month on annual terms Google Workspace pricing. For 220 users, that makes Standard about USD 3,080 a month and Plus about USD 4,840 a month, a difference of USD 1,760 monthly Google Workspace pricing.

The buyer mistake is to multiply that difference by headcount and assume the whole uplift buys security. It does not. For many mid-market firms, most of the uplift is really buying three operational conveniences: much more storage, built-in retention and legal hold tooling through Vault, and fewer compromises around large internal or client meetings Google Workspace pricing, Google Vault.

If your company does not have frequent litigation hold requirements, long retention obligations, or a board-level reason to standardise on 500-attendee meetings, then you are probably paying for unused headroom. Equally, if you do have those requirements, self-hosting or redesigning mail is not a cheap shortcut, because you would need to rebuild the control surface that Plus gives you in a managed service.

There is also a subtle data location point. Google Workspace data regions let customers choose the United States, Europe, or no preference for covered data. Google does not offer an Australia-specific Workspace data region on these pages Google Workspace data regions, Choose a geographic location for your data. If your procurement team assumes Business Plus solves Australian data residency by itself, that assumption needs correcting before renewal.

03When Business Plus is still the wrong plan

For a 220-person Australian company, Business Plus is often still wrong in five common situations.

First, only a small subset of users needs compliance features. Google notes that if your edition does not include Vault, you may be able to buy Vault add-on licences Buy Vault licenses for your organization. That matters because it changes the estate design question. If 20 people in finance, legal and leadership need stronger retention and search, and the other 200 do not, an all-Plus estate can be wasteful.

Second, your real problem is mail architecture, not collaboration licensing. Companies often keep Plus because shared mailboxes, workflow addresses, archived ex-staff accounts or system-generated mail have grown into a messy estate. If that is your pattern, the right fix may be to redesign mail flows, journal rules, shared identities and relay paths, not to keep buying the most feature-rich per-user SKU. See Google Workspace migration checklist and Emails started going to spam after a domain or provider change if your concern is deliverability and migration hygiene rather than end-user features.

Third, you are paying Plus mainly for storage. Google’s public plan matrix shows Standard with 2 TB pooled storage per user and Plus with 5 TB Google Workspace pricing. If you have poor Drive governance, duplicated files, unrestricted shared drives and no lifecycle discipline, buying more storage can hide a content management problem for another year, not solve it.

Fourth, you are moving toward a specialised or self-hosted mail environment anyway. Once that becomes a live option, you should compare Plus against the target-state operating model, not against Standard in isolation. That includes gateway design, authentication, spam handling, monitoring, backup, incident response and admin labour. If you are likely to make that move within the next 12 months, a short-term annual commitment to Plus can lock in cost while you are actively planning to replace the thing you are buying.

Fifth, the team is using Plus as a substitute for security design. The ASD’s guidance is explicit that organisations need an email usage policy and should implement SPF, DKIM and DMARC properly Guidelines for email, SPF, DMARC and DKIM. A higher Workspace tier helps with tooling, but it does not remove the need to define approved services, block non-approved webmail where required, and set authentication policies correctly Guidelines for email.

• Wrong fit if only a minority needs Vault or strong retention controls.
• Wrong fit if storage bloat is the hidden issue.
• Wrong fit if a mail redesign is already coming.
• Wrong fit if procurement expects Plus to solve Australian-only data residency.
• Wrong fit if the uplift is masking weak email security operations.

04When redesigning mail beats paying the uplift

Mail redesign is the middle path between doing nothing and building a full self-hosted estate. For a 220-seat company, this usually means keeping Google Workspace for collaboration and primary user mail where it fits, while moving some identities, relay functions, archived accounts, or transactional and workflow mail to a separate design.

This path starts paying off when the expensive part of your estate is not human collaboration, but non-human mail behaviour. Common examples are application senders, shared service inboxes, high-volume outbound notifications, old employee mail retained for reference, and departments that need queue-based handling rather than a personal mailbox model.

A sensible redesign usually asks five questions. Which mailboxes are attached to a human user and need full collaboration features? Which are functional addresses that could be reworked? Which addresses exist only because an old process was never retired? Which messages are business records that need retention? Which outbound flows require strong deliverability controls and domain authentication?

This is where a delivery team with mail infrastructure services, cloud infrastructure support and governance and compliance capability can help model the estate before you touch licences. The work is less about buying another platform and more about classifying identities, dependencies and compliance needs.

The trade-off is effort. Redesigning mail means discovery workshops, directory cleanup, mail flow diagrams, alias rationalisation, relay decisions, migration sequencing and user communications. It is a real project. But when the alternative is carrying a large Plus uplift across 220 users for reasons that apply to only part of the estate, it is often the more rational project.

• Keep collaboration where Google is already strong.
• Move only the mail patterns that distort per-user licensing.
• Treat archived, shared and system mail separately from active staff mail.
• Model compliance requirements before choosing the target architecture.

05When self-hosted or custom mail infrastructure is rational, and when it is not

Self-hosted or custom-managed mail is not automatically cheaper just because Google’s Plus tier feels expensive. It becomes rational only when you have stable internal capability, clear compliance needs, and a narrow target scope. A 220-person company should usually avoid a full self-hosted rebuild for all users unless there is a strong operational or sovereignty reason.

The security bar is not theoretical. ASD guidance for email covers policy, content filtering, protective marking behaviour, and authentication controls. ASD’s Blueprint material also stresses that SPF, DKIM and DMARC must be configured correctly, and warns that downstream gateway changes can break DKIM alignment Guidelines for email, SPF, DMARC and DKIM. In practice, that means every custom mail design inherits work in DNS, gateway policy, routing, monitoring, certificate management and change control.

For most mid-market buyers, the rational custom path is partial: separate outbound infrastructure for applications, dedicated retention paths for records, or a ring-fenced system for special-use mail. The irrational path is rebuilding a whole-user mail platform because Plus looks pricey this quarter.

Before you approve a self-hosted or hybrid option, ask the vendor to show exactly how they will handle these controls: SPF, DKIM, DMARC, backup and restore, anti-spam posture, mailbox migration rollback, admin access control, log retention, monitoring, patching and incident response. If they answer in platform names instead of operating procedures, keep digging.

• Rational: scoped custom or hybrid mail for special cases.
• Usually irrational: full self-hosting for every user just to avoid Plus pricing.
• Non-negotiable: documented operating model for authentication, patching, monitoring and recovery.

06What to ask before you renew anything

If renewal is within one quarter, do not start with price. Start with seat classification. Split your 220 users into at least five groups: regulated or legal hold users, standard knowledge workers, heavy-storage users, meeting-intensive users, and non-human or shared mail identities. You cannot make a sensible Standard-versus-Plus decision until that list exists.

Then ask your Google partner or internal admin team for hard evidence on four things: current Vault use, storage consumption patterns, meeting usage above Standard limits, and endpoint management requirements. If the business case for Plus is real, it should show up in those operating facts.

If self-hosting or a custom mail design is on the table, ask for a transition plan, not just a target diagram. You want the order of migration, coexistence model, rollback approach, security controls, and who owns support after go-live. That work often overlaps with technology consulting and cybersecurity and risk, because mail projects fail more often on control gaps than on server setup.

Finally, check the contract term against your likely architecture decision point. Google’s own billing help says Annual Plan customers must pay the full commitment even if they cancel early, while flexible plans allow cancellation without that penalty Compare Flexible and Annual/Fixed-Term payment plans. If you may redesign mail within the year, that single contract choice can matter almost as much as the edition choice.

• Classify users before comparing editions.
• Demand evidence of actual Vault, storage and meeting usage.
• If custom mail is in scope, ask for migration and rollback detail.
• Match licence term to architecture timing, not just headline discount.