Someone reruns this argument every few months and both sides come armed with the same evidence.
One side: cut your form to three fields, every field you remove lifts conversion. The other side: your sales team is drowning in junk, add qualifying questions. Both are describing something real, and both are answering the wrong question.
The number of fields is a secondary variable. Which fields you chose is the primary one. Three well-chosen questions qualify better than eight badly chosen ones, and I have seen forms with two fields produce a cleaner pipeline than forms with nine.
The short versus long argument, done honestly
What the short-form side has right: adding fields lowers submissions. That is real and it is consistent. Every extra question is another moment where someone decides this is more effort than it is worth.
What the short-form side misses: the drop is not evenly spread across your visitors. The people who abandon a longer form are disproportionately the ones with low intent, because a person who genuinely wants to talk to you will fill in six fields without much thought. So a longer form can cut total submissions substantially while leaving qualified opportunities almost unchanged.
What the long-form side has right: raw lead count is a terrible number to run a marketing team on. A hundred submissions that produce four real conversations are worse than thirty that produce twelve, once you count the sales hours spent finding out.
What the long-form side misses: most of the fields they add do not qualify anything. Phone number, job title, how did you hear about us, and a budget dropdown do not tell your sales team whether this account is worth a call. They just make the form longer.
So the honest version is that both camps are optimising the wrong variable, and the fix is to look at each field individually and ask what it is doing.
What a form field is actually doing
Every field on a B2B form is doing one of three jobs. Most forms mix them up.
- Contact. How you reach the person. Name and email. That is it. Phone number belongs here only if someone will actually call, and if nobody calls, the field is theatre.
- Fit. Whether this account matches who you can serve. Company name, company size, industry, sometimes location. This is the half of qualification a person's behaviour on your site cannot tell you.
- Intent. Why they are here now. What problem they are trying to solve, what triggered the search, what they have already tried.
Fit questions are increasingly answerable without asking. Intent questions are not, and they are the ones most forms leave out entirely.
The fields that predict qualified pipeline
Run this check on your own data rather than trusting anyone's list, including mine. Export twelve months of form submissions, mark which ones became qualified opportunities, and look at which field values show up disproportionately in that group. A field with no relationship to outcomes after a year is collecting information nobody uses.
What tends to hold up in B2B:
Company name. The single most useful field, because it makes everything else lookupable. It also filters casually, since people who are just browsing often skip it or type something meaningless.
Company size. Usually the strongest predictor of fit for a services or software business, because deal size and complexity both track with headcount. Offer bands rather than a free text number.
An open question about their situation. One optional text box: what are you trying to solve. This is routinely the most valuable thing on a B2B form and the first thing people cut. Someone who writes three sentences about a specific problem is a different prospect from someone who leaves it blank, and your sales team can see that before the first call.
What tends not to hold up: how did you hear about us, which people answer badly and which your analytics answers better. Job title, which is useful context but rarely decides anything on its own. And budget.
Why company size beats budget
Budget is the question everyone puts on a form and almost nobody can answer accurately.
Think about who is filling it in. They have not scoped the work. They do not know what your category costs. They may not control the money at all. So they pick the middle option, or the lowest one to avoid looking like an easy target, and now your CRM holds a number that was a guess.
Then it gets worse, because the guess becomes real. A sales rep sees the range and either disqualifies a good account or anchors the whole conversation to a figure the prospect invented in four seconds.
Company size does not have this problem. People know their own headcount. They answer it honestly because there is no reason not to. And for most B2B businesses it correlates with what a deal is worth well enough to route on. A 12-person firm and a 400-person firm are different conversations regardless of what either one guessed about budget.
If you genuinely need budget qualification, it belongs in the first call, where someone can ask follow-up questions. A dropdown cannot.
Let enrichment answer what it can
This is the part that has actually changed, and most forms have not caught up.
Given a business email address and a company name, tools like Clearbit, Apollo, and Clay can usually return headcount, industry, location, revenue band, and the technologies a company runs. HubSpot does a version of this natively on company records. Coverage is better for larger and more established companies than for small local businesses, so check it against your own list before you rely on it.
Where it works, stop asking. Every firmographic field a tool can fill is a field you are charging your visitor for information you could have looked up. Ask for what enrichment cannot know, which is why they are here and what they need.
The practical shape: name, work email, company, and one optional open question. Enrich on submission. Route on the enriched data. Your form got shorter and your qualification got better at the same time, which is the outcome both sides of the original argument said was impossible. If you are building this inside HubSpot, the workflow recipes post covers the routing side.
The routing question nobody asks
A form is one half of a system. The other half is what happens in the sixty seconds after someone hits submit, and that part is usually left as a default nobody chose.
Two questions worth answering before you touch the fields. Where does each submission go, and how fast does a person see it? A demo request that lands in a shared inbox somebody checks twice a day is a demo request you will lose to whichever competitor replied first. A person who filled in your form is actively comparing options, and the comparison does not pause for your process.
The second question: does the form tell the person what happens next? Most confirmation messages say thanks, we will be in touch. That is a wasted screen. Say who will contact them, roughly when, and what the first conversation covers. It costs nothing, it reduces no-shows, and it is the last impression the form leaves.
Progressive profiling without the trap
Progressive profiling asks a few questions now and different questions later, once the earlier answers are stored. HubSpot supports it with queued fields, and the idea is sound: never ask the same person the same thing twice, and build the profile across visits.
It works well for a returning visitor who is recognised. It breaks in specific, predictable ways.
- Device switching. First visit on a laptop, second from an email link on a phone. Different cookie, no recognition, first-stage questions again.
- Cleared cookies and privacy settings. More common every year, and the trend is going one direction.
- Multiple people from one company. Three colleagues download three things and you have three partial records that look like three separate buyers.
So treat progressive profiling as something that improves your data when it works rather than as the system your qualification depends on. The first form should stand on its own. If the only way you learn company size is a second visit that may never happen, you have built a process that fails quietly.
And keep the queue short. Two extra fields on a second form is reasonable. A queue of eight means most people never reach the useful ones, since the majority of your visitors submit once and never come back. That data hygiene problem is the same one covered in the CRM data hygiene post, arriving through a different door.
The takeaway
Stop counting fields. Look at each one and say what job it does: contact, fit, or intent. Delete anything that does none of the three, and delete anything enrichment can answer for you.
What is left for most B2B companies is short. Name, work email, company, and one open question about what they are trying to solve. Ask company size when enrichment cannot cover you. Never ask for budget on a form.
Then measure qualified opportunities instead of submissions, because that is the number the form was supposed to be improving all along.