Mobile Email Editor

Express Send was a workaround that the team had shipped as a stopgap. Users opened a pre-built email, tweaked content, picked recipients, and hit send. The send numbers went up and the team considered it a win.

I challenged that conclusion. Those send numbers had no qualitative backing. Express Send was masking the capability gap, and users were forming a false impression of what the product could do.

Activated users converted to paid at significantly higher rates. The quality of the first real send was the highest-leverage opportunity on mobile. Users needed to trust that they could create an email themselves.

Challenging an existing solution required evidence. I built the case with three layers: a qualitative gap in the existing data, user research I'd conducted 18 months earlier on the native app, and a competitive audit showing no one in the market had solved mobile email creation well. Together they justified the investment.

• Qualitative Gap Audit: Express Send had been approved on send volume alone. No qualitative signal existed on what users were actually experiencing. That absence was itself evidence.
• My Prior Native App Research: 18 months earlier I'd designed and tested a full mobile editing pattern for the native app. It was deprioritized, but 10 out of 10 participants wanted a capable mobile editor. That signal held.
• Competitive Analysis: I audited direct and indirect competitors' mobile email creation experiences. Nobody had solved dexterity on small screens well. The problem was unsolved across the industry.
• Defining the bar: An experience that gave users real confidence they could create and send. Good enough to change behavior and set accurate expectations.

I'd originally designed this three-state model for the native app 18 months earlier. It was deprioritized for scope, but the research signal held. I adapted it for mobile web in two weeks, with strong engineering partnership on the implementation.

The editor needed a complete flow around it. For the activation path to work end to end, users needed a clear way to go from editing to sending. I designed the full flow: a landing page that surfaces drafts and prompts the next action, a save-draft confirmation that preserves work on exit, and a scheduling screen supporting send-now, send-tomorrow, and custom date/time selection.

Every surface was designed to reduce the number of decisions between "I want to change something" and "it's sent." Fewer steps between editing and sending means more users complete the loop and come back to send again.

Previously, opening the editor automatically created an email behind the scenes. Every tap counted as a creation, regardless of intent. We changed that. Now the editor only counts a creation when a user makes an edit and saves a draft. Backing out without changes leaves no trace. This distinction is what makes the flat creation rate in the results meaningful: every creation in the test group represents a real decision to start a campaign.

Would quality drive conversion, or just presence?

The hardest part of this project was making the case that a solution the team had already shipped and celebrated was producing misleading signal. The research gave us the evidence to have that conversation productively.

The results confirmed that quality drove conversion. Users who could create a real email came back to send again. The editor turned tentative first attempts into confident, repeatable sends and created a more efficient path to payment.

The system is currently in the patent process. It continues to evolve as the foundation for all mobile web email editing at Constant Contact.