KoltrixPersonal domain or product domain: where a founder's email lives
Should a founder use a name-based domain or the product's domain for email? How to split the two, plan for a rename or sale, and avoid losing old mail.
On this page(9 sections)
Early in a company's life, a founder's email address is a small decision that quietly becomes a large one. Investors, customers, vendors and old colleagues all learn it. Two years later the product is renamed, or the founder starts a second project, or the company is acquired, and every address that was built on the wrong domain has to move.
The question is simple: should your everyday email live on a domain with your name on it, or on the domain of the product you are building? The honest answer is "both, for different jobs". This guide explains how to split them so that nothing important is tied to a name that may change.
If you are still choosing the domain itself, start with choosing a domain with email in mind. If you are still on a free personal mailbox, read moving from personal Gmail to a custom domain first.
What each domain is good for
A personal domain is something like mayaokafor.com. It follows you from project to project. It is the right home for addresses that describe you as a person: your writing, your speaking, your advisory work, your long-term contacts.
A product domain is something like yourproduct.com. It is the right home for everything that speaks for the company: support, billing, sales, press and the sign-off on your product emails. It carries the brand, and customers expect to see it.
Neither is wrong. The mistake is mixing the roles, for example sending customer support from a personal domain, or receiving personal references on an address that disappears when the product does.
A simple split
| Address | Domain | Why |
|---|---|---|
maya@ (day-to-day founder mail) |
Product | Customers and partners see the company, and the mailbox is covered by the company's security setup |
support@, billing@, hello@ |
Product | Role addresses belong to the company, not to a person |
maya@ (personal) |
Personal | Advisors, press, references, newsletters you read, anything that should survive a rename |
| Product notification mail | Product, on a sending subdomain | Keeps transactional mail separate from people |
Notice that the founder can hold an address on each domain. That is fine, and often the best setup: two mailboxes, or one mailbox that receives mail for both.
Reasons to prefer the product domain for work mail
- Trust. A message from
[email protected]looks like the company. One from a name-based domain can look like a personal project, and in a cold outreach it may look like a free-mail address with extra steps. - Control. The company owns the domain. If the founder leaves or a co-founder joins, access is a company matter, not a personal favor.
- Security. Company mail can be covered by the same two-factor authentication, DKIM and DMARC setup as everything else. Why Koltrix signs each domain with its own DKIM key explains what that means for each domain you connect.
- Handover. When a first hire starts to share the inbox, handing the inbox off is easier if the addresses are already role-based and on the company domain.
Reasons to keep a personal domain too
- Continuity. If the product is renamed, shut down or sold, your personal address does not change. Contacts you made over years can still reach you.
- Reputation that is yours. Writing, talks and open-source work are tied to you. A personal domain lets that reputation stay in one place.
- Independence. You may build more than one thing. A domain with only your name does not need to be explained each time.
- Safe forwarding target. Role addresses can forward to a personal mailbox if you ever need to hand over a company domain and keep a copy of the conversation.
What happens when the product changes
Founders often underestimate how often a name changes. A trademark conflict, a pivot or an acquisition can all force one. If your email is built carefully, the change is a project. If not, it is a crisis.
Plan for it from the start:
- Keep the old domain. Renew it for years, not months. Never let it lapse: someone else can register it and receive mail meant for you. See moving company email to a new domain for the full migration steps.
- Forward, then keep forwarding. Old addresses should deliver to new ones for at least a year, preferably longer. The people who still write to the old address are often customers and partners, not spam.
- Update the places that remember you. Billing portals, domain registrar accounts, app stores, bank, tax authorities and every service where the old address is a login. List them before you cut over, and change the login address first.
- Do not abandon the old domain's records. If you stop using it for sending, publish a strict policy so nobody can spoof it. Locking down parked domains shows how.
- Tell people once, clearly. Send a short note from the old address announcing the new one, and keep the old one working beside it.
Mistakes to avoid
One mailbox for everything on the personal domain. Support mail piles up in a founder's private inbox, and the company has no record of it when that person is unavailable.
Registering the product domain in a personal registrar account. Put the domain in an account the company owns, with a role address as the contact and two-factor authentication on. If it belongs to your private login, it is hard to transfer later.
Sending bulk mail from a personal domain. Marketing and notification email can hurt the reputation of the domain it is sent from. Use a subdomain of the product domain, as described in sending subdomain strategy, and keep personal mail out of it.
Leaving the founder as the only recipient. Role addresses should reach more than one person, or a shared mailbox, so that a holiday or illness does not stop customer mail.
Using a free mailbox as a safety net. A free address is easy to start with but cannot be authenticated for your brand and is a weak place to keep recovery mail for important accounts.
A checklist for this week
- Product domain registered in a company-owned account with two-factor authentication on
- Role addresses created:
support@,billing@,hello@, each reaching at least two people or a shared mailbox - Your day-to-day work mailbox on the product domain
- A personal domain kept for your own long-term contact, with a mailbox or a forward
- SPF, DKIM and DMARC published for every domain that sends or could be spoofed
- A written list of every account that uses a founder address as its login
- A calendar reminder to renew every domain, including the ones you no longer use
How this looks in a team inbox
In Koltrix you connect each domain you own and create the mailboxes you need on it. You can read personal and company addresses in one place, use labels to keep them apart, and let the AI sort the incoming mail into Primary, Updates, Promotions, Newsletters and Cold pitches. Drafts are always yours to review and send: nothing goes out without a human click. If you want an AI assistant to help with triage, the MCP server lets Claude or ChatGPT work with your mail from the apps you already use.
Key takeaways
- Use the product domain for anything that speaks for the company, and a personal domain for anything that should outlive it.
- Own the domains in a company account, with role addresses as contacts and two-factor authentication on.
- Plan the rename before it happens: keep the old domain, forward its mail for a long time and list every account that uses it as a login.
- Keep marketing and notification mail on a subdomain, and keep personal mail out of it.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
