Your email address is your first impression. When a potential client sees johnsmith.consulting.2019@gmail.com in their inbox, you've already lost credibility. When they see john@johnsmith.dev, you look like someone who takes their work seriously.
Setting this up isn't hard—but it's not as simple as just buying a domain and pointing it at Gmail. Here's what I learned getting my professional email running.
Why Custom Domain Email Matters
Every touchpoint with clients shapes their perception. Your email address appears in:
- Initial outreach
- Every reply thread
- Calendar invites
- Invoice emails
- Contract signatures
- Referral forwards
A generic Gmail says "I haven't invested in my business." A custom domain says "I'm established, professional, and planning to stick around."
There's also a practical reason: separation. I don't want client emails mixed with my personal Netflix notifications. A custom domain gives me clean separation without managing multiple inboxes.
The Options
Google Workspace ($6-18/month)
The obvious choice. Full Gmail interface, calendar, Drive—everything works seamlessly. But you're paying $72-216/year per mailbox. For a solo consultant, that's unnecessary.
Microsoft 365 ($6-12.50/month)
Similar deal, Outlook-flavored. If you're in the Microsoft ecosystem already, this makes sense. Same cost concerns apply.
Fastmail, Zoho, Proton ($3-12/month)
Solid alternatives with varying feature sets. Zoho's free tier covers basic needs. Fastmail is excellent but not free. Proton prioritizes privacy.
The Send-As Alias Approach (Free)
Here's what I actually did: keep my existing Gmail, but send and receive as my custom domain. Zero monthly cost. Full Gmail interface. One inbox.
This is the path most solo consultants should take.
Setting Up Send-As Aliases
The idea is simple: emails to owen@owen-devereaux.com forward to your existing Gmail, and you can reply from that address.
Step 1: Set Up Email Forwarding
Most domain registrars offer email forwarding. In your DNS settings, you'll configure something like:
owen@owen-devereaux.com → yourpersonal@gmail.com
Cloudflare does this elegantly through their Email Routing feature. Namecheap, Google Domains (RIP), and others offer similar options.
Step 2: Configure Gmail to Send As
In Gmail → Settings → Accounts → "Send mail as" → Add another email address:
- Enter your custom domain address
- Uncheck "Treat as an alias"
- Configure the SMTP server (use Gmail's own, or your registrar's)
- Verify via the confirmation email
Now when you compose, you can select your professional address from a dropdown.
Step 3: Make It Default
Set your custom domain as the default "Send mail as" address. Set "Reply from the same address the message was sent to" so replies go out correctly.
Done. You now have professional email for $0/month.
The Authentication Trap
Here's where most tutorials fail you. You set up forwarding, it "works," and you start emailing clients. Then you notice: some emails never arrive. Others land in spam. A client mentions they never got your proposal.
Welcome to email authentication hell.
SPF (Sender Policy Framework)
SPF tells receiving servers which mail servers are authorized to send email for your domain. Without it, your emails look suspicious.
Add a TXT record to your DNS:
v=spf1 include:_spf.google.com ~all
This says "Google's servers can send mail for my domain."
If you're using multiple services (maybe Mailchimp for newsletters), you need to include them too:
v=spf1 include:_spf.google.com include:servers.mcsv.net ~all
DKIM (DomainKeys Identified Mail)
DKIM cryptographically signs your emails to prove they weren't tampered with. Gmail handles this automatically for workspace accounts, but for send-as aliases, you need your email provider to set it up.
Cloudflare Email Routing does this. If you're using another provider, check their DKIM documentation.
DMARC (The One That Bit Me)
DMARC ties SPF and DKIM together and tells receiving servers what to do when authentication fails. This is where I learned a painful lesson.
I had SPF and DKIM configured. Everything seemed fine. Then I noticed a client on a corporate Exchange server never received my emails. They weren't in spam—they were rejected outright.
The reason: I'd set a strict DMARC policy prematurely:
v=DMARC1; p=reject; rua=mailto:dmarc@owen-devereaux.com
That p=reject means "if authentication fails, reject the message." Problem is, email forwarding can break SPF alignment. The forwarding server's IP isn't in your SPF record, so the receiving server sees a mismatch and—following your instructions—rejects the email.
The fix: start with a relaxed policy while monitoring:
v=DMARC1; p=none; rua=mailto:dmarc@owen-devereaux.com
Check your DMARC reports (those rua emails) to see what's failing. Only tighten to p=quarantine or p=reject once you're confident in your setup.
Testing Your Configuration
Before emailing clients, verify everything:
- mail-tester.com — Send an email to their address, get a score
- MXToolbox — Check your DNS records
- Send yourself a test — Check headers for authentication results
Look for spf=pass, dkim=pass, and dmarc=pass in the headers. If any show fail, fix it before sending important emails.
The Email Signature
Your signature is real estate. Use it wisely.
Include:
- Your name
- Your title/role ("Independent Consultant" or your specialty)
- Your domain (links to your site)
- One contact method (phone or calendar link, not both)
Skip:
- Inspirational quotes
- Legal disclaimers (unless required)
- Social media icons for every platform
- Your job history
- Images that break in every email client
My signature:
Owen Devereaux
owen-devereaux.com
Consulting: owen@owen-devereaux.com
That's it. Clean, professional, functional.
The Practical Checklist
Here's the minimal setup for professional email:
- ✅ Buy a domain matching your name or brand
- ✅ Set up email forwarding to your existing address
- ✅ Configure Gmail (or your provider) to send-as
- ✅ Add SPF record to DNS
- ✅ Enable DKIM (via your email routing provider)
- ✅ Add DMARC record (start with
p=none) - ✅ Test with mail-tester.com
- ✅ Create a simple signature
- ✅ Send a test email to a friend on a different provider
Total cost: $10-15/year for the domain. That's it.
What This Gets You
Professional email is table stakes for consulting. It's not a differentiator—it's the absence of a red flag. Clients won't hire you because of your email address, but they might not hire you because of a sketchy one.
More importantly: it forces you to treat your consulting as a real business. You have a domain. You have an identity. You're not freelancing from a personal Gmail—you're running a practice.
That mindset shift matters more than the email itself.
Setting up your consulting infrastructure? Check out my rates or how I work. Questions about email setup? Hit me at owen@owen-devereaux.com—I'll prove the setup works.