Google Workspace pricing vs forwarding + SMTP for small teams

Quick answer for a Google Workspace pricing alternative

Buy Workspace when every teammate needs a hosted mailbox, admin controls, Calendar, and Drive as the company system of record. Google’s current packaging lives on the Google Workspace — product overview page and changes. Do not treat a blog number as Google’s price list. The economic shape is per-user and ongoing.

Buy forwarding plus SMTP when the team already lives in consumer Gmail and the domain is an identity, not a new office suite. MailerZ is that layer: inbound MX, envelope SRS only, Header From never rewritten, delivery history, and paid send-as. It is not Workspace. It is not IMAP. It is not an open relay. Role addresses such as hello@ and billing@ become aliases, not extra Google seats.

The safest Google Workspace pricing alternative setup is a roster, not a feeling. List humans who need a login. List public local-parts that only need to land in an existing inbox. If those lists are the same length and everyone needs Calendar, you are buying the suite. If you have three people and twelve printed addresses, you are buying routes. A public thread of operators who only wanted forwarding is a snapshot of the pain, not a product review: cheap mail hosting, just forwarding.

MailerZ Free is one domain, ten aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. That proves inbound. It does not finish “recipient sees our domain on the reply.” Solo is $40 per year for five domains, 25 aliases, 90-day store, 2,500 outgoing per month, and 20 send-as per hour. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on MailerZ pricing. Compare the suite model on MailerZ versus Google Workspace.

Do not run Workspace MX beside MailerZ MX “during the trial.” Leftover MX is a hard stop. Split records lose mail in a pattern that looks random and then gets blamed on whichever invoice is smaller.

The user problem and the decision criteria

Small teams meet Workspace pricing when a founder wants you@brand.com and a quote arrives per user, per month, for Calendar they will not open. They already have Gmail. They have four role addresses and two humans. Buying four hosted mailboxes to park aliases is how forwarding companies get invented.

The opposite mistake is also common. A five-person shop needs shared drives, device management, and legal hold. They buy a $40-a-year forwarder and then ask why there is no admin console for mailboxes. There isn’t one. MailerZ seats operate the delivery account. They do not create Gmail users.

Forwarding plus SMTP is a good fit when Gmail is already the archive, role addresses outnumber people, and you can tolerate published send limits. It is a poor fit when counsel wants a tenant archive, when every contractor needs a managed mailbox, or when you expect MailerZ to promise Primary-tab placement.

Technical mail flow

Pricing arguments hide a transport fact. IETF RFC 5321 — Simple Mail Transfer Protocol still governs delivery. The sender looks up MX and talks SMTP. Google Workspace pricing versus forwarding plus SMTP only changes who answers MX and who stores the bytes after 250.

Forwarding plus SMTP

MailerZ MX receives for a verified domain. The edge matches an alias or catch-all policy, stores required content, returns 250, and forwards into Gmail. Header From stays the original sender. Envelope MAIL FROM may use SRS. Delivery history records the destination response. Gmail can still file the message in spam. That is Gmail’s decision, and it is why “cheaper than Workspace” is not an inbox-placement claim.

Outbound is separate. Gmail Send mail as needs an SMTP identity allowed to use the domain. MailerZ provides that on paid plans. You copy host, port, username, and generated password. Limits apply. Unhosted or unauthorized recipients get 550. The send-and-reply surface is documented on send and reply as your domain.

Workspace as the store

Workspace MX points at Google. The message is stored in a mailbox you administer in the tenant. Clients use the Workspace account, not a forward into consumer Gmail—unless you then forward again, which is how teams pay twice and debug twice. Outbound leaves through Google’s submission path, signed with Google’s DKIM for that domain. You bought a store. Use it as a store.

SPF, DKIM, and DMARC authorize sending on both paths. IETF RFC 7208 — Sender Policy Framework (SPF), IETF RFC 6376 — DomainKeys Identified Mail (DKIM), and IETF RFC 7489 — Domain-based Message Authentication, Reporting, and Conformance (DMARC) are the texts. They do not make mail inbox. They do not replace MX. Publish one set that matches the sender you actually use. Two signers with one From domain make DMARC reports ugly.

