Industry

SaaS & Transactional

Product notifications, magic links, password resets, in-app alerts, digest emails. The application depends on email delivery. Failure modes are latency, not just placement.

Challenges

Latency-sensitive: a delayed magic link is a failed login
Per-tenant attribution required for reporting and support
Volume grows with the customer base — capacity planning is continuous
Reputation isolated from any marketing activity the product also does

Our approach

Dedicated transactional IPs with sub-30s median delivery targets
Per-tenant tagging for downstream observability
REST API with signed webhooks for delivery events
Isolated from any marketing sending the same company operates

Deliverability recommendations

Send transactional and marketing from different subdomains at minimum
Instrument delivery event ingestion into the product's observability stack
Rate-limit magic link resends at the application layer, not the SMTP layer

Example engagements

B2B SaaS platform: migrated 12M/month transactional volume; median delivery at Microsoft went from 68s to 18s; support tickets for 'didn't get the email' dropped 71%.

Examples are anonymised. Named references available under mutual NDA.

Questions

Do you handle IPv6?

Yes for outbound. Some providers still throttle IPv6 more aggressively, so we typically default to IPv4 for transactional.

Other industries

iGaming
Casino, sportsbook, poker and lottery operators face some of the strictest filter posture …
Affiliate Marketing
Affiliate and performance-marketing programmes send at scale across shifting offers, creat…
Crypto & Web3
Exchanges, wallets, Web3 platforms and on-chain services all send high-volume email — tran…
Forex & CFD
FX and CFD brokers combine regulated status with high-volume promotional and educational c…
Lead Generation
Direct-response lead-gen programmes live or die by inbox rate. Whether you are running len…
E-commerce
High-frequency lifecycle programmes — carts, browses, back-in-stock, price drops, order co…