Doubling email activations by removing friction from follow-up automation.

Why this mattered to the business.

The product is a landing-page builder used by marketers to launch campaigns quickly. The built-in email module lets a published landing page automatically email leads the moment they submit a form — the natural next step in any campaign. Together, they form the four-step pattern customers buy the product for:

On paper, every landing page should have a follow-up email. In reality, almost none did. The product existed, customers paid for it, and the feature sat idle. It was a textbook activation problem: a strategically important feature with near-zero adoption.

Eleven actions, four friction points, and a lot of leaving and coming back.

I mapped the existing flow end-to-end. Users started in the form builder, hit an empty "Select email" dropdown with no path forward, navigated away to a separate email tool, created an email from scratch, manually flipped the "automated" status, activated, and then re-found their way back to the form they'd left. Four of those steps were friction points where users actively dropped out.

Four problems, four decisions.

The team had an instinct to "redesign the email builder." I pushed back. The email builder wasn't the problem; the bridge between form and email was. Rebuilding the email tool would have consumed the roadmap and wouldn't have moved the metric we cared about. I broke the user journey into four specific friction points and designed one decision against each.

The key trade-off

The biggest call: whether to treat follow-up email as a property of a form or as a first-class object with its own lifecycle. I argued for the first — at this stage of the product's maturity, the email doesn't need to exist without a form attached. Keeping the object model simple let us ship in weeks, not quarters, and we can split them apart later if the data supports it.

Old vs new flow, side by side

The new flow has eight actions, the old had eleven — a small numeric reduction. The real change is what was eliminated: the empty dropdown that stranded users, the cross-tool navigation that broke the form context, the hidden "automated" toggle users had to remember, and the manual journey back to re-find the form. Each of those was a place where users dropped out.

Connected across tabs, with automation already on.

The form settings panel now shows follow-up automation as an explicit, visible option, with a Create Email CTA where the dead-end dropdown used to be. Clicking the CTA opens a new tab directly in the email creation flow — the form tab stays open in the background. Users pick a template first, build the email, and activate. The key move: every template ships with automation pre-enabled. Users don't need to know that "Enable automation" is a required step, hunt for the toggle, or remember to flip it. When they come back to the form tab, the dropdown that was empty is now populated with the new email, ready to connect.

Activations doubled. We missed the 3× target — and that's a useful finding.

In the weeks after launch, automated email activations approximately doubled against the pre-launch baseline. Support tickets related to follow-up email setup stopped arriving in the volume we'd seen before.

We had targeted a 3× lift. We got ~2×. I don't spin this as a win-win. Here's what I actually took from it:

• The UX change was necessary but not sufficient. We removed friction — and the remaining gap suggests the email builder itself (the thing we decided not to redesign in this cycle) is now the next real constraint.
• Our hypothesis model over-indexed on friction. We assumed friction explained most of the gap. In reality, it explained about half. The other half is likely awareness at a different point in the journey.
• "5% of savers" was probably the wrong benchmark. Not because users don't want follow-up email — but because of who reaches form-saved state. A non-trivial portion are exploring, not launching.