MailerZ recovery storage is 14 days on Free and 90 days on paid plans. That is a failed-hop window. It is not Workspace vault, not eDiscovery, and not a reason to skip Gmail’s own archive. If legal hold is the requirement, you are not shopping for a Workspace pricing alternative. You are shopping for a tenant.

Seats on MailerZ are operators of the delivery account. Starter includes five seats so more than one person can rotate SMTP passwords and read history. Those five people still read mail in Gmail. Do not translate “5 seats” into “5 Workspace licenses saved” unless you actually avoided five hosted mailboxes. Translate it into “five people can run the router.”

Step-by-step setup and decision path

This is the Google Workspace pricing alternative setup path. Do the roster first. DNS second. Purchasing third.

1. Build two lists

   Column A: humans who need a mailbox login you control. Column B: public addresses that only need to land somewhere. If A is the whole company and includes Calendar, you are done—buy the suite. If B is longer and A already has Gmail, continue.

2. Price the suite from Google, not from memory

   Open the Workspace page the week you decide. Multiply by the people in column A, not the addresses in column B. If that number is acceptable because you need the suite, stop shopping for a forwarder. If that number exists only to host billing@, you found the waste.

3. Add one domain on MailerZ and verify TXT

   Use the root domain. Publish the unique verification TXT. Receiving stays off until the check passes. Do this before you delete any Google records if a trial MX is already live.

4. Create aliases for column B

   Map role addresses to the Gmail inboxes that should receive them. Complete destination verification. Do not buy a mailbox for an address that only needs a route. Free allows ten aliases. Count column B against Solo (15), Starter (50), Business (200), and Agency (500).

5. Publish one MX set and delete leftovers

   Copy MailerZ hosts and priorities. Remove leftover Google, Microsoft, registrar, or host MX. If you chose Workspace instead, publish only Google’s MX. Mixed sets are not a discount. They are a mail-loss bug.

6. Prove inbound from a different mailbox

   Send a uniquely titled message from an unrelated provider. Confirm Header From. Open delivery history. Self-send from Gmail to the same Gmail account can hide a bad cutover and a leftover MX at the same time.

7. Add paid send-as only if column B must also send

   Free has no send-as. Solo and above add authenticated SMTP. Configure Gmail Send mail as. Test to a second external inbox. If you bought Workspace, send from the Workspace identity instead. Do not run both outbound signers for the same From.

8. Revisit the roster in ninety days

   If you added contractors who now need Drive, buy the suite for those people. If you only added more printed addresses, raise the MailerZ alias ceiling. Do not convert a working forwarder into Workspace because a sales deck said “professional email.”

Failure modes and proof

Most “the cheap alternative broke email” reports are leftover Google MX, an alias that was never created, or a team that expected IMAP on MailerZ. Work the evidence.

Proof is a sanitized destination header block plus the receiving event with timestamp and remote response. Do not send SMTP passwords to support. Inbox placement is not proof you saved money correctly. DNS diagnostics live on troubleshooting.

MailerZ workflow and product boundary

MailerZ is a custom-domain email delivery layer operated by Secuno LLC. Point MX at MailerZ. Mail for a hosted, verified domain can land in Gmail or Outlook. Paid plans add authenticated SMTP. The live site is mailerz.net. The app is mail.mailerz.net.

Positioning for this article: MailerZ exists to avoid buying full mailbox seats for addresses that only need routing. That is the whole conversion angle. If the address needs a mailbox, buy a mailbox.

What MailerZ does in this workflow

• Accept inbound mail for verified domains and configured recipients.
• Preserve Header From on the forward into Gmail.
• Hold or forward unknown recipients according to plan and settings.
• Store messages for 14 days on Free or 90 days on paid plans.
• Send through authenticated SMTP from approved identities on paid plans.
• Record delivery history for inbound and outbound hops.
• Give operators seats that are not Gmail mailboxes.

What MailerZ does not do

• Replace Workspace with IMAP, Calendar, Drive, or device management.
• Rewrite header From, Subject, Date, Message-ID, body, or MIME.
• Offer send-as on Free.
• Promise inbox placement, uptime SLAs, or review counts.
• Claim SOC 2, ISO 27001, or HIPAA.
• Act as an open relay or a campaign sender.
• Quote Google’s price for you. That number lives on Google’s site.

Plan shape for a small team that stays on Gmail: Solo for one operator and up to 25 aliases; Starter when five people must share the router and you need 5 domains or 50 aliases; Business and Agency when domain count jumps. Annual Starter, Business, and Agency billing includes two months free relative to paying monthly for a year. Solo has no monthly option.

Cost, alternatives, and trade-offs

The honest comparison is economic shape, not a screenshot of last year’s Workspace SKU. Google changes packs. MailerZ publishes the cards on /pricing. Multiply Workspace by humans who need the suite. Compare MailerZ to addresses and send limits. If you mix the units, you will pick the wrong product and then write a bitter review of the unit you invented.

Example arithmetic that stays honest because it uses MailerZ numbers only: three role aliases and inbound proof fit Free. Adding send-as for one founder is Solo at $40 per year. A five-person Gmail team that needs fifty aliases and ten send-as per hour is Starter at $8 or $80. None of those figures is a Workspace quote. Put Google’s current per-user price next to column A yourself.

Cloudflare Email Routing is inbound routing, not a suite and not MailerZ stored hops. Read Cloudflare — Email Routing documentation if that is the stack you run. ImprovMX is the closest forwarding class; compare current plans on their site: ImprovMX — product documentation. Registrar free email is usually leftover MX waiting to happen.

If column A grows—new hires who must live in a tenant—buy Workspace for those hires. Keep MailerZ only if the domain still receives through MailerZ, which means you did not also publish Google MX. Most teams should pick one receiving answer when people join. Hybrid estates are how invoices and outages both go up.

Contractors complicate the spreadsheet. A designer who already lives in Gmail and only needs studio@yourdomain.com forwarded into that account is a route. A bookkeeper who must retain seven years in a tenant you administer is a seat. Do not give the designer a Workspace login to make the bookkeeper feel consistent. Do not put the bookkeeper on Free forwarding to save forty dollars a year. Write the job next to the name. The invoice follows the job.

Send limits are the other hidden unit. Solo allows 20 send-as messages per hour and 2,500 outgoing per month. Starter allows 40 per hour and 5,000 per month. Business allows 60 and 12,000. Agency allows 60 and 20,000. A support alias that replies all afternoon can exhaust Solo before it exhausts alias count. That is not a reason to buy Workspace. It is a reason to pick Starter or to move true ticket volume onto a help desk that already sends. MailerZ is not a queue.

FAQ

Key takeaways

• A Google Workspace pricing alternative is seats versus routes, not “cheap email.”
• Price Workspace from Google’s current page. Price MailerZ from /pricing. Do not mix units.
• Role addresses do not need hosted mailboxes if Gmail already stores the mail.
• Header From stays the original sender on inbound. Envelope SRS is the allowed rewrite.
• Leftover Google MX beside a forwarder is a hard stop.
• Test inbound from a different mailbox. Self-send lies.
• Free has no send-as and ten aliases. Solo is $40 per year when the From identity must travel.
• MailerZ seats operate the router. They are not Workspace licenses.
• MailerZ is not SOC 2, not IMAP, and not a bulk sender.

Conclusion and next action

If you came here for a Google Workspace pricing alternative, keep the units honest. Pay Google per human who needs the suite. Pay a delivery layer per domain and alias when Gmail is already the store. Publish one MX set. Prove inbound. Add paid SMTP only if the printed From must leave as the domain.

MailerZ fits when you want that split with delivery history and a recovery window. It does not fit when you need a hosted mailbox for every user, a certified compliance report, or campaign-scale sending. Start on Free if you only need to watch inbound. Move to Solo or Starter when alias count or send-as requires it.

Next action: write the two columns, add one domain, create the first role alias, and send a uniquely titled message from a mailbox that is not the destination. Buy Workspace only for the people who actually need the suite.

Review quarterly, or sooner if Workspace packaging, MailerZ plan limits, or DNS guidance changes. Author: MailerZ editorial, Secuno LLC.