How to Send Professional Email Without Paying Per-Seat for Google Workspace

By Forward Team Apr 25, 2026 8 min read Business

When you register a new domain, the first thing you need is a professional email address. But signing up for a full Google Workspace or Microsoft 365 account just to answer customer support emails is expensive overkill.

This setup is narrow on purpose: keep your personal inbox, send from a branded address, and avoid paying for inboxes you do not need.

The $72/Year Per User Problem

Google Workspace (formerly G Suite) is an incredible product. If you have a team of 50 employees who need shared drives, enterprise device management, and massive Google Drive storage quotas, it's worth every penny.

But if you are a solo founder launching a side project, an agency spinning up multiple domain names for different client projects, or a freelancer setting up a portfolio site, paying $6 to $12 per user, per month, per domain is brutal. A team of three people on three different startup ideas could easily be burning hundreds of dollars a year before they ever make a sale.

The goal is not to replace every mailbox. The goal is to keep one inbox and one branded sending identity without the seat tax.

The Lean Setup: Forwarding + SMTP

Most businesses just need to look professional in their inbox. When a customer emails support@yourstartup.com, they expect a reply from support@yourstartup.com.

You do not need a dedicated 30GB mailbox for that. You already have a perfectly good, free email client (like your personal Gmail, Apple Mail, or Outlook).

The modern, lean setup uses two parts:

  1. Inbound Routing (Forwarding): You point your domain's MX records to Forward. Forward catches emails sent to hello@yourdomain.com and instantly drops them into your Gmail inbox.
  2. Outbound Routing (SMTP): When you hit "Reply" in Gmail, you use Forward's SMTP credentials. Gmail securely hands the drafted email back to Forward, which then delivers it to the customer.

To the outside world, you are a professional organization running your own mail servers. To you, everything lives seamlessly inside the email app you already check fifty times a day.

How Forward SMTP Works

Unlike free shared SMTP relays that tank your deliverability, Forward provides dedicated sending infrastructure. Our Creator plan (just $5/month flat, not per user) allows you to manage up to 20 different domains and generate highly secure SMTP credentials for your team.

We built this for human sending. Our infrastructure is heavily optimized for day-to-day business communication. To protect the reputation of the IPs handling your mail, we enforce strict limits:

  • 10 recipients per minute
  • 100 recipients per hour
  • 500 recipients per day
  • Max 25 recipients per single email

These limits ensure that no single compromised account on the platform can blast 100,000 spam messages and ruin deliverability for everyone else. If you are sending newsletters, use a bulk sender like Resend or Mailgun. If you are talking to humans, use Forward.

Practical Setup

  1. Add your domain and verify ownership.
  2. Create the address you want to send as, like you@yourdomain.com.
  3. Generate an SMTP credential scoped to that address.
  4. Add the SMTP details to Gmail's "Send mail as" flow.
  5. Send a test to a non-Gmail inbox and confirm SPF, DKIM, and DMARC alignment.
Rule: forwarding handles inbound mail, SMTP handles outbound mail. Use both only when you need branded replies.

Security First: Why Scoped Credentials Matter

When you generate an SMTP credential in Forward, we don't just hand you a master password to your domain. That's dangerous.

Instead, we force you to scope every credential. If you generate a password for your marketing intern, you can lock that credential so it can only send mail as marketing@yourdomain.com. Even if that password is leaked on the dark web, attackers cannot use it to spoof an email from the ceo@yourdomain.com.

Furthermore, Forward requires strict TXT record domain verification before you can send a single byte. We physically verify that the person generating the credentials actually controls the DNS for the domain in question. This prevents spoofing and domain hijacking before it can even start.

When Not To Use This

  • Teams that need shared calendars, docs, and inbox collaboration inside one suite.
  • Compliance-heavy orgs that require mailbox-level retention or legal hold.
  • Newsletter or bulk-send use cases.

Quick Troubleshooting

  • If replies show the wrong From address, re-check Gmail's default sender.
  • If mail lands in spam, verify SPF and DKIM for the domain you send from.
  • If Gmail rejects the SMTP login, regenerate the scoped credential and confirm the username matches the alias.

Stop paying a per-seat tax just to send an email. Create your free Forward account, verify your domain, and start sending professional email today.

Start scaling your email without the per-seat tax

Get your custom domain email running in minutes. Send and receive from your existing inbox.

View Pricing