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.
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.
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.
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.
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.
~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.
Lead Product Designer, end-to-end: discovery, IA, interaction model, filter-state logic, hero / banner / grid hi-fi, analytics-event design with the PM.
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.
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.
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:
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.
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.
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.
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.
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.
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.
Four calls shaped Phase 1. The interesting ones, as usual, are the ones we cut.
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.
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.
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.
Two things underneath the headline:
~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.
Three things I'd change next time.
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.