← All work
Case Study 04 / 2026 · B2B SaaS · First-time dashboard

From one big button to three intent-based doors.

Instapage had a single, prominent "Create page" CTA on the trial-user dashboard — and almost nobody clicked it. Only ~2% of trial users took any meaningful action from the dashboard; the rest left the screen entirely and created pages from a different tab. The button wasn't the problem. The premise was: a single CTA asks users to commit before they're oriented. I led design end-to-end on a redesigned first-time dashboard with three intent-based entry points instead of one — a hero banner for users who knew what they wanted, filter chips for users who knew roughly what they wanted, and a pinned template grid for users who wanted to look first. Sessions with at least one action on the dashboard roughly doubled in 30 days post-launch.

RoleLead Product Designer
End-to-end
IndustryB2B SaaS
Instapage
TeamPM, core eng team,
analytics
DurationDiscovery → ship
(Phase 1)
Outcome~2× sessions
with a meaningful action
Note

Published with written permission from airSlate (May 2026). Customer screenshots, employee names, and any personally identifying information have been omitted under the terms of the permission.

Quick read · 30 seconds

The whole case, in six lines.

The problem

Only ~2% of trial users took a meaningful action from the dashboard. A single big "Create page" CTA was supposed to drive activation; almost nobody clicked it.

The diagnosis

Users weren't ignoring the button — they were leaving the dashboard entirely and creating pages from a different tab in the sidebar. Single-CTA fatigue.

The intervention

Three intent-based doors instead of one commitment point: a personalized hero banner, filter-led entry, and a pinned template grid with Blank Page always first.

The trade-off

Built bidirectional state sync between dropdown filters and quick-filter chips. Pinned Blank Page in position one. Deferred clear-all and applied-tag UI to the next phase.

The result

~2× the share of dashboard sessions with at least one meaningful action, in 30 days post-launch. Upstream funnel for trial-to-paid conversion improved alongside.

My role

Lead Product Designer, end-to-end: discovery, IA, interaction model, filter-state logic, hero / banner / grid hi-fi, analytics-event design with the PM.

At a glance
Activity lift
~2×
sessions with at least one meaningful action on the dashboard, post-launch vs baseline
Entry points
1 → 3
single CTA replaced with three intent-based doors
Measurement
30 days
post-launch window via internal events on dashboard interactions
Scope
First-time
view shown only when a trial user has zero pages; reverts to standard dashboard once content exists
01 · Context

The first screen a trial user saw — and didn't act on.

The first-time dashboard is a small but disproportionately important surface. It's the screen a trial user lands on right after signup — before they've created anything, before they've explored the editor, before they've made up their mind about the product. Whatever they do next on this screen is the strongest predictor of whether they'll convert to paid.

The version that existed when I picked up the project did one thing: it showed a single, prominent "Create page" CTA. Internally, this was the right answer to the wrong question. The right question wasn't "what action do we want them to take?" — it was "what action are they ready to take?"

The numbers showed the gap. Internal events placed the share of trial users who took a meaningful first action from the dashboard at around 2%. The PRD set a goal of ~10%, with a downstream target of lifting trial-to-paid conversion from ~2.5% toward ~3.5%. The dashboard was the lever — but only if it stopped asking trial users to commit before they were oriented.

Strategic frame

The dashboard wasn't underperforming because the CTA was weak. It was underperforming because it offered one path — and trial users in their first few minutes need optionality, not a forced choice.

02 · Diagnosis

Users weren't ignoring the button. They were walking around it.

The diagnosis came from looking at where users went instead. Pulling sidebar-click events alongside the dashboard-CTA-click events showed a pattern: users who landed on the dashboard frequently clicked into the Landing Pages tab in the sidebar — and created their first page from there. The dashboard was being treated as a way station, not a starting point. The CTA wasn't being ignored; the entire screen was being bypassed.

Three things were happening at once:

  • Single-CTA fatigue. A trial user 30 seconds into a product they've never seen does not feel ready to "create" anything. A button that asks them to commit feels premature. Users prefer to look around first.
  • The dashboard wasn't telling them what was possible. The button said "Create page" — but it didn't say what kinds of pages, what use cases, what would happen on the other side of the click. It was a leap of faith with no preview.
  • The Landing Pages tab won by accident. That tab had templates, filters, and a sense of place — it gave users somewhere to browse before they had to commit. The dashboard, comparatively, felt like a homepage with a single front door.
Insight

The dashboard's job wasn't to drive a click. It was to give trial users orientation — somewhere to look, narrow, and pick — and then make the click a natural consequence.

03 · Approach

Three intent-based doors, not one.

I framed the redesign around a simple idea: different trial users arrive with different levels of clarity. Some know exactly what they want to build. Some know roughly — they have a campaign type or industry in mind. Some don't know yet and need to see options before they pick. The dashboard had to serve all three without asking any of them to commit too early.

So instead of one CTA, three doors — each calibrated to a different level of intent.

Door 01 — high intent "I know what I want"

Hero banner with personalized greeting and Create Page CTA

For users who came in with a clear plan. A larger-than-before primary CTA in a banner that introduces the product, addresses the user by name, and goes straight to the template library on click.

Door 02 — medium intent "I know roughly"

Filter chips and dropdowns for use case, industry, and page type

For users who knew the kind of thing they wanted to build, but not the specific template. Five quick-filter chips for the most popular use cases, plus three multi-select dropdowns. Filters narrow the grid live.

Door 03 — low intent "Show me what's possible"

Pinned template grid, with Blank Page always in position one

For users who needed to see options before they could pick. The full template grid surfaced directly on the dashboard, four columns wide, with Blank Page protected in the first slot for users who genuinely wanted to start from scratch.

The three doors share one piece of state: the filter system. Pick a quick chip and the corresponding dropdown checkbox flips; uncheck the dropdown and the chip deactivates. This bidirectional sync is small but load-bearing — without it, the user notices an inconsistency the moment they cross between the two filter UIs, and the whole thing starts to feel broken.

Design principle

Match the UI to the user's level of clarity, not to the action you want them to take. A trial user who isn't sure yet doesn't need a louder button — they need a place to look.

04 · Design decisions

What I argued for — and what I argued against.

Four calls shaped Phase 1. The interesting ones, as usual, are the ones we cut.

What I pushed back on

  • "Make the button bigger." The button wasn't the problem; the premise was. Doubling button size in pixels would not move the metric.
  • "Hide Blank Page to push users to templates." That would have punished the small minority who legitimately wanted blank-canvas — and those users tend to convert well. We pinned Blank Page in slot one instead.
  • "Add applied-tags and clear-all to Phase 1." Both were nice-to-haves that would have stretched scope. We could measure the impact of the three doors first, layer those in once we knew the foundation worked.
  • "Show this dashboard to everyone, not just first-time users." A returning user with 12 pages doesn't need orientation. The new dashboard is gated to the zero-page state and quietly reverts once the user has content.

What shipped

  • Three doors — banner, filters, pinned template grid — each calibrated to a different intent level.
  • Bidirectional filter state sync between the dropdown filters and the quick-filter chips, with no duplicate selection allowed across the two UIs.
  • Personalized greeting in the hero. A small touch, but it makes the screen feel like a starting point rather than a generic landing pad.
  • Blank Page pinned in position one regardless of active filters — visible escape hatch for users who already know they don't want a template.
  • Conditional rendering: the redesigned dashboard appears only when the user has zero pages. Once they have content, the standard dashboard returns.
  • Granular event tracking on every door — banner clicks, filter opens, chip activations, template previews, template selects, sidebar exits — so we could read which door was doing the work.
Decision

Conditional rendering — showing the new dashboard only to zero-page users — was the unflashy call that made shipping painless. We didn't have to argue about the experience for power users; we never showed it to them.

05 · Shipped

The dashboard, redrawn.

Five pieces of the design are worth seeing — the hero banner, the filter bar with both UIs visible, the pinned template grid, the hover state on a template card, and the empty state. Image placeholders below; final images will be added once publication consent is in place.

Fig 01 — Image placeholder
dash-01-hero-banner.png
Hero banner with personalized greeting, value statement, and the larger primary CTA. Door one — high-intent.
Fig 01Hero banner — high-intent entry
Fig 02 — Image placeholder
dash-02-filter-bar.png
Three dropdowns (Use Case, Industry, Page Type) plus five quick-filter chips, with bidirectional state sync. Door two — medium-intent.
Fig 02Filter bar — medium-intent entry
Fig 03 — Image placeholder
dash-03-template-grid.png
Four-column template grid with Blank Page pinned in position one. Door three — low-intent / browse-first.
Fig 03Template grid — low-intent entry
Fig 04
dash-04-hover-state.png
Template card hover state surfaces Preview / Select actions; default state shows only the preview image.
Fig 04Hover state — preview / select
Fig 05
dash-05-empty-state.png
Empty state when no templates match active filters — with a hint to clear the most restrictive one.
Fig 05Empty state — when filters return nothing
06 · Outcome

Doubled in 30 days.

Phase 1 went out via a staged rollout with internal events tracking every door. The headline number — share of trial-user dashboard sessions with at least one meaningful action — roughly doubled in the 30 days post-launch.

Share of dashboard sessions with at least one meaningful action

Pre-launch baselinebaseline first-action rate from dashboard
~2%baseline
Post-launch (30 days)~2× the baseline rate
~4–5%~2× lift
PRD goallonger-horizon target
~10%full target
~2× lift in 30 days, on a metric — share of trial dashboard sessions with a meaningful action — that was deliberately strict (any single sidebar exit didn't count). The full PRD goal of ~10% is a longer-horizon target; Phase 1's job was to prove the three-doors thesis was correct before scaling investment.

Two things underneath the headline:

  • The doors got used differently. The hero CTA carried high-intent users; quick-filter chips carried medium-intent users (especially "Lead Generation" and "Webinar Signups"); the pinned template grid carried users who scrolled before clicking. None of the three doors dominated. That distribution itself was evidence the redesign was reading users correctly.
  • Sidebar exits dropped. Fewer trial users were leaving the dashboard to find page creation elsewhere. The dashboard had become the place to start, not just a place to pass through.
Headline result

~2× the share of trial-user dashboard sessions with at least one meaningful action, in 30 days post-launch. The dashboard stopped being a pass-through screen and started being a starting line.

07 · Reflections

What I'd do differently.

Three things I'd change next time.

  • Run a small prototype test before shipping the three-doors thesis. The hypothesis was strong and the analytics supported it, but a 30-minute moderated session with 5 trial users on a Figma prototype would have caught two minor copy issues we noticed only post-launch.
  • Surface the cost of inaction earlier in the PM/leadership conversation. "Only 2% take an action" lands harder than "the activation funnel needs work." Framing the existing baseline as a missed opportunity made the case for a redesign — but I should have done that on day one, not week three.
  • Design the second-time dashboard at the same time. We deliberately gated the new view to zero-page users, which was the right call for shipping speed. But the moment a trial user creates their first page, they get dropped back into the standard dashboard — which has its own issues. Phase 2 picks that up; in retrospect, sketching both states in parallel would have made the seam less abrupt.
Lesson

The most useful thing I did on this project wasn't the visual design. It was reframing the metric question — from "how do we get clicks on this button" to "what state are users in when they see this screen, and what do they need next." The button followed.

Continue reading