Why AI Email Assistants Fail for Custom-Domain Users
Most AI email tools quietly require a Google or Apple account. If you’re on a custom domain, here’s why you keep getting left out — and what actually works instead.
Almost every AI email assistant requires a Google or Apple account, so anyone on a custom domain (you@yourcompany.com over IMAP) is locked out. Tomorrow is built the other way around: it works on any IMAP mailbox, reads your inbox, prepares actions, and executes them with your approval — no matter who hosts your mail.
The Gmail tax on AI email
The current wave of “AI email” products has a quiet entry requirement: a Google Workspace or Gmail account. Some add Outlook. Almost none support standard IMAP.
- Poke is an iMessage-first assistant that connects to Gmail and Google only.
- Orchid is a delegation layer built on Gmail and Google Calendar.
- Shortwave is a genuinely good AI client — for Gmail, and only Gmail.
- Superhuman covers Gmail and Outlook, but offers no agentic workflow layer.
If you live inside Google Workspace, you have options. If you don’t, the category has mostly ignored you. That’s the Gmail tax: the assumption that “email” means “Gmail,” baked into the OAuth flow before you ever see a feature list.
Why custom-domain users get left behind
This isn’t an accident, and it isn’t only laziness. There are real reasons builders default to Gmail:
- OAuth is easier than IMAP. Google and Microsoft hand you a clean OAuth scope and a rich API. IMAP is an older protocol with more edge cases across providers, so it’s tempting to skip.
- The loudest early adopters are on Workspace. Venture-backed startups skew toward Google Workspace, so that’s who early products optimize for.
- IMAP is unglamorous. It doesn’t demo as well as a slick Gmail integration, even though it’s what most of the world’s professional email actually runs on.
The result: founders, freelancers, and small teams on name@theircompany.com — exactly the people who’d benefit most from an assistant handling triage — are the ones the category leaves out.
What “works on any email address” actually requires
Supporting custom domains isn’t a checkbox; it’s an architecture decision. An AI inbox that genuinely works for non-Gmail users has to:
- Speak IMAP and SMTP directly, not just a single provider’s proprietary API, so it can connect to Fastmail, Outlook, your registrar’s mail, or a self-hosted server.
- Handle credentials securely, because IMAP often means app passwords or stored credentials rather than a delegated OAuth token.
- Parse mail provider-agnostically — threading, labels, and attachments differ across servers, and the intelligence layer has to normalize all of it.
This is the foundation Tomorrow is built on. Universal IMAP support is the single biggest reason to choose it over a Gmail-only tool — it’s why Tomorrow can be the AI email client for IMAP that the rest of the category isn’t.
What you should be able to do on a custom domain
Connecting is the floor, not the ceiling. On a custom domain you should get the same agentic capabilities Gmail users are being sold:
- Triage that understands context — Tomorrow reads what comes in and surfaces what matters, because it already knows your threads and your clients.
- Drafted replies in your voice, ready for one-click send.
- Workflows that set themselves up from plain language — describe “when a supplier emails an invoice, create it in Moneybird” and Tomorrow builds the recipe. No Zapier, no flow builder, no developer.
- Approval-gated execution. Every side-effecting action — sending a reply, creating an invoice, updating a task — waits for your explicit approval before it runs. You stay in control without staying in the inbox.
Tomorrow reaches the tools you already use through multiple integration paths — Composio (500+ providers), MCP servers, OpenAPI specs, and a browser fallback for tools with no API — so automation isn’t limited to whatever a single integration marketplace supports.
Common mistakes when choosing an AI inbox
- Assuming “AI email” includes your provider. Read the connect screen first. If it only offers “Sign in with Google,” a custom domain won’t work.
- Confusing a client with an agent. A faster inbox still leaves you doing the work. An agent prepares and executes the work — with your approval.
- Paying for speed you don’t need. Superhuman optimizes keystrokes; it won’t draft an invoice or chase an unanswered thread for you.
- Accepting full autonomy. A tool that acts without asking is a liability in a real inbox. Insist on approval-gated actions.
Frequently asked questions
Can I use an AI email assistant with a custom domain?
Yes — but only if it supports IMAP. Most popular AI email tools require a Google or Apple account and won’t connect to a custom domain. Tomorrow works on any IMAP mailbox, including custom domains on any mail server.
Is Tomorrow a Gmail alternative?
Tomorrow works with Gmail, but it isn’t limited to it. Unlike Shortwave or Orchid, it also runs on Outlook, Fastmail, and custom domains over IMAP — so it’s a real option if you’ve outgrown Gmail-only tools.
Does Tomorrow send emails or take actions on its own?
No action runs without your approval. Tomorrow prepares replies, drafts, invoices, and tasks, then waits for you to approve before anything is sent or changed.
What tools can Tomorrow automate?
Tomorrow connects through Composio (500+ providers), MCP servers, OpenAPI specs, and a browser fallback — covering founder workflows like email-to-invoice (e.g. Moneybird), follow-up reminders, and creating tasks in Linear or Notion.
How much does Tomorrow cost?
Pricing is on the pricing page, and you can review plans before connecting a mailbox.
The AI inbox that works on any email address
If you’ve been locked out of the AI email wave because you’re on a custom domain, that’s the whole reason Tomorrow exists.
