Grow the list. Watch the bill stay put.
Broadcasts, segments, topics, and a hosted preference center — the lifecycle toolkit you expect, priced on the events you track instead of the contacts you store. Every plan carries unlimited contacts, so a good acquisition month never arrives as an invoice problem.
| Contacts | Customer.io | Klaviyo | Wraps |
|---|---|---|---|
| 5,000 | $100 | $100 | $19 |
| 10,000 | $145 | $150 | $19 |
| 50,000 | $505 | $720 | $19 |
| 100,000 | $955 | $1,380 | $19 |
Wraps tiers move on tracked events, not list size, and sending is billed by AWS directly at SES rates. Competitor figures verified July 2026.
Ship the campaign without booking an engineer.
A four-step composer that goes from template to scheduled send. The engineering team set up the sending infrastructure once; they do not need to be in the room for the newsletter.
Pick an audience without writing a query
Send to everyone, to a topic, or to a saved segment. The audience resolves to a live recipient count you can see before you schedule anything.
Map your variables, or let it guess
The composer auto-detects the variables in a template and maps them to contact fields or static values. First names come from the list; the campaign name you type once.
Preview against real people
A preview carousel renders the email with actual sample contacts from the audience, so you catch the empty greeting before it ships, not after.
Schedule in plain English
Type “next Wednesday at 9am” and it parses. Scheduled and in-flight broadcasts can be cancelled up until they finish.
Two different ways to stop sending everyone the same thing.
Segments — what you decide
A visual builder with AND/OR groups over engagement, dates, counts, topic membership, and any custom property you put on a contact. Save it once and it resolves fresh every time you send.
- Opened something in the last 30 days but never clicked
- Signed up before June and still hasn’t confirmed
- Subscribed to product news, not to billing alerts
- Any custom property your app writes — plan, region, role
Preview any segment for a count and sample addresses before you commit. Behavioral filters — triggered or didn’t trigger a given event, within a window — are on the Scale plan.
Topics — what they decide
Named subscriptions your contacts opt into individually, with double opt-in and a hosted preference center linked from the footer of every send. You style it; we host it and keep the link signed.
- Someone tired of the newsletter drops one topic, not you entirely
- Confirmation emails go out from a sender you verify
- Set the title, description, and copy; preview before publishing
- Unsubscribes land on the contact, so every future send respects them
A granular unsubscribe is the cheapest retention work available. The alternative is losing the whole address.
An open rate you can actually defend in a meeting.
Every broadcast gets a Sankey diagram tracing sent → delivered → opened → clicked, with clicks broken out per destination URL, and a funnel showing the conversion rate at each step.
Opens generated by security scanners and inbox prefetchers are filtered out of engagement metrics. The number that goes in the deck is lower than the vanity version and survives someone asking where it came from.
Click breakdown
Which link in the email did the work, not just whether somebody clicked something.
Subject line performance
Top performers sorted by engagement across sends, so the next subject line is an informed guess.
Event timeline
Search to one send and read every event it produced, in order — useful when one customer swears they never got it.
Three things you would find out in week two anyway.
Worth knowing now, while switching still costs you nothing.
There is no drag-and-drop email builder.
Templates are React Email components with a live preview beside them. In practice you start from the gallery or describe what you want to the AI panel — “a newsletter with three sections”, “add a hero image and a button” — and edit from there. Version history is on by default, so nothing you try is unrecoverable. But if a visual block editor is non-negotiable for your team, this will feel wrong.
There is no A/B testing.
Not in broadcasts, not in workflows. You can rank subject lines by engagement after the fact, and split an audience into even cohorts with a partition filter, but nothing automatically picks the winner. If your program runs on holdouts and lift measurement, this is a real gap today.
You cannot upload a CSV to a single send.
Recipients come from your contacts — everyone, a topic, or a segment. You can bulk-import a CSV into contacts, with column mapping and duplicate handling, then target it. But the one-off “here is a list, mail it” flow does not exist.
Unlimited contacts on every plan. Including the free one.
Broadcasts, segments, topics, and scheduling start at $19 a month. Sending is billed by AWS directly, at SES rates.