Your Signup Form Is Killing Conversions: The Exact Number of Fields You Actually Need

By Jonathan · Founder, PageGains

Every field you add to your signup form feels justified when you're building it. Sales wants the company size. Marketing wants the job title. Product wants the use case. But the person on the other side of that form? They wanted to try your software, and now they're staring at eleven questions they didn't expect to answer. A chunk of them just closed the tab.

The Research Is Clear: More Fields = Fewer Signups

Unbounce analyzed over 40,000 landing pages and found that reducing form fields from eleven to four increased conversions by 120%. Expedia famously killed one field — "Company name" — and made an extra $12 million a year. These aren't edge cases. They're what happens when you stop treating your signup form like an intake questionnaire.

The uncomfortable truth is that most of the fields on your form exist for internal reasons, not customer reasons. You want the data. Your prospect wants access to the product. Those two goals are in direct conflict, and right now your form is picking a side — and it's not theirs.

Here's the rule: ask for the minimum information you need to create an account and deliver value. Everything else is a tax on the people trying to sign up.

The Magic Number Is Three (Sometimes Four)

For most SaaS products, the optimal signup form has three fields: email, password, and — if your product genuinely requires it — a first name for personalization. That's it.

Some products legitimately need a fourth field. If you're B2B and billing is seat-based, a company name makes sense. If onboarding is meaningfully different by role, a single "What best describes you?" dropdown can earn its place. But notice the standard: the field has to change what you do next. If you're collecting job title but your onboarding flow is identical for everyone, that field is deadweight.

Tools like Slack and Notion built their early user bases on two-field signups — email and password, sometimes just email. They figured out who the user was inside the product, through behavior, not interrogation. That's the model worth copying.

"But We Need That Data for Segmentation"

This is the most common pushback, and it's worth taking seriously. Yes, you need segmentation data. No, the signup form is not the right place to collect it.

Here's the better approach: collect it progressively. Let the user in with minimal friction, then ask one question at a time during onboarding, triggered by where they are in the product. Intercom does this well — they ask about your use case inside the product after you've already created an account, when you're already invested in figuring it out. Response rates for in-app questions are higher than signup form completion rates, and the answers are more accurate because users understand the product better at that point.

Typeform built its entire onboarding around progressive questions, and their completion rates on onboarding surveys run well above industry average. The lesson: people will tell you a lot — just not all at once, and not as the price of admission.

Phone Number Fields Are Conversion Killers (Unless You Have a Good Reason)

Adding a phone number field drops form conversions dramatically — studies consistently show 5–10% drops per unexpected field, and phone numbers trigger the biggest anxiety spike. People immediately wonder if they're going to get cold-called, and that fear overrides everything else.

The only time a phone number belongs on a signup form is if your product genuinely requires it for verification (two-factor auth) or if you're selling enterprise deals where a call is part of the sale. Even then, consider making it optional and explaining exactly why you need it. "We'll text you a verification code" is a reason. "So our team can reach you" is a warning label.

If your sales team is pushing for phone numbers on the signup form because they want to call leads faster — that's a valid sales goal, but the signup form is the wrong place to solve it. Use intent signals, firmographic enrichment tools like Clearbit, or a separate "Talk to sales" path for high-intent visitors.

The Credit Card Question: When to Ask, When to Skip

Requiring a credit card at signup used to be standard. The logic was that it filters out tire-kickers and improves trial-to-paid conversion. The reality is more complicated.

Removing the credit card requirement typically increases trial signups by 20–60%. That's a massive top-of-funnel gain. The tradeoff is that a higher percentage of those trials won't convert to paid. So the question isn't "should we require a card?" — it's "what's our conversion rate at each stage, and where does the math work out?"

For most early-stage SaaS companies, you should skip the card requirement. You need volume. You need to learn what makes users successful. You need case studies and testimonials. A credit card gate slows all of that down.

For more mature products with strong activation metrics and a defined ideal customer profile, a card requirement can actually improve the quality of the pipeline and reduce churn from users who were never serious. Run the test — don't assume.

Label and Layout Choices That Quietly Kill Completions

The field count matters, but so does the execution. A three-field form with bad labels and weird layout still underperforms.

Specific things that hurt completion rates: placeholder text instead of labels (placeholder text disappears when someone starts typing, which confuses users and fails accessibility standards), password requirements hidden until you get them wrong, and double email confirmation fields — nobody enjoys typing their email twice, and studies show it doesn't meaningfully reduce typos.

Things that help: inline validation that tells users immediately if their email is already registered, password strength indicators that appear in real time, and single-column layouts (two-column forms are consistently outperformed by single-column in A/B tests, probably because they feel more like a document than a conversation). Keep the form narrow — 400 pixels is plenty. Wide forms feel like paperwork.

What Happens Right After the Form Is Just as Important

Your signup form doesn't end when someone clicks the button. The confirmation step — what happens next — is part of the form experience, and most products treat it like an afterthought.

If you're using email verification, the time between form submission and the user's inbox is a conversion bottleneck. People forget, get distracted, or assume the email got lost. Spotify reduced drop-off at this stage by showing a clear, specific instruction: "Check your inbox — we sent you a link to confirm your email." They put the expected wait time on the confirmation screen. Small things, but they hold attention.

The best practice here is to eliminate email verification for signup entirely if you can — use it later, for sensitive actions. If you can't eliminate it, use a magic link instead of a password, send the email instantly, and make your confirmation page do the work of keeping the user engaged while they wait.

Run This Audit on Your Form Right Now

Before you touch anything, do this: sit down and go through every field on your current signup form. For each one, ask two questions — does this field change what we do in the next 48 hours? And does removing it create a meaningful operational problem? If the answer to both is no, cut it.

Then look at your form analytics. Tools like Hotjar, FullStory, or even Google Analytics form tracking will show you exactly where people abandon. If users are dropping off after the first field, you have a trust or expectation problem — the form showed up when they weren't ready. If they're dropping off at a specific field, that field is the problem. Cut it or move it.

Finally, test one change at a time. Remove the phone number field. Or swap your password field for a passwordless email link. Or make your job title field optional. Singular changes produce readable results. Multiple changes at once just give you noise.

The Bottom Line

The best signup form you can build is the one that asks for the least information needed to get someone into your product and experiencing value. That's almost always fewer fields than you think.

The instinct to collect data upfront is understandable, but it costs you real signups from real people who would have become real customers. Every field is a question you're making someone answer before they've decided they trust you enough to answer it.

Start with email and password. Add a field only when you can directly explain how it changes the experience for the user — not for you, for them. Then watch your numbers. The drop in form abandonment will make the case better than any argument you can have in a product meeting.

Your form isn't a data collection tool. It's the first moment someone decides whether your product is worth their time. Treat it that way.