An illustrative story. The people in it are made up. Every Rowsend feature they use is real and quoted alongside.
It is a quiet Tuesday and Dana is looking at her user table. Quite a few people signed up in the spring, used the app for a few weeks and then stopped coming back. She has shipped two features since then that they never saw.
She opens Rowsend on her Mac. Her database is already connected through the read-only login the setup SQL created, so her users are there as her audience. She builds a segment from her own columns: people on the free plan whose last sign-in is older than a couple of months. The count looks about right, a few hundred people.
In the editor she starts from her saved template, so the logo, colours and button style are already in place. She writes a short note about the two new features, adds one button that goes to the login page, and keeps it plain.
This email goes under a product updates topic. If someone does not want updates anymore, they can leave that topic and still get her monthly newsletter. Every email also carries the one-click unsubscribe header Gmail and Yahoo ask for, so she does not have to set that up herself.
She sends herself a test, reads it on her phone, and fixes a typo. Then she schedules it for Wednesday morning and leaves it.
Wednesday goes fine for most of the list. A handful of old addresses bounce, which is normal for people who signed up months ago. Rowsend leaves those addresses out of every later send. Had the bounces kept climbing, the campaign would have paused itself so she could look at the audience.
On Thursday she opens the campaign report: deliveries, bounces, unsubscribes and complaints. There are no open or click numbers, because Rowsend adds no tracking pixels. She checks her own app instead and sees a few of those quiet accounts signing in again. The sending itself went through her SES account at SES prices.