Should B2B SaaS use progressive profiling?

Yes for PLG B2B and mid-market product-led signups; the same pattern as B2C with the additional discipline of capturing role and company size early enough to inform sales follow-up. Sales-led enterprise where the signup is really a lead-qualification form is a different problem - the form length is justified by the qualification need, not by user-acquisition optimisation.

What is the cost of each extra B2B signup field?

B2B users tolerate more fields than B2C, but the per-field cost is still 5-8pp drop in the 3-6 range and 8-12pp drop beyond 6 fields per HubSpot 2024 forms research. The break-even calculation: a 5pp drop in signup conversion needs to be offset by a 5pp lift in MQL-to-SQL or SQL-to-Closed rate for the field to pay for itself.

Last verified May 2026 · 8 min read

How many fields should a B2B SaaS signup form have?

Q: How many fields should a B2B SaaS signup form have?

It depends on ACV band. SMB B2B (under $5K ACV): 3 fields (work email, password, company name). Mid-market ($5K-50K): 5 fields (add role and company size). Enterprise ($50K+): 7 fields (add phone, industry). Beyond these counts, drop-off accelerates faster than lead quality improves per HubSpot 2024 forms data and Marketo benchmarks.

The B2C answer is 1-3 fields. The B2B answer depends on ACV band, sales motion (PLG vs sales-led), and what the form is actually for. This guide gives the cited field counts, the progressive-profile schedule, and the MQL-vs-PQL fork that decides which discipline applies.

Field count by ACV band

SMB B2B (under $5K ACV)

FIELDS

3 fields

TYPICAL CONV

30-45%

work email
password (or OAuth)
company name

Rationale. Treat as B2C plus minimal qualification. The MQL-to-SQL rate at this band is low enough that signup conversion lift dominates the lead-quality argument.

Mid-market ($5K-50K ACV)

FIELDS

5 fields

TYPICAL CONV

25-35%

work email
password (or OAuth + SAML)
company name
role / job title
company size / employees

Rationale. Role and company size justify themselves at this ACV: the sales team needs them to route the lead and price the contract. Beyond 5 fields, progressive-profile.

Enterprise ($50K+ ACV)

FIELDS

7 fields

TYPICAL CONV

20-30%

work email
password (or SSO)
company name
role / job title
company size
industry
phone (optional but recommended)

Rationale. Enterprise signup forms are lead-qualification forms in disguise. The signup conversion rate is secondary; lead quality is the primary KPI. Phone optional unless your SDR motion runs on outbound.

Progressive profile: what to defer

Six common B2B signup-form fields that almost always belong in progressive-profile, not the signup form.

Field	When to capture	Source
Phone number	Defer until first sales-team call request	HubSpot 2024 forms research
Use case / Goal	Capture in product first-run experience, not on signup	Reforge product growth content
Team size beyond company size	Defer until workspace setup	Lenny Rachitsky benchmarks
Industry sub-segment	Infer from email domain + Clearbit-style enrichment, do not ask	ZoomInfo / Clearbit case data
Budget / Timeline / Authority (BANT)	Defer to SDR call, never on signup form	Marketo benchmarks, Mutiny
Marketing channel	Track via UTM, do not ask	Segment, common-sense analytics

The MQL-vs-PQL fork: two completely different problems

The biggest mistake in B2B signup-form design is treating PLG (product-led) and sales-led signup as the same problem. They are not. A PLG signup form is account creation with light qualification; a sales-led signup form is a lead qualification questionnaire. Field-count discipline applies in opposite directions.

	PLG signup form	Sales-led signup form
Goal of the form	Account creation, get into the product fast	Qualify a lead, route to the right SDR
Primary KPI	Signup conversion rate	MQL to SQL conversion + SDR pickup rate
Field-count discipline	Aggressive: 3-5 fields, progressive profile rest	Permissive: 5-9 fields, sales accepts the conversion hit
Email verification	Verify-later or soft-verify	Hard verify (cuts spam leads, accepts the drop)
OAuth offering	Yes (work-email Google OAuth)	Often no (corporate OAuth politics outweigh conversion lift)
What success looks like	70% of starts complete signup	50% of leads are qualified, 25% become opportunities

The break-even math: when an extra field pays for itself

The honest test for an extra B2B signup field: does it lift downstream MQL-to-SQL conversion (or sales velocity, or lead score accuracy) by more than it depresses signup conversion?

Worked example. 2,000 monthly signups at 35% completion, $1500 LTV, mid-market sales motion. Adding a sixth field drops completion to 28% (per HubSpot 2024 average of 7pp drop in the 5-7 band). Lost monthly signups: 140. Lost annual LTV: $2.52M.

Break-even: the extra field needs to add $2.52M of incremental closed-won revenue from better sales targeting. At a 25% close rate on $1500 LTV deals, that means routing 6,720 better-qualified leads to the right SDR per year. If you are not generating that much downstream lift from one extra question, the field is not paying for itself.

To run the math for your own ACV and volumes, see /calculator. For the design pattern of deferring fields, see /progressive-profiling.