Test your website →

Blog

Why Your Signup Form Loses People at Field Three

Every field in a signup form is a renegotiation of the visitor's consent, and most forms lose the negotiation by asking for things they don't need yet.

A signup form looks like a single obstacle. It isn’t. It’s a series of small obstacles, one per field, and the visitor renegotiates their decision to continue at each one. This is the thing form designers most often miss. They think the visitor decided to sign up when they clicked the button, and the form is just the paperwork. But the decision isn’t finished. Every field reopens it.

The first field is almost free. Usually it’s email, and the visitor came prepared to give an email; it’s the understood price of admission on the internet. The second field costs a little more — a name, maybe a password — but it’s still within the expected transaction. It’s around the third field that something shifts. The visitor came prepared for a quick exchange, the form is revealing itself to be longer than that, and now they’re doing arithmetic they weren’t doing before: how much more of this is there, and is the thing on the other side worth it? Whatever field happens to sit in that slot inherits the blame, but the real problem is cumulative. Field three is where the form’s true length becomes undeniable.

What makes this worse is that fields don’t just cost effort. They leak information about your intentions. A phone number field says, plainly, someone intends to call you. A company-size dropdown says you’re being scored for a sales pipeline. A “How did you hear about us?” field says this form serves the marketing department, not me. Visitors read these signals fluently, because they’ve been burned before. The effort of typing a phone number is ten seconds; the anticipated cost of having given it is weeks of calls. When someone abandons your form at the phone field, they’re not lazy. They’re pattern-matching correctly on what that field predicts.

The uncomfortable question, then, is why the extra fields are there at all. Almost always the answer is that they’re for you, not for the user. The product needs an email and a password to create an account; everything else is someone downstream wanting data. Sales wants the phone number. Marketing wants attribution. Analytics wants the job title. Each request sounds cheap — “it’s just one more field” — because the person asking never sees the people who leave. The abandoned form is invisible in a way the missing data isn’t. So forms grow the way committees grow, one reasonable addition at a time, until the signup page is a customs declaration.

The principle that cuts through this is simple: ask for the minimum needed to deliver the next thing the user wants, and nothing else. Not the minimum your CRM wants. The minimum the next step requires. When I built the entry point for GazeSite, my website-audit tool, the free scan needs exactly one input — a URL — because that’s all a scan requires. Email comes up only at the point where there’s a report worth sending somewhere. That ordering wasn’t cleverness; it fell out of asking, at each step, what do I actually need to hold up my end right now? Everything the flow doesn’t need yet, it doesn’t ask yet.

“Yet” is the operative word, because the deferred fields aren’t lost. A user who has signed up and gotten value is a different negotiating partner than a stranger mid-form. Ask for the company size after they’ve seen the product work and the question feels like configuration. Ask before, and it feels like an interrogation to enter a building they’re not sure they want to be in. The data arrives either way. The difference is whether the person is still there.

There are honest exceptions. If the product genuinely can’t function without the information — shipping needs an address, payments need a card — then asking isn’t friction, it’s the transaction, and users accept it without complaint. People will fill out long forms when every field is self-evidently necessary. What they resent is fields whose necessity they can’t see, and they’re right to, because those fields usually aren’t necessary. The resentment is accurate.

So audit your own form the way a skeptic would. Read each field and say out loud what it’s for and who it’s for. “Email — to send the login link — for the user.” Fine. “Phone — so sales can follow up — for us.” That one’s costing you signups, and you should at least know the price. Then try the harder exercise: delete every field that isn’t needed for the very next step, and find a later, better moment for each one. Your form will shrink to two or three fields, your signups will stop dying at field three, and the strange thing is you’ll likely end up with more of the data, not less, because you’ll have more users to ask.

More articles

← All posts