Who it’s for
Small businesses usually pay for three separate email products: mailboxes for the team, a newsletter tool and a service that sends receipts and password resets.
What needed to change
Three bills, three dashboards — and DNS records (SPF, DKIM, DMARC) that decide whether emails land in the inbox or in spam. Most owners don’t know what those are, and shouldn’t have to.
What we built
- [01]Domain onboarding that generates the exact DNS records and verifies them automatically in the background
- [02]Business mailboxes and aliases, with a Gmail-style web inbox and an installable mailbox app
- [03]A sending API for app emails — receipts, password resets — with API keys, safe retries and signed webhooks
- [04]Automatic suppression of bounces and complaints, and one-click unsubscribe
- [05]A separate sending subdomain per customer, so their main domain’s reputation stays protected
- [06]Newsletters with contacts, tags, segments and open/click tracking
- [07]Email sequences that send each step exactly once, with an audit log
- [08]Stripe billing across all three products, and an integration guide written for AI coding assistants
How it works, step by step
- [01]
Choose mailboxes, newsletters or app emails
- [02]
Add your domain — records are generated and checked
- [03]
Create mailboxes or an API key
- [04]
Send team mail, newsletters or app emails
- [05]
Delivery events flow back and bad addresses are suppressed
Results so far
mailboxes, newsletters and app emails
API requests per key, with safe retries
every sequence step, with an audit log
Decisions that mattered
- [01]Rent the hard infrastructure — mailbox hosting and bulk sending — and own the customer experience.
- [02]Swappable email providers behind one layer, so a vendor can be replaced without touching the product.
- [03]A separate sending subdomain for every customer to protect their main domain.
The technology
For the technically curious. You don’t need to know any of this to work with me.