← All work
Case Study 01 / 2025–2026 · B2B SaaS · Follow-up automation

Doubling activations by removing friction from a follow-up automation flow.

Users on marketing teams rarely set up follow-up emails — not by choice. The flow stranded them in an empty dropdown, sent them off to a separate email tool, and left them to find their way back. I rebuilt it as one connected workflow: a clear entry point, a new tab that opens straight into email creation, and templates with automation already on. Activations doubled in the first weeks after launch.

RoleLead Product Designer
owned end-to-end
TeamPM, 3 engineers,
analytics, support
DurationNov 2025 — Jan 2026
~3 months
Outcome2× activated
follow-up emails
Note

Published with written permission from airSlate (May 2026). Employee names and identifying details are withheld; product UI is captured on demo pages, with no customer data shown.

Quick read · 30 seconds

The whole case, in four lines.

Problem

Marketers wanted their pages to follow up with leads, and couldn't get it working. We measured 10 activations across 6,305 users — plus 7 tickets asking how.

Diagnosis

Not disinterest — a dead end. The form builder showed an empty dropdown and no way forward.

Design

Build the bridge, not the tool. A CTA where the dead end was, a new tab that keeps the form open, templates with automation already on.

Result

2× activations. We aimed for 3×. The gap showed us where the next constraint sits.

01 · At a glance
Activation lift accounts switching on follow-up automation
Friction removed 4 → 0 dead end, context switch, hidden toggle, manual return
Target vs. actual 3× / 2× short of the PRD target — and that is the finding
Shipped Jan 2026 connected flow across two products
02 · Context

What customers were actually buying.

Instapage is a landing-page builder for marketing teams. Its built-in email module can reply to a lead the second they submit a form — the last step of the pattern the product is sold on.

Four-step marketing pattern: create a form, add it to a landing page, collect leads through form submissions, engage them with an automated follow-up email — step four highlighted as the focus of this case study
Fig. 01 Steps 1–3 worked. Step 4 almost never got switched on.
03 · The dead end

The interface asked for something it never let you make.

Open a form's settings, expand Email automation, and you meet a dropdown asking you to select an email. If you have never built one, the list is empty. No button, no hint that the thing it wants lives in a different product. Just a list with nothing in it.

Fig. 02 The old form editor. Email automation exists, expects a pre-built email, and offers no way to make one.

Ten accounts out of 6,305 switched it on across a two-week window. Seven more wrote to support asking how.

Activation funnel for 21 October to 6 November 2025: 6,305 total active users, 424 saved a form, 122 added a form to a landing page, and 10 activated email automation — the bottleneck
Fig. 03 The funnel, 21 Oct – 6 Nov 2025. Internal analytics, cross-checked against session recordings and tickets.
Takeaway

Low adoption wasn't a preference. It was a blind spot in the interface.

04 · The detour

Eleven actions across two products.

I mapped what it took to get one follow-up email running: leave the form, find a separate email tool, write an email from scratch, flip on an "automated" status nobody mentioned was required, then find your way back. Four of those steps were places people quit.

Diagram of the old eleven-action follow-up automation flow with four friction points marked: the empty dropdown dead end, the context switch to the email tool, the hidden automation toggle, and the long manual return path
Fig. 04 The old flow. Red marks where people dropped out or backtracked.
Team brainstorm artefact mapping where users dropped off, what session recordings showed, and what support tickets corroborated
Fig. 05 Session recordings, support tickets and funnel data all landed on the same four points.
Takeaway

The cost wasn't any single step. It was being asked to become an email author halfway through building a form.

05 · The design call

The team wanted to rebuild the email builder. I argued for the bridge.

Rebuilding the email tool would have eaten the roadmap and left the same gap between the two products. The builder wasn't what stopped people — the crossing was.

I kept the object model simple too: a follow-up email doesn't need to exist without a form attached yet. That let us ship in weeks, and split them apart later if the data asks.

If we make follow-up automation visible, guided, and auto-enabled right where a form is built, activations will rise 3×.

0.11%Baseline activation, 21 Oct – 6 Nov 2025
0.5%PRD target — a 3× lift
5%The assumption we pressed on: how many form-savers our email product was good enough for
06 · Four decisions

One decision against each drop-out point.

01 · Dead end

An empty "Select email" dropdown. No CTA, no path forward.

A Create Email CTA in exactly the place the dead end used to be.

02 · Context switch

Leave the form builder for a separate email tool, losing the campaign you were building.

A new tab opening straight into email creation — the form tab stays where it was.

03 · Hidden requirement

Only automated emails can connect to forms — and nothing said so.

Templates ship with automation already on. The constraint stays on our side of the glass.

04 · The way back

"Where was that form again?" — a manual hunt back to connect the email.

One tab click. The dropdown that was empty is now populated and ready to connect.

Side-by-side comparison of the old eleven-step flow with four friction markers and the new eight-step flow with none
Fig. 06 Same start, same finish, four friction points gone in between.
07 · What shipped

Connected across tabs, with automation already on.

Fig. 07

A door where the wall was

Email automation now explains itself and offers one action, in the panel the user is already in.

The shipped form settings panel: an Email automation section headed add follow-up email after contact submits the form, a short explanation, and a Create Email button
Fig. 08

Every template arrives already automated — we do that step for the user

Only emails carrying the "automated" status can connect to a form. Users used to have to know that, find the toggle, and switch it on themselves. Now the template ships that way, and the requirement never surfaces.

The select layout template screen: a grid of starter email templates for different fictional brands, with create with AI and build with HTML as alternative starting points
Fig. 09

The dropdown fills itself

One tab click back, and the list that was empty now holds the email just built — already automated, ready to connect.

The same form settings panel after returning from the email tab: the Email automation dropdown is open and now offers the newly created automated email alongside None
Fig. 10 The whole crossing, end to end: form → new tab → email → back → connected.

Shipped UI, captured on demo pages — no customer data shown.

Takeaway

The best fix for a hidden requirement is to stop requiring the user to know it.

08 · Outcome

Activations doubled. We wanted 3×.

Activations roughly doubled in the weeks after launch, and the support tickets about setting up follow-up email stopped arriving. About 4.7% of form-savers activated — close to the 5% ceiling we had assumed.

Activation rate compared across three bars: 0.11% pre-launch baseline, approximately 0.22% post-launch actual, and a 0.33% PRD target that was missed
Fig. 11 Pre-launch, post-launch, and the target we set. Honest read: we closed about half the gap.

Three things came out of the shortfall:

  • Friction explained about half the problem. Removing it was necessary, not sufficient — the email builder we chose not to touch is the next real constraint.
  • "5% of savers" was the wrong denominator. A meaningful share of people who save a form are exploring the product, not launching a campaign.
  • Awareness lives elsewhere too. The form settings panel is one moment in the journey. It isn't the only one worth intercepting.
09 · Reflections

What I'd do differently.

I'd talk to the people who quit. Recordings and tickets carried the diagnosis, and they were enough to ship on. But five interviews with real drop-outs would have surfaced the awareness gap before launch, not after.

More work