Resend Expands into Marketing Automation

This is the move that can turn Resend from an infrastructure line item into a larger system of record for customer messaging. Once a product team is already sending receipts, password resets, or alerts through Resend, Broadcasts and Automations let marketing and lifecycle teams use the same event stream and contact data for welcome flows, win back emails, and campaign sends, instead of exporting users into a separate tool.1 2 3 4

• The product expansion is concrete. Resend now positions itself around transactional, marketing, inbound, and automated email, and prices automations separately by run. That creates a second budget path beyond developer API usage, because a growth team can spend more as it launches journeys and campaigns on top of the same email stack.2 3 4
• The closest precedent is Customer.io. It built a large business by taking app events and user attributes, turning them into segments and branching workflows, and selling that to technical growth teams before broader marketing organizations. Customer.io has since scaled to an estimated $100M ARR, showing how far the engagement layer above raw delivery can expand monetization.5 6
• The competitive tradeoff is that winning transactional email gets Resend into the account, but winning marketing dollars requires serving non developer users well enough to displace tools like Mailchimp, Klaviyo, or Customer.io. The more campaign logic, audience data, and deliverability history live inside Resend, the harder it becomes to swap out just one piece.1 5 7

The next step is a broader convergence of developer infrastructure and marketing software. If Resend keeps making campaign building, audience management, and inbox workflows usable for non technical teams, it can grow from an email API into the shared messaging layer that product, support, and lifecycle teams all build on.1 2 3 7