Guide · Lead generation
B2B lead forms for paid ads: ask the questions that separate buyers
Most form advice tells you to cut fields until completion rate rises. In B2B that often buys you more students, job-seekers and tiny buyers. Friction is a filter: add the fields that separate buyers, remove the ones nobody uses, and judge the form on cost per qualified lead.
How many fields should a B2B lead form have?
Short answer
As many as you need to route and qualify the lead, and no more. Name, contact details and two or three qualifying questions, such as company size, requirement and timeline, usually beat both a two-field form and a ten-field form. Judge any change by cost per qualified lead, because fewer fields can raise volume while cutting real buyers.
Field count is the wrong unit. A form with seven fields that sales reads on every lead is better than a form with four fields where two are ignored. What matters is the job each field does, and whether that job has to happen before the first conversation.
Paid ads add a second reason to care. Every submission is a conversion that Google, Meta and LinkedIn learn from. A form that anyone can fill in teaches bidding to find anyone. A form with a qualifying question lets you record which leads qualified and send that stage back, so bidding learns what a buyer looks like. See lead quality for how to define one.
Original framework
The Field Decision Table
Put every current and proposed field into one of five classes. Keep Route, Qualify and Signal fields on the first form. Move Personalise fields to the first call. Delete Remove fields.
| Class | What the field does | Fields that usually belong here | Where it goes |
|---|---|---|---|
| Route | Decides who should call and how fast | Country or region, product line, phone | First form |
| Qualify | Tests fit or requirement | Company size band, buyer type, quantity, service needed | First form |
| Signal | Becomes a status you can send to the ad platforms | Timeline, use case, a requirement that marks a lead technically qualified | First form |
| Personalise | Helps sales prepare, but doesn’t change whether they call | Current tool, job title detail, long project description | First call or an optional field |
| Remove | Nobody reads or uses it | Fax, full address for a demo, “how did you hear about us” when tracking already records source | Delete |
Run the table with the person who calls the leads. The test for each field is simple: “If this answer changed, would you do something different with the lead?” If the answer is no, the field isn’t earning its friction.
Which qualifying questions work for demo, RFQ and consultation forms?
Short answer
Ask what separates a lead sales can act on from noise. RFQ forms need product or specification, quantity, delivery location, buyer type and timeline. Demo forms need company size, role and use case. Consultation forms need the service, company size, decision role and timeline. Use dropdowns or bands, each with an “other” option.
These three templates cover the main B2B segments. Treat them as a starting point to run through the Field Decision Table, not a fixed list.
| Segment | Qualifying fields | Contact fields | Optional |
|---|---|---|---|
| Industrial RFQ | Product or category (dropdown); quantity with a minimum order hint; delivery city, state or country; buyer type (end user, EPC contractor, distributor, other); timeline | Name, phone, email, company | Specification or drawing upload |
| SaaS or IT demo | Company size band; role; primary use case; timeline | Name, work or other email, company | Current tool |
| Consulting enquiry | Service needed; revenue or employee band; decision role; timeline | Name, email, phone, company | Brief description |
Wording decides whether answers are usable:
- Bands, not open text. “50–199 employees” can be reported and routed. “About 120 people, growing” can’t.
- Always offer “other”. Without it, people pick the nearest wrong answer and your data lies.
- Ask timeline neutrally. “When do you need this?” with ranges such as “within 30 days”, “1–3 months” and “just researching”. Researchers who say so are useful, not failures.
- Leave budget for the call unless a minimum is a hard cut-off. If it is, state the minimum on the page instead of asking.
The page the form sits on can pre-qualify too, with who the offer is for, minimums and locations served. That is covered in the B2B landing page guide.
Do qualifying questions hurt lead volume, and is that OK?
Short answer
Usually they lower submissions, and that is fine when the qualified rate rises by more. At equal spend, a new form wins if the new qualified rate divided by the old qualified rate is greater than old submissions divided by new submissions. Test on qualified leads, never on submissions or completion rate alone.
The break-even rule comes from one line of arithmetic. Qualified leads equal submissions times qualified rate. If spend is the same, the form with more qualified leads has the lower cost per qualified lead.
| Form | Demo requests | Cost per lead | Qualified rate | Qualified | Cost per qualified lead |
|---|---|---|---|---|---|
| 3 fields | 120 | $75 | 25% | 30 | $300 |
| 5 fields (adds company size and use case) | 90 | $100 | 40% | 36 | $250 |
Check: 40% ÷ 25% = 1.6, and 120 ÷ 90 is about 1.33. Because 1.6 is greater, the five-field form wins, even though its cost per lead is a third higher.
| Form | Enquiries | Cost per lead | Technically qualified | Qualified | Cost per qualified lead |
|---|---|---|---|---|---|
| Name and phone only | 300 | ₹1,000 | 20% | 60 | ₹5,000 |
| Adds product, quantity and buyer type | 200 | ₹1,500 | 40% | 80 | ₹3,750 |
Check: 40% ÷ 20% = 2, and 300 ÷ 200 = 1.5. The longer form wins. The sales team also makes 100 fewer calls a month to reach 20 more qualified buyers.
The rule fails in one case: if the qualifying question scares off good buyers as well as poor ones, the qualified rate barely moves and the new form loses. That is why the test has to count qualified leads. Run your own figures through the cost per qualified lead guide.
Website form or native lead form: Google, Meta or LinkedIn?
Short answer
Native lead forms are faster to submit, especially LinkedIn’s prefilled forms, which raises volume but often lowers intent. They work well when you add qualifying questions and send qualified outcomes back. Website forms suit RFQs that need detail or attachments, and let the landing page do more pre-qualifying before anyone submits.
| Form | What helps quality | Watch out for | Go deeper |
|---|---|---|---|
| Google lead form with qualifying responses | Qualifying questions are required, and a submission with a qualifying answer is tagged as a qualified lead under the conversion action “Lead form – Response qualified (Google-hosted)” (Google Ads Help) | Search campaigns only; a self-declared answer isn’t the same as a sales-qualified lead | Improve lead quality in Google Ads |
| Meta Instant Forms | The higher intent form type adds a step where people review and confirm their answers before submitting (Meta for Developers); custom questions | Details are pre-filled, so accidental and low-intent submissions are common on the volume form type | Instant Forms lead quality |
| LinkedIn Lead Gen Forms | Up to three custom questions and up to 20 hidden fields for tracking, alongside up to 12 profile fields (LinkedIn Help) | Profile prefill makes submission a couple of taps, so intent varies widely | Lead Gen Forms lead quality |
| Website form | Unlimited fields, file uploads, page proof before the form | Click IDs lost through redirects; more drop-off on mobile | Landing page guide |
Use a website form when the buyer needs to upload a drawing, when the page has to show capability before a buyer will ask, or when you need more than three qualifying questions. Use a native form when speed matters more than detail and sales can call quickly. If you can’t decide, run both with the same offer and compare cost per qualified lead over the same weeks.
Multi-step forms, progressive profiling and enrichment
Each technique solves a different problem, and each can break your conversion data.
- Multi-step forms help when a form has five or more fields: ask the easy qualifying question first, contact details last. Fire the conversion only on the final step. A tag on step one reports partial forms as leads and teaches bidding to find people who start forms.
- Progressive profiling asks returning contacts for new fields instead of repeating old ones. It suits content offers and nurture, not a first RFQ from a new buyer.
- Enrichment fills company size or industry from a data provider so the form can be shorter. It works best for mid-market and enterprise teams with a CRM. Enriched data is still personal data, so check notice and consent rules first.
How do you keep spam and bots out of your ad conversions?
Short answer
Add a low-friction bot check, a hidden honeypot field, phone validation and a server-side duplicate check. Then make sure obvious spam never counts as a conversion, or is sent back as disqualified. Fake leads don’t just waste sales time; if they fire your conversion tag, bidding learns to find more of them.
- Bot check. Use a managed or invisible challenge such as Cloudflare Turnstile or reCAPTCHA rather than a puzzle every visitor has to solve.
- Honeypot. A field hidden from people; if it’s filled in, a bot did it.
- Validation. Check phone length and country code, and reject impossible email formats before submit.
- Duplicates. Match on email or phone within a short period, server-side, so repeat submissions don’t count twice.
- Conversion rules. Fire the tag only after the submission passes these checks. If spam still lands in the CRM, mark it disqualified with a reason code.
Form-level defences are one part of the problem. For a full diagnosis order across targeting, placements and offers, see junk leads from ads.
Should B2B forms block free email addresses?
Short answer
Usually not in India or the UAE, where many owners and industrial buyers use free email addresses. Blocking them removes real buyers. Flag free domains as a lower-fit signal instead, and rely on company, requirement and buyer-type questions to qualify. In US SaaS, requiring a work email is more common but still worth testing.
A flag keeps the lead and informs the score. It also keeps your test honest: if free-domain leads from a campaign rarely qualify, the data will show it. See the lead scoring framework for how to weigh it.
Consent and privacy on B2B forms
Business contact details are personal data. Keep marketing consent separate from the terms, say plainly how you’ll contact the person, and check before uploading form data to ad platforms. The details for India, the UAE and the US are in lead generation compliance.
Context
Company size, India, UAE and US
SMB
One form, two or three qualifying fields and a spreadsheet with each lead’s status and status date. Review the Field Decision Table once a quarter with whoever calls the leads.
Mid-market
Route by field, map every field to a CRM property, and pass UTM parameters and click IDs in hidden fields so outcomes can be matched to campaigns later.
Enterprise
Enrichment replaces some fields and new leads are matched to known accounts. Legal review of data use and a named owner for form changes keep regions consistent.
India
Buyers expect a phone call, so make phone required and validate it. Offer a separate, unticked WhatsApp opt-in. An optional GSTIN field is a useful fit signal for industrial buyers.
UAE and GCC
Ask country and emirate, because costs and delivery differ. Validate +971 and other GCC phone formats. A free-zone or mainland field helps sales on delivery and invoicing. See B2B paid ads in the GCC.
US
Work email is common for SaaS demos. A state field helps territory routing. If sales will text the lead, collect TCPA-compliant consent in its own checkbox.
Failure modes and a test plan
- Judging form tests on submissions. The shorter form almost always wins on volume; that isn’t the question.
- Blocking free email domains in markets where buyers use them.
- Required fields sales never reads. Friction with no benefit.
- Native forms with no qualifying question. Cheap volume, then a collapsing qualified rate.
- Multi-step forms that fire the conversion on step one.
- Dropdowns without an “other” option.
- Consent bundled into the terms.
- Thank-you pages reachable without submitting, so visits count as leads.
A test plan that works at B2B volumes
- Change one thing that matters: a qualifying question, the form type or the offer. Not button colour.
- Keep spend and targeting the same for both versions, or split traffic with a platform experiment.
- Wait until sales has marked a status on the leads from both versions. Newer leads always look worse.
- Compare qualified leads and cost per qualified lead, with the break-even check above.
- Treat a result as directional until each version has a few dozen qualified leads, and confirm it over a second period.
What to measure next
| Measure | Formula | Why it matters |
|---|---|---|
| Qualified rate by form | Qualified leads ÷ submissions | The half of the break-even that completion rate hides |
| Cost per qualified lead by form | Spend ÷ qualified leads | The number the test is decided on |
| Field completion | Leads answering each optional field ÷ leads | Shows which optional fields buyers ignore |
| Disqualification reasons | Count of each reason code | Tells you which qualifying question is missing |
| Spam share | Leads marked spam ÷ leads | Shows whether the defences are working |
Once statuses exist, send the qualified stage back to the platforms; CRM lead stages for ad platforms covers how. Zephra uses lead quality and business outcomes from CRM data or a spreadsheet, and creates and manages landing pages on Google, Meta and LinkedIn campaigns where configured. See lead quality optimisation.
Questions, answered
B2B lead forms FAQ
01Should a B2B form be multi-step or single-step?
Multi-step helps when there are five or more fields: start with an easy qualifying question and ask for contact details last. With three or four fields, a single step is simpler. Either way, fire the conversion only when the final step is submitted.
02Should the phone field be required?
It depends on the market and how sales works. In India and much of the GCC, buyers expect a call and a required, validated phone field is normal. For US SaaS demos booked by email, an optional phone field usually costs fewer good leads.
03Should a lead form ask about budget?
Usually not on the first form. Budget answers are unreliable before a conversation. If you have a hard minimum, state it on the landing page. If you must ask, use bands and include a “not sure yet” option.
04How long should a form test run?
Until both versions have leads that sales has reviewed, and enough qualified leads to compare. For many B2B accounts that means several weeks, not days. Count qualified leads per version rather than days on the calendar, and confirm a winner over a second period.
05Does a CAPTCHA hurt conversion?
Visible puzzles add friction for every buyer. Managed or invisible challenges, combined with a honeypot field and server-side duplicate checks, stop most bots without asking people to do anything.
06Should the form ask how people heard about us?
Only as an optional field. Tracking with UTM parameters and click IDs records the paid source more reliably. Self-reported source is still useful for spotting word of mouth, podcasts or events that tracking can’t see.
Your accounts
Find out whether your forms or your targeting are letting junk leads in.
The free ad account assessment reviews wasted spend, campaign structure, performance constraints and measurement gaps across Google, Meta and LinkedIn. It takes 10–15 minutes, needs no CRM and makes no campaign changes.