Case Study · Product Design

Invoices Null
State Redesign

Using research insights and product instincts to increase the invoices null state CTR by ~20%

Company Square
Role Lead Designer
Invoices null state redesign

The invoices funnel was leaking

The Invoices funnel had a 55% drop-off rate from high-intent sellers landing on the product page to sending their first invoice. While there were a number of probable factors likely contributing to this, the team identified the current invoices null state as a clear opportunity to address the drop-off. In its current state, rather than offering guidance or context, the dashboard simply showed empty data, giving sellers no information to orient themselves or clear actions to take next.

Previous Invoices null state showing an empty dashboard

We saw an opportunity: if we replaced the empty dashboard with contextual content about the product and its benefits, more sellers would take the next step. But the page needed to work for two very different audiences. Sellers who signed up specifically for Invoices needed a clearer path to action, while sellers casually exploring Square needed context on why Invoices would help their business. Additionally, we had limited objective data on what kind of content would most likely incentivize them to take action.

Understanding the landscape

To better understand the null state landscape in terms of both messaging and structure, we audited pages across four competitors (Zoho, Mailchimp, Freshbooks, and Honeybook) as well as several internal Square product pages. Three structural patterns emerged, each with a distinct tradeoff between user control and information density.

Product null state design patterns

Pop-up overlay

An informational guide overlays the product page to walk users through key features, without changing the underlying layout.

Pros
  • Sequences information without requiring layout changes to the actual product page
  • Dismissible, so users that don't need the info can skip immediately to get started
Cons
  • High dismiss risk and the content is not discoverable for users to return to later
  • People hate pop-ups

Honeybook

Honeybook pop-up overlay example

Honeybook

Honeybook pop-up overlay example

Temporary setup page

A dedicated setup page surfaces in the nav and guides users through key actions. Once setup is complete, the page disappears.

Pros
  • Persistent during setup without disrupting the main product
  • Users can return to it as needed
Cons
  • Easy to skip entirely during onboarding
  • Disappears before some users are ready

Mailchimp

Mailchimp temporary setup page example

Zoho

Zoho temporary setup page example
✓ Chosen direction

Dynamic null state

The product page itself adapts, surfacing CTAs, educational content, and feature context that evolves as the user engages. Once used, the page shifts toward the standard product view.

Pros
  • Speaks to both new and nearly-active users
  • Lets marketing, education, and product content coexist
Cons
  • More complex to design and test the evolution logic
  • Can feel disorienting if transitions are not handled well

Mailchimp

Mailchimp dynamic null state example

Mailchimp

Mailchimp dynamic null state example

Ultimately, we felt that despite its higher design overhead, the dynamic null state would let us create a more broadly relevant page, one that could adapt based on what we know about sellers and the actions they take in the product.

Content section mapping

Before jumping into design, we mapped how Zoho, Mailchimp, and Square Marketing each structured their content sections. This helped us identify which modules (primary CTAs, product features, educational content) were common across implementations and gave us a shared vocabulary heading into the brainstorm.

Cross-functional brainstorm

With the evolving page direction decided, we ran a cross-functional session with engineering, product, marketing, and design to align on content strategy. Three questions framed the conversation: how do we help get sellers started, what key information should sellers know about the product in their first few days, and what benefits does the product offer?

Two different content strategies

Coming out of the brainstorm, we aligned on two potential paths forward: one focused on explaining the benefits to new users, and the other focused on helping high-intent sellers get started quickly. Each implied different content priorities. The marketing-led approach would lead with high-level product value, while the set-up-led approach would prioritize showing first actions to get started.

Both variants used a simple, modular design system built from interchangeable content blocks. This meant future testing, audience-specific customization, and optimization could happen through content swaps rather than structural redesigns, giving us a scalable foundation without additional engineering investment.

A dynamic page to guide sellers

The dynamic null state adapts as sellers engage. Each variant opens with a different content strategy, but both follow the same progression, shifting from an introductory layout to an action-oriented view after the first send, then settling into the standard product experience.

Marketing-led

Marketing-led initial state First-use state Active state

Set-up-led

Set-up-led initial state First-use state Active state
Initial state First-use Active

Impact

~20% CTR lift (marketing-led variant)
11% CTR lift (set-up-led variant)
4x Expected lift

Both variants exceeded our 5% target, with the marketing-led page delivering roughly 4x the expected lift. The results confirmed that grounding design decisions in competitive research and cross-functional alignment leads to high-confidence hypotheses. The A/B test measured magnitude, not direction.

Beyond the immediate metrics, the modular content block system we built means the team can now run future tests, targeting different audiences, adjusting messaging, or swapping content, through simple configuration changes rather than structural redesigns.