Custom domain email for founders means the company name on From and To without buying a suite seat you will not use. Keep personal Gmail. Point the domain at one exclusive hop. Map founder@ and hello@ into the inbox you already search. MailerZ does that with MX plus authenticated SMTP. Free receives on one domain. Solo is forty dollars a year when you need send-as. Do not buy Workspace because a blog said businesses have Workspace.
Quick answer for custom domain email for founders
Register the domain if you have not. Add it to MailerZ. Publish the MX and TXT the dashboard prints. Delete the parking MX the registrar added for 'email coming soon.'
Create founder@ and hello@ as named aliases. Point both at the Gmail you already open. HOLD everything else. You do not need a catch-all in week one.
Receive on Free. Print the address after a third-mailbox probe lands. Buy Solo when a vendor or customer must get mail From the domain, not from your personal Gmail.
Transport: IETF RFC 5321 — Simple Mail Transfer Protocol. DNS: IETF RFC 1035 — Domain names. Gmail send-as help: Google Gmail Help — Send mail from a different address. Paths: email forwarding, send and reply, pricing.
User problem and decision criteria
Founders buy the wrong email product because the internet sells fear. 'Real companies use Workspace' is a marketing sentence. A real company needs a domain people can reply to and a From that matches the site.
Decision criteria: you already live in Gmail or Outlook; you do not need IMAP folders on the domain; you can change DNS; you will delete leftover MX; you can wait a TTL; you will probe from another account.
If you need shared Drive with a cofounder tomorrow, that is a suite buy. Still consider whether that suite must own MX. Many teams keep Docs on Google and mail on a forwarder. Mixing those jobs is optional.
If you want anonymity from the domain itself, stop. A custom domain is a public identity. Privacy aliases on a domain you own are containment, not invisibility.
If you cannot name who logs into the registrar, you are not ready to cut MX. Recover the registrar first. Email is downstream of that login.
If a developer friend offered to 'just run mailcow,' you are buying a second job. Founders with a product to ship should not adopt an MTA for fun.
Technical mail flow for a one-person company
Customer writes hello@yourdomain. Their server asks DNS for MX. After a correct cut, that answer is only MailerZ. MailerZ accepts, applies SRS on the envelope, and hands the message to your Gmail with the original Header From.
You read it in Gmail like any other mail. Reply-all still shows the customer's address. You are not impersonating them. You are receiving.
When you send-as, Gmail (or another client) authenticates to MailerZ SMTP with the dashboard values. MailerZ is not an open relay. If the identity is not hosted or not allowed, you get 550 5.7.1.
Plus addressing on Gmail is not a custom domain. hello+investor@gmail.com is still gmail.com. Investors can see that. The domain is the product you are buying.
Leftover MX from the registrar's 'free email' split senders. Your probe can hit MailerZ while a paying customer hits the parked host. That is the first-week outage founders blame on 'DNS propagation.'
Step-by-step buy path
- Confirm you can log into the registrar and the DNS host. They are often different companies.
- Add the domain in MailerZ. Start free.
- Publish exclusive MX and verification TXT. Delete parking and website-builder MX.
- Create two or three named aliases. HOLD unknown.
- Wait TTL if you changed records that still advertised the old host.
- Send a uniquely titled probe from a mailbox that is not yours.
- Open the original, not a forwarded copy you sent yourself.
- Only then print the address on the site, Stripe, and the pitch deck.
- Add send-as after Solo if you must reply From the domain. Copy dashboard SMTP. Follow Gmail's send-as screens.
- Write a one-page note: registrar, DNS, MailerZ login, alias list. Future you is a stranger.
Failure modes and proof
Empty hop after a 'successful' DNS save: you edited the ghost zone. Check NS.
Mail in the registrar webmail after cut: leftover MX or a republished builder product. Delete names. Disable the product.
Gmail saying you cannot send-as: you are on Free, or you invented the SMTP host. Copy the dashboard. Confirm /pricing.
Investor mail in spam: destination reputation and content. MailerZ does not sell an inboxing number. Do not promise one on a launch thread.
Cofounder still using @gmail.com in public: that is a people problem. The hop cannot fix a bio.
Proof is the probe, the hop line, and two resolver listings. A screenshot of the DNS UI is not proof the world sees those rows.
MailerZ workflow and product boundary
MailerZ is Secuno LLC. Site mailerz.net. Desk mail.mailerz.net. Receive, reply, and send as the domain. Not Workspace. Not IMAP. Not SOC 2.
Free: one domain, three aliases, one seat, fourteen-day store, fifty outgoing a month, HOLD unknown, no send-as.
Solo: forty dollars a year, fifteen aliases, ninety-day store, one hundred outgoing, five send-as an hour, unknown forwarded.
Starter, Business, and Agency exist when you hire or add domains. Do not pre-buy Agency as a founder with one zone.
The store recovers hops MailerZ saw. It does not replace Gmail search. Export anything you must keep beyond the window.
If you need a mailbox host, buy one. Do not hammer MailerZ into IMAP. The 550 you get is the product telling you the truth.
Cost and alternatives
Google Workspace monthly per user is honest if you use the suite. It is expensive if you wanted a From line.
Microsoft 365 is the same shape. Outlook as a destination does not require Microsoft MX.
Cloudflare Routing is a fair inbound experiment. Add a send-as story before you print invoices From the domain.
Apple Hide My Email and other masks are not company email. Banks and payroll will not treat a random icloud relay as founder@.
A personal domain on Fastmail or a host is fine if you want folders. You are then running mail, not forwarding. Budget time.
The founder math that matters: domain renewal plus MailerZ Free or Solo versus a suite seat you will forget to cancel. Confirm live prices. This page does not freeze them.
Which addresses to create first
founder@ or your-name@ for humans who already know you. hello@ or team@ for the site form. billing@ if Stripe and the bank must have a stable box.
Do not create twenty role addresses on day one. You will not read them. Three aliases on Free is a design constraint, not an insult.
Do not put your personal Gmail on the site 'until DNS works.' That leak lasts years in caches and decks.
Do not use plus addressing on the company domain as your only isolation. Named aliases disable cleanly. Plus tags get stripped by sloppy forms.
Legal@ can wait until you have counsel. A hollow legal@ that you never open is how a subpoena sits in HOLD.
When a vendor leaks hello@, disable that alias and make a new one. Do not burn founder@ because a shop sold a list.
When the first hire changes the buy
A first hire who lives in Gmail can take a named alias. They do not automatically need a Workspace seat for mail.
Shared passwords to founder Gmail are the usual disaster. Give the hire their own destination and their own alias. Rotate anything they saw.
If you now need calendar and Drive as the company, buy the suite for those jobs. Revisit whether MX must move. Many teams leave forwarding in place.
Catch-all FORWARD becomes tempting when customers guess names. HOLD plus a weekly review is safer until you like the noise.
Upgrade the MailerZ plan when aliases or send-as limits bite. Do not open a second hacked-together forwarder beside the first. That is leftover MX with extra steps.
Write the handoff while you still remember the registrar. Founders who 'keep it in their head' become the outage when they fly.
Worked scenarios for founders
You incorporated last Tuesday. The registrar offered 'free professional email.' That product published MX you did not read. Your first Stripe receipt bounced to a parking host. Custom domain email for founders starts by deleting that gift, not by buying Workspace.
You already live in personal Gmail. An advisor said companies look fake without Workspace. You need hello@ on the site. You do not need Drive this month. Buy exclusive MailerZ MX. Keep Gmail. Revisit the suite when a hire asks for calendar as the company.
You printed founder@gmail.com on the seed deck. That leak will outlive the round. Create founder@ the domain, probe it, then send a short correction. Do not wait for 'when DNS is done.' DNS is done when two resolvers agree and a third mailbox lands.
A cofounder wants their own mailbox host 'for privacy.' That is a second company. If you still publish one MX set, they get aliases. If they publish a second MX, you bought leftover MX. Pick one hop.
You need to email a bank From the domain. Free will 550. That is not an outage. That is the plan. Solo is forty dollars a year. Confirm pricing. Then copy dashboard SMTP. Then follow Gmail send-as. Then probe from a third path.
A no-code site builder turned email on again after you published a landing page. Morning mail hits the builder. Re-query after every website save until that product stays off.
You asked a friend to 'check if email works' by writing to themselves. They used Gmail to Gmail. The check lied. Use a mailbox that is not yours.
Practice and anti-patterns for a one-person company
Practice: two or three named aliases. Anti-pattern: twenty role addresses you will never open.
Practice: HOLD unknown. Anti-pattern: catch-all FORWARD because it felt complete.
Practice: a one-page note with registrar, DNS, MailerZ, and alias list. Anti-pattern: 'I will remember.'
Practice: print the address after the probe. Anti-pattern: print first, debug in public.
Practice: upgrade when send-as is the job. Anti-pattern: keep old Workspace MX because you have not paid Solo yet.
Practice: plus addressing only on sites that keep the plus. Anti-pattern: plus as your only isolation.
Practice: disable a leaked shop alias. Anti-pattern: burn founder@ because a coupon site sold a list.
Custom domain email for founders stays cheap when the map stays small and exclusive.
Operator closeout before you print the deck
Closeout for a founder is shorter than an agency packet and just as strict. Two resolvers. One third-mailbox probe per public alias. Leftover parking MX gone. Builder email off.
If you will send-as, closeout includes the paid plan and a unique subject that left through MailerZ SMTP. If you will not, closeout says inbound only so you do not discover 550 on a customer thread.
Put the registrar 2FA device in a drawer you can name. Founders lose companies on airplanes because the only phone is in the seat pocket.
Write the close date for the registrar's leftover email product. If there is no product, write 'none.' Silence is how gifts return.
Share the one-page note with a deputy even if the deputy is a spouse who should not operate it unless you are unreachable.
Schedule a quarterly reminder to re-query MX. Website builders and 'helpful' registrars republish.
Then print the address. Not before. Custom domain email for founders is a sequence, not a vibe.
Edge cases founders hit in month one
A university or corporate firewall still caches the parking MX. Call them after the clock. Do not republish the parking host to be polite.
Apple Hide My Email on your phone is not company email. Do not put a relay on the invoice.
Namecheap, GoDaddy, and peers will sell you mailbox upsells after you already cut. The upsell often writes MX. Read the zone after every purchase.
A no-code form that sends From your Gmail instead of the domain. That is the form product. MailerZ inbound cannot fix outbound the form owns. Use send-as or the form's SMTP if you paid for it.
A partner who insists on being CC'd on hello@. Give them a destination on the alias or a mail filter. Do not share the Gmail password.
You bought the .com and the .io. Only one should be exclusive MX unless you intend to operate both. The other can 550. Two half-configured zones is two outages.
You moved countries and lost the registrar SMS. Recover that before you need to rotate a leaked alias. Email is downstream of the registrar.
Field notes from founders who printed the address too early
The usual first outage is not MailerZ. It is the registrar gift MX you never read. You added MailerZ, you did not delete parking, and a paying customer hit the gift. Custom domain email for founders is a delete job first. Add is easy. Delete is the product.
The usual second outage is self-send. You emailed yourself from Gmail, saw nothing, and spent a night in SPF folklore. Gmail can short-circuit. A friend with a different provider is the whole test. Keep one for launch week.
The usual third outage is a website builder that turns email back on when you publish a landing page. Re-query the morning after every marketing push until that toggle stays off. Founders who ship pages at midnight discover this at nine.
Advisors will sell you Workspace as adulthood. If you need Drive and Meet as the company, buy it. If you need a From line, do not. Put both invoices on one page. You will pick the number you can explain to a cofounder.
Hide My Email on your phone is not hello@. Banks will not play. Keep masks for junk. Keep the domain for money.
Write the one-page note while you still remember the registrar. Founders who keep it in their head become the outage when they fly. A spouse who can open the note is a continuity plan, not an operator, until they have done the lab loop.
Free receives. Solo sends. Confirm pricing the day you promise a bank you will reply From the domain. A 550 on that thread is a plan error, not a DNS mystery.
Print the address after the packet exists. Decks outlive TTL. You cannot unprint a Gmail.
Handoff memo for future you
Future you is a stranger. Write registrar, DNS host, NS check, MailerZ URL, alias list, HOLD policy, whether send-as is paid, and where the 2FA device lives.
Include the last probe IDs and the date leftovers were absent. Include the builder product you had to disable twice.
If a cofounder joins, they get their own alias and destination. They do not get your Gmail password. The memo should say that before anyone asks.
If you sell the company, the memo is part of the asset. Masks on your Apple ID are not.
Schedule the quarterly MX re-query in the same calendar as domain renewal. They are the same class of forgetting.
Acceptance criteria before the deck goes out
Two resolvers exclusive. Third-mailbox probe per public alias. Parking and builder MX gone. HOLD on unless you wrote otherwise.
If send-as is in the deck, Solo or above is live and a unique subject left through dashboard SMTP. If not, the deck does not imply it.
The one-page note exists. The deputy knows where it is.
You did not print personal Gmail on the site 'until DNS works.'
You can say MailerZ is not a suite and not a badge without flinching.
Operations review after you are live
Once a week for the first month, query two resolvers and send one unique probe to hello@. Founders who skip this learn about leftover MX from a customer. Custom domain email for founders stays cheap when the review is a calendar item, not a feeling.
Read HOLD. If it is empty, good. If it is full of guesses, your prefixes are obvious or someone is stuffing. Tighten local parts. Do not turn on FORWARD to 'clean it up.'
If you hired, give them an alias and a destination. Do not share founder Gmail. Rotate anything they saw. The first hire is when sloppy maps become incidents.
If you added a no-code form, confirm whether it sends From Gmail or through MailerZ SMTP. Forms that lie about From will confuse the bank you just impressed with send-as.
If you bought a website theme that 'includes email,' read the zone after install. Themes include leftover MX more often than they include taste.
If Solo send-as is live, keep a monthly unique subject in a ticket so you know 550 is new.
If you still have the registrar gift product, cancel it. An unused gift that can write MX is a loaded gift.
Quarterly review for a one-zone company
Re-read pricing. Confirm you are still on the plan you think you are. Confirm alias count versus cap.
Re-query MX. Re-check NS. Re-disable any builder email that returned.
Diff the alias list against the site footer, Stripe, and the deck. Orphans go or get documented.
Retest one reset on a high-risk login if you also use aliases in a vault.
Reread the one-page note. If the deputy cannot find the 2FA device, fix that before you travel.
If the company now needs a suite, buy the suite for the suite. Do not assume MX must move. Many teams leave forwarding in place.
If you outgrew one domain, add the second as its own exclusive hop. Do not dual-publish a merger of .com and .io.
Appendix notes
Appendix: if a university or office firewall still caches parking MX after your clock, call them. Do not republish parking to be polite. Custom domain email for founders includes that awkward call.
Appendix: Namecheap, GoDaddy, and peers will upsell mailboxes after a cut. The upsell writes MX. Read the zone after every purchase, including SSL and parking add-ons.
Appendix: the .com and the .io are two hops if you operate both. A half-configured second zone is a second outage. 550 on the unused name is allowed.
FAQ
What is the safest way to handle custom domain email for founders?
Keep Gmail. Publish exclusive MailerZ MX. Map founder and hello. Delete leftovers. Probe from a third mailbox. Buy Solo only when you must send-as.
Does this require a new mailbox?
No. MailerZ is not IMAP. A new mailbox is optional and usually waste for a one-person company.
Will it work with Gmail or Outlook?
Yes as the destination. Self-send can fail. Use a personal second account or a friend. Free has no send-as.
What DNS records are involved?
Exclusive MX, verification TXT, leftover rows gone. SPF and DKIM when you send. NS must name the panel you edit. RFC 1035 first if two panels exist.
What should you test before printing the address on a deck?
A unique subject to each public alias from an unrelated provider, hop history, and Header From matching the sender. Then a send-as only after you pay for it.
When should a founder still buy Google Workspace?
When they need the suite: shared Drive, Meet as the company, or a policy that demands Google MX. Email-only founders should not pay per-user tax for forwarding.
Key takeaways
- Custom domain email for founders is exclusive MX plus the inbox you already use.
- Do not buy a suite to obtain hello@.
- Free receives. Solo starts send-as. Confirm /pricing.
- Leftover registrar MX is how first customers vanish.
- Self-send is not the launch test.
- HOLD unknown until you like typos.
- Header From stays intact. Envelope uses SRS.
- No inboxing promise and no SOC 2 claim.
Conclusion and next action
Founders should buy custom domain email as exclusive MX and two or three named aliases, not as a suite. Keep Gmail. Delete leftover MX. Probe from another mailbox. Upgrade when send-as is the job. MailerZ will not invent Docs or a compliance badge. It will show the hop it accepted. Start free on one domain.
Ready to put the domain on Gmail
Start free on one domain and prove inbound before you print the address.
Receive on Free. Solo when you must send-as. Sign in if the domain is already there.
Review quarterly, or sooner if provider behavior, pricing, or MailerZ scope changes. Author: MailerZ editorial, Secuno LLC.