Engagement — not a product
You bring the goal (“onboarding sequence,” “invoice run,” “deliverability rescue”), we ship the working pipeline on your infra.
We're a small team of engineers who design, build, and run production email infrastructure for product and operations teams. Transactional and lifecycle pipelines, deliverability work, domain reputation rescue, BYO-ESP integrations — on your stack, billed by the engagement.
You bring the goal (“onboarding sequence,” “invoice run,” “deliverability rescue”), we ship the working pipeline on your infra.
BYO SMTP / SES / Postmark / SendGrid / Resend. We never own the sending reputation; you do.
Templates as code, every send recorded with the JSON payload that produced it. Hand-off ready from day one.
If any of these sound like the thing eating your sprint, that's why you should send a note.
Order, billing, password-reset, magic-link — designed and shipped on your ESP, with retries, suppressions, and an audit trail.
Branching journeys driven off your actual product events, not a marketing-tool's ten-step template.
You're landing in spam. We diagnose DKIM/SPF/DMARC, list hygiene, content patterns, and reputation, then ship the fixes.
Move from Mailgun/SendGrid/Mandrill to wherever you actually want to be — templates, lists, suppressions, webhooks, all preserved.
One source of truth, version-controlled, render-tested across the clients your customers actually use.
Inbound bounce/complaint/reply handling with the right thing happening downstream — not just a Slack message no one reads.
Bounce categorization, role-account filtering, engagement decay. The boring work that doubles your inbox rate.
Quiet hours, time-zone-aware sends, per-recipient frequency caps. Programmatic, observable, undoable.
Unsubscribe-of-record, consent timestamps, data-retention policies wired into the actual pipeline — not a checkbox in a UI.
Monthly: domain health review, an inbox-placement test, and a human to call when something blows up at 11pm.