The editor doesn't impose a layout grid or add padding to every block. Our monthly studio note uses a serif headline, one column, and margins I set on purpose; on the previous platform spacing values were forced, and the result read like a template no matter what we uploaded. Here the newsletter matches our site, which is the entire point of having a brand at all.

The harder test was a handoff. We built a site for a non-profit literacy group, and their volunteer coordinator — she's in her seventies, sends one update a month, has never opened a CMS — learned this in a single sitting. Eight months on, nobody has emailed the studio asking how to send the newsletter. For an agency, that silence is the deliverable: a tool a client can genuinely operate is the difference between a clean handover and an unpaid support line that runs for years.

RSS earns its keep quietly. Case studies publish to the blog and go out to subscribers without anyone remembering, which matters in a studio where marketing gets whatever attention remains after client work.

What it refuses to include: real segmentation, branching automations, A/B testing worth the name. Were we running lifecycle campaigns for a retailer, this would be the wrong tool. For a list of a few hundred and a charity's donor updates, those features would be decoration.

One more thing, as the person who signs off on tools: the cost is knowable. No per-contact creep as a list grows slowly over years. Review collected by and hosted on G2.com.

There's a spreadsheet called segments_master.xlsx. The tool organizes contacts by list, not by the attributes we actually care about — prospect, peer studio, recruiter, vendor — so each quarter I export everything, sort by hand, and re-import three groups. Ninety minutes, and it produces duplicates roughly every time, which then need deleting individually.

There's a folder of headline images. Our brand uses a licensed typeface unavailable in the editor, and the font stack can't be extended, so the big serif line atop every newsletter is a PNG. I know precisely what that costs: text inside images doesn't scale, doesn't translate, and reads badly to a screen reader. We add alt text and accept the compromise, because the alternative is a mismatched wordmark twelve times a year.

There's a bounce list I maintain manually. After importing a partner's list in the spring, about forty addresses hard-bounced, and the reporting gave me a count rather than a file. I had to ask the partner to re-clean their source because I couldn't extract which records failed.

And there's an uncomfortable conversation I keep postponing: the volunteer coordinator at the literacy charity holds full administrative rights. No roles, no read-only access, no approval step. She would never deliberately break anything, but one mis-click on a donor list isn't recoverable by undo. For now the mitigation is that I keep the export.

Automation is the final gap. A welcome sequence works, but it cannot branch on whether someone clicked the donate link — precisely the distinction a charity cares about.

None of this is hidden; the product is honest about being small. But "simple" and "safe for someone else to operate" aren't the same thing, and the difference lives in that pile. Review collected by and hosted on G2.com.