For a decade, outbound tooling has been sold like a clever trick — rented inboxes, shared IPs, a dashboard that hides the machine. We think that's backwards. Sending a million emails a month through your own mailboxes is an infrastructure problem. So we built it like infrastructure: an API, your own credentials, signed webhooks, and a price an agency can actually pay.
NuMail didn't start as a product. It started as a spreadsheet of grievances. We ran outbound for clients on the usual suspects — rented mailboxes that got spun down without warning, shared warmup pools we couldn't audit, "unlimited" plans that throttled the moment volume mattered, and a reply that landed in our inbox forty minutes after the prospect hit send.
Every one of those problems traced back to the same root cause: the tool owned the infrastructure, and we were renting access to it. When something broke, we couldn't see why, couldn't fix it, and couldn't bill our clients with a straight face.
So we rebuilt the layer underneath. Connect your mailboxes — Gmail API, Microsoft Graph, raw SMTP. Send through your own credentials. Detect replies in 2.4s. Draft them with Claude in your voice. Warm up against a real cross-customer pool, not a bot farm. And expose all of it through a REST API and an MCP server, because the future of outbound is half-run by agents.
The tool we wished existed is the tool we shipped. NuMail is that spreadsheet of grievances, fixed.
Every decision in the product gets checked against these. When a feature request conflicts with one of them, the principle wins.
There's no offshore "platform team" you'll never meet. The people who designed the send pipeline answer your support tickets. We run our own outbound on NuMail every week — if a bug ships, we feel it before you do. Dogfooding isn't a slogan here, it's the on-call rotation.
The dashboard is a client of the API — not the other way around. Every action you can take in the UI maps to a documented endpoint with an OpenAPI 3.1 spec, typed SDKs, and HMAC-signed webhooks. If you can't script it, automate it, or wire it into your own product, we consider it unfinished.
Outbound is a margin business, and we refuse to be the line item that eats it. $149 to start, $349 for Pro, $699 for the Agency tier with Stripe-Connect white-label and sub-billing. No "contact sales for pricing," no per-seat extortion, no surprise overage that lands at quota-close. The price is on the page because it should be.
We never rent you an inbox or hide a shared IP behind a curtain. You connect Gmail, Microsoft 365, or SMTP under your own credentials and your own domains. Your sending reputation is yours to build and yours to keep — and if you leave, you walk out with every mailbox, every reputation point, intact. No lock-in by infrastructure hostage.
We didn't staple a chatbot onto a 2019 product. Reply detection at 2.4s, classification, and Claude-drafted responses in your voice are the core loop — and they're exposed to agents through our MCP server so an autonomous SDR can run a whole sequence end to end. AI is the engine, not a marketing badge in the corner of the pricing page.
Idempotency keys on writes. Cursor pagination. Webhooks retried with backoff for 24 hours. A 12-month sunset header before anything breaks. Deliverability isn't where you get to be clever — it's where you get to be predictable. We save the surprises for the changelog, never the production pipeline.
We don't want to be the clever growth hack you churn off in six months. We want to be the boring, dependable layer your whole outbound business runs on — the part you stop thinking about because it just works.
NuMail is a focused team of engineers and operators who spent years running outbound for agencies and founders before deciding to build the layer underneath it. We're product-led and engineering-heavy — most of the company can read the send pipeline, and the people making roadmap calls are the same people who've felt a domain get cooked at 2am.
We build in the open where it counts: a public changelog, a versioned API, and honest docs. You send through your own mailboxes — Gmail, Microsoft Graph, SMTP — Claude drafts the replies, and agencies bill clients on their own Stripe. No black boxes you can't see into, no "proprietary deliverability magic" we won't explain — just infrastructure built carefully and documented honestly.
We're cash-flow minded, not growth-at-all-costs. That's why the pricing is fixed and public, why the API came before the polish, and why the agency tier is built to make you money rather than meter every send. We'd rather earn a decade of your business than a quarter of your runway.
The blog goes deep on deliverability, warmup, and building outbound that lasts. Or skip ahead — connect a mailbox and watch the loop run on a 14-day trial.