Email Marketing Case Studies: Revenue From the List
See Where Your Email Program Can Work Harder
- Lifecycle and automation coverage
- Deliverability and list-health risks
- Measurement and revenue-attribution opportunities

“I have worked with some of the OuterBox team members in a past life so it was an easy call to make when we needed help with our email strategy. They took the time to thoroughly understand our situation and came up with a comprehensive solution to not only address our immediate needs, but align them with our long-term goals. The work they have done is already paying off and I know we will exceed our expectations.” — Mark Melius, Zerbee Business Products
All Email Marketing Case Studies
Email Marketing FAQs
How long before we see results from email?
The flows in these case studies produced measurable revenue inside a quarter. Unclaimed Baggage’s cart-abandonment flow returned $51,000 in its first 90 days before we made any further changes. Timelines depend on list size and how much automation already exists.
Do you work in our email platform, or move us to a new one?
We work in yours where it is viable. Every case study on this page runs in Klaviyo, and we also work in HubSpot, Salesforce Marketing Cloud, and Mailchimp.
What happens after I request a review?
We review your current setup for gaps in lifecycle and automation coverage, deliverability and list health, and measurement and revenue attribution. No obligation.
We already have automations. Is there anything left to gain?
Usually yes. Mount-It’s 141% came from optimizing an existing Welcome Series rather than rebuilding it, and one of the largest single wins was repairing a broken integration that had been quietly losing revenue.
Do you do SMS as well as email?
Yes. Unclaimed Baggage and Mount-It both run SMS alongside email in Klaviyo, which is what makes behavioural segmentation work across both channels.
Who owns the flows and templates you build?
You do. The segmentation logic, lifecycle flows, and template system live in your platform under your account, and your team can run them without us.












