Skip to the case study

[Product design][SaaS][Email automation]

The email that only sends when there’s something new

A screen-by-screen critique of the 2022 recurring emails design at FunnelKit, and my redesign that answers each moment.

Company
FunnelKit
Role
Product Designer
Original design
2022, by another designer
At FunnelKit
Until 2025
The redesigned setup page for a recurring email, with the real next email previewed beside it

Why this mattered

Store owners kept asking for the same thing

Send my newest products and posts to my subscribers every week, without building a new email each time.

Over six months, about 150 requests reached support.

The workaround? Support switched scheduling on by hand, store by store.

The 2022 design could do the job. But it asked a lot of the people it was built for.

Recurring emails were first designed in 2022, by another designer. This case study is my redesign of that flow.

It goes through the 2022 screens one moment at a time, asks what each one asked of the store owner, then shows how the redesign answers it.

A recurring email is a promise: every one of them has something new in it.

That sentence became the test for every screen. There are three ways to break it:

  • Sending an empty emailNothing new was published, and the email goes out anyway.
  • Repeating last weekThe same products show up two sends in a row.
  • Calling a restock “new”An old product comes back in stock and is presented as new.

The 2022 design could keep the promise, but it hid how. The redesign makes it visible.

Who it’s for

Two people shaped the decisions

Both are composites, built from conversations with customers and the support team.

Meera

Runs a small ceramics store. Her first recurring email.

Wants new pieces and posts to go out on their own, so she can stay in the studio.

Worries about sending something empty or wrong to customers who trust her.

Daniel

A marketer running emails for several stores.

Wants control: segments, exclusions, resends, and a clear reason when something goes wrong.

Worries about automation he can’t check or explain to a client.

Walkthrough 1

The 2022 design, moment by moment

This is where I started: a list of recurring broadcasts and a five-step wizard, designed in 2022.

Step through it the way Meera would meet it. Each moment is lit up on the screen, with what she’s likely thinking beside it.

2022 design: list of recurring email broadcasts with five status tabs

01 / 14 · Recurring broadcasts list

Five tabs for something that is either running or not.

“Is ‘Ongoing’ different from ‘Scheduled’? Which one is mine?”

Mental model mismatch

The redesign keeps the builder owners already know, and rebuilds everything around it.

Walkthrough 2

My redesign, moment by moment

Each moment answers one from the 2022 design.

  • One setup pageThree short steps instead of a five-step wizard.
  • The real next emailThe builder shows this week’s actual products, not placeholders.
  • An honest overviewEvery send is sent, skipped or late, and says why.
Redesigned list of recurring emails with next send contents and an on/off switch

01 / 26 · Recurring emails list

The next send says what is in it, not only when: “4 items ready”, or “Nothing new yet · skips if still empty”.

“So Monday’s email won’t be empty. Good.”

Visibility of system status

Try it yourself

The redesign, working

A working prototype with sample data from a made-up ceramics store. Click anywhere; nothing is sent.

  1. 01Set up a new recurring email
  2. 02Leave one product out of Monday’s send
  3. 03Find out why the 1 October email went out late
FunnelKit · Recurring emails (prototype with sample data)

The Screens button inside jumps to any state. Open it in a new tab

The prototype is built for a laptop screen. Open it anyway

Takeaways

Four things I’d carry into any automation

01The rule that decides everything was fine print

The most important rule on the page had the least important styling.

In the 2022 design, a recurring email only ran if its template had a Post block. The design said so in a grey bar under the editor:

Please make sure you have added post or product block in your email template. Otherwise this broadcast will not run

People don’t read warnings while they’re getting something done. They follow the path the interface leaves open.

So the redesign turns the warning into a constraint:

  • Only templates that work are offeredThe template picker hides any template without the Latest items block.
  • A blank email is never emptyStarting from scratch adds the block for you.

02Show the email, not the settings

Trust comes from seeing the outcome, not reading a summary of inputs.

The 2022 review step listed every setting as text.

The template could be previewed, but no screen tied a send date to the items it would carry.

Places that show a specific upcoming send with its actual items
20220
Redesign4

Counted from the designed screens. In the redesign: the setup preview, the email builder, each send’s overview, and the test email.

The redesign shows the real next email wherever a decision is made.

03Defaults should come from the store, not from us

A blank field makes every owner do the same research.

  • Suggested daysFrom how often the store actually publishes.
  • All subscribers, preselectedSo new subscribers join automatically.
  • Preview text that writes itselfFrom the items in each send, so it never promises something that isn’t there.

A beginner can turn on a first email in seven clicks, with no typing.

Counted in the prototype: Continue, Choose a template, Use template, Save and return, Continue, Save and finish, Turn it on.

04Label states the way the owner would say them

Status words are where trust is won or lost.

A send that went out two hours late is not a failure.

A recurring email that will run again is not complete.

Situation2022 designRedesign
A recurring email that will run againIn-Progress, or CompletedActive
Turned off by the ownerPaused, or CancelledPaused
The provider’s daily limit stops a sendFailed, with Try againSent late: retried automatically, cause named
Nothing new to sendNo state designedSkipped · nothing new, and the owner is told
Just turned on, nothing sent yetNo state designedNo sends yet

What testing changed

Two simulated users, eight changes

I tested the first version with two simulated users: AI agents briefed to act as Meera and Daniel, working through set tasks and thinking aloud.

They’re no substitute for real participants. But they were quick and specific about where the design made them stop.

  1. Right after turning it on, the overview showed past sends. “Did I already email people?”

    Day one says “No sends yet”.

  2. Restocked products were counted as new.

    Restocks are an opt-in choice, off by default.

  3. No way to pick or build a segment.

    A segment picker, plus a builder with rules or hand-picked contacts.

  4. Edit opened a second “new” setup labelled Draft.

    Settings is a tab on the email’s own page.

  5. An excluded product still showed in the previews.

    Exclusions apply per send, show everywhere, and can be undone.

  6. “Failed” on a send that went out late.

    “Sent late”, with the cause named.

  7. Fixed preview text didn’t match the items.

    Preview text is written from each send’s items.

  8. “Post block” and “Audit” meant nothing to Meera.

    “Latest items block” and “Checks”.

What’s still weak

Where I’d go next

  • Send pacingDaniel asked for throttling and send-time optimisation. Neither is designed yet.
  • One category at a timeA store with overlapping collections can’t combine them.
  • Setup still has three stepsA Phase 2 idea fills the setup from one sentence. It needs engineering planned for after the AI work.
  • Real participantsThe next round should be with real store owners, on their own stores’ data.

Every problem in the first walkthrough came from one place: the design described the system’s settings, not the owner’s promise.

Reflection

Describe the promise, not the settings

The 2022 wizard wasn’t wrong step by step. Each screen did what it was asked to do.

Once the promise became the test, most decisions made themselves.

Your turn

A store publishes twelve new products on Sunday night, and the email shows four.

What should happen to the other eight: wait for Thursday, go out in a bigger email, or something else? What would you show the owner so she trusts the answer?