When late mail moves physical goods.
Shipment notifications, exception alerts, and delivery windows — where a message that arrives an hour late has already failed, and where the downstream cost is measured in trucks rather than tickets.
Downtime you find out about from customers
A sending platform without public incident reporting means your first signal is a support queue filling up. By then the operational decision has already been made badly.
Opaque delivery
“Delivered” tells you a server accepted the message. It does not tell you whether the driver, the warehouse, or the customer actually saw it in time to act.
Latency hidden inside an average
A mean delivery time looks fine while the tail is catastrophic. The messages that arrive late are precisely the ones attached to a time window.
Per-provider evidence
Every event keeps the receiving provider's response. When notifications to one provider start deferring, you can see the concentration and the reason rather than watching an aggregate slowly worsen.
Latency as a distribution
Our published methodology commits to reporting latency as a distribution rather than a mean, because a mean hides exactly the tail that breaks a delivery window.
Incident clarity
We publish incident timelines with scope, cause, remedy, and whether the remedy worked — measured from first customer impact rather than from when we noticed.
SLA on Dedicated
Dedicated plans carry a written SLA with specific numbers and specific remedies, plus a named support contact rather than a queue.
One product, three versions of the same problem.
We do not build a separate edition per industry. The five things below are what every OutSend account gets, and they are what makes each of these workloads tractable.
Agents are first-class
API, CLI, and MCP with verifiable outcomes.
Per-ISP truth
See where every email went — and why.
Reputation sovereignty
Your reputation is yours. No neighbor can burn it.
Observable sending
Explainable by a person or an agent.
Portable by construction
Read it. Run it. Leave freely.
We do not have a public SLA yet.
We are not going to imply one. There is no published service level agreement today, and until there is we would rather say so plainly than let the word “reliable” do the work.
Dedicated plans can have an SLA agreed in writing now. A public one, with teeth, is on the roadmap and will appear alongside the first transparency report — the methodology for which is already published, so you can judge how we intend to measure before we publish any numbers.
Ready to see where your email goes?
Seven days free. No card to start, and everything we claim is checkable.
Open core · never venture-backed · operated by Martin Business Consultants