The One Thing I'd Change First in Your Signup Experience

Ask most people to review your signup experience and you'll get a list. Button color, headline, too many fields, no social proof, slow page, confusing pricing link. Twenty observations, all technically true.

A list like that feels thorough, but it rarely changes anything. Nobody fixes twenty things. The team picks the easiest three, the numbers don't move, and everyone concludes that "optimization doesn't work for us."

When I review a signup experience, my job is the opposite: find the one change most likely to matter, and be able to say why.

A composite example

This example is a composite built from patterns I see often — not a specific client or product.

Picture a B2B scheduling tool for small service businesses. The marketing site gets steady traffic. The signup form asks for name, email, password, company name, team size, and phone number. After signup, the user lands on an empty dashboard with a checklist: connect your calendar, set your availability, customize your booking page, invite your team.

The founder's worry is the form — "six fields is too many." It might be. But the form isn't where I'd start.

Step 1: Find the biggest drop, not the ugliest screen

I look at the numbers for each step before I look at design. In this composite, most visitors who start the form finish it. The steep drop is after signup: a large share of new accounts never connect a calendar, and without a connected calendar the product can't do anything.

That tells me the "signup experience" problem isn't really at the form. It's at the first step that requires the user to go get something — in this case, calendar permissions, possibly from an admin.

Step 2: Ask what the person is missing at that moment

At the calendar step, people commonly stall because:

• They aren't sure what the permission request will let the product do.
• They use a work calendar they don't control.
• They were just exploring, and connecting a calendar feels like a commitment.

Each of those has a different fix. The numbers tell me where; the reasons tell me what. If I can't tell which reason dominates, a short prompt asking stalled users "what stopped you?" usually answers it within days.

Step 3: Choose one change and define how you'll know

In this composite, suppose the dominant reason is the third one — people want to see it work before they commit. The one change I'd make first: let new users see a working booking page with sample availability before asking them to connect anything, then ask for the calendar connection as the step that makes it real.

And I'd define the measure before shipping: the share of new signups who connect a calendar within 48 hours, compared with the month before.

Why not fix the form too?

Maybe later. But in this composite, trimming form fields would polish the part of the journey that's already working, while the real drop-off stays untouched. One change aimed at the biggest drop teaches you more than five changes spread across the whole flow, because you can actually tell what worked.

The method, in short

1. Get step-by-step numbers before looking at design.
2. Find the single step where the most people stop.
3. Figure out what people are missing at that step.
4. Pick one change that addresses the main reason.
5. Decide the number that should move, and check it.

Want me to find yours?

That's the Growth Fix: one priority problem, one agreed improvement implemented with you, and one measurement plan. It's $997 and fixed in scope — built for B2B software and tech-enabled service businesses that already have signups and want more of them to become customers.

Get your one first fix →