Feature reference

Every part of the studio, described plainly.

Below: each feature, what it actually does, where it pays off, and which plans carry it. The examples are live — the demo studio behind them runs the same code paths.

The block editor

Campaigns are stacks of blocks — headings, paragraphs, buttons, dividers — added in the order you mean them and edited in place. No canvas wrestling, no HTML islands: the letter reads like a letter, and a campaign needs only a subject and one block before it can send.

Where it pays off

A Sunday note: one heading, two paragraphs, a button to the new arrivals. Three minutes, done properly.

Why it matters: Writing goes fast because the format never gets in the way.

Available on every plan, including Sapling.
Interactive example
Editor playground

This strip mirrors the studio editor's gestures — same edit-in-place, reorder, and delete.

Previews that behave like inboxes

Open the preview and your campaign renders in a reading frame — desktop-width or phone-width, subject and preheader on top. What you check is precisely what arrives; the editor validates alongside so a missing subject never slips to the queue.

Where it pays off

Check the mobile frame before the Sunday send: the heading fits, the button sits in a thumb's reach.

Why it matters: Embarrassing layouts die in the preview instead of in 2,000 inboxes.

Desktop and mobile previews on every plan.
Interactive example
Editor playground

This strip mirrors the studio editor's gestures — same edit-in-place, reorder, and delete.

Segments you can trust

Segments are honest filters: tag rules (VIP, trial, wholesale), status subscribed or unsubscribed, and location — combined with and/or and shown with a live match count as you build. Send to a segment and you know exactly who's receiving it.

Where it pays off

VIPs get early restock access; the sleepy get a win-back — the count flickers to the truth as rules stack.

Why it matters: Targeting stops being guesswork; the recipient list is visible before the send.

Basic segments everywhere; behavior-based rules from Garden.
Interactive example

2 of 6 sample subscribers match.

  • lisbon
  • cork

The studio's segment builder shows the same live count — before any send.

Sending with receipts

Pressing send walks the recipient list: each subscriber passes queued → delivered, with a few honest bounces (bad address, full mailbox) flagged with reasons. You watch progress on the send sheet, then the campaign files itself in Reports with the full log.

Where it pays off

The Sunday letter goes to 46 people at 09:00 — by 09:02 the sheet shows 44 delivered and two bounces with reasons.

Why it matters: No more send-and-pray: every recipient has a receipt, every bounce a reason.

The delivery log arrives on Sapling; a dedicated IP is Estate's business.
Interactive example

Read the letter and pressed the button — receipts keep the story straight.

The studio report carries one row per recipient — opened/clicked included.

Reporting that answers questions

Each campaign's report opens with the shape of the send — delivered, opens, clicks, bounces as clean bars — plus the per-recipient log. A workspace overview compares campaigns side by side so subject line habits become visible patterns rather than anecdotes.

Where it pays off

Comparing three subject styles over a month, then keeping the voice that actually gets opened.

Why it matters: Decisions get evidence; the letter keeps improving on purpose.

Per-campaign reports everywhere; CSV export from Garden.
Interactive example

Read the letter and pressed the button — receipts keep the story straight.

The studio report carries one row per recipient — opened/clicked included.