Which flows do we build?
| Flow | Trigger | Benchmark context |
|---|---|---|
| Abandoned cart | Checkout started, no order | $3.65 avg revenue per recipient; 3.33% placed-order rate (Klaviyo) |
| Welcome | New subscriber | $2.65 avg RPR; top 10% of programs reach $21.18 |
| Browse abandon | Product viewed, no cart | Runs on Klaviyo/Omnisend site tracking |
| Cancel-save | Cancellation intent signal | A fitness app's rebuilt flow went from 3.4% to 6.1% clicks |
| Win-back | Engagement decay threshold | Triggered by score decay, not a fixed 90-day timer |
Cart recovery matters because the leak is enormous: the average online cart abandonment rate is 70.2%, per Baymard Institute's meta-study of 50 datasets. A three-touch sequence recovering even a modest share of that is usually a store's single best email investment.
What makes our flow builds different?
Timing comes from the audience map built in the Audience Intelligence service. Instead of one cart sequence for everyone, suppression and offer depth vary by segment: VIPs skip the discount, high-churn-risk profiles get a gentler cadence, and silent profiles are excluded entirely so the flow's engagement stays strong in Gmail's eyes.
Every flow ships with an A/B test plan. Subject lines and send delays get tested against your baseline for at least two full cycles before we call a result. Reporting is in revenue per recipient and placed-order rate, the numbers Klaviyo's benchmark reports use, so you can compare yourself to your category directly.
ESP builds and migrations
We build natively in Klaviyo (both strategists are Klaviyo Product Certified), Omnisend, Braze, and Customer.io. Platform migrations include flow rebuilds, list transfer with engagement history, revenue-tracking parity checks, and a 30-day overlap period so nothing silently breaks. See our process for how a typical 6-to-10-week build is sequenced.