The Anatomy of a High-Converting B2B Lead Form

Most B2B lead forms are built backwards: too many fields, a single long page, no conditional logic, and UTM parameters nowhere in sight. The result is a form that qualifies nobody and attributes nothing. This guide covers the anatomy of a B2B lead form that actually converts — field count, step structure, conditional logic patterns, UTM capture, and lead routing.

Whether you build with Forge, React Hook Form, or a no-code builder, the principles below apply to any B2B form — the implementation examples use the Forge React SDK.

1. The Optimal Field Count — It's Not “Fewer is Always Better”

The most repeated advice in conversion optimisation is “fewer fields = more conversions.” That is only half true for B2B. Here is how field count actually maps to outcome:

The recommendation: for B2B lead capture, use 5–6 fields across 2–3 steps. Multi-step forms outperform equivalent single-page forms because users commit to step 1 before seeing the full scope of the form.

2. Step 1 — The Hook (2–3 fields)

The first step should be low-friction. First name, work email, and company name. Never ask for phone number, annual revenue, or budget on the first screen — these are high-anxiety questions that convince the user the form is “salesy” before they've even committed.

// Step 1 schema — low friction
const step1Schema = z.object({
  firstName: z.string().min(1),
  workEmail: z.string().email(),
  company:   z.string().min(2),
});

3. Step 2 — The Qualifier (2–3 conditional fields)

Use conditional logic to adapt step 2 based on what you learned in step 1. If the user enters a company like “Acme Corp” you might show a “team size” dropdown. If they enter a personal email domain, you might show a “What are you building?” free text.

Forge's no-code conditional logic engine handles this with AND/OR operators and field value conditions — marketers can set this up without a developer writing a single if statement.

// React implementation of conditional step 2
const companySize = watch("companySize");

// Show the high-value path only for larger teams
const showEnterpriseQuestion = 
  companySize === "201-1000" || companySize === "1000+";

{showEnterpriseQuestion && (
  <Field label="What's the main pain point with your current form setup?">
    <textarea {...register("enterpriseNote")} rows={3} />
  </Field>
)}

4. The UTM Attribution Gap

Most B2B forms don't capture UTM parameters. The result: your marketing team cannot tell which campaigns drive your highest-quality leads — only which ones drive the most volume. Add these as hidden fields with default values read from the URL query string:

// Read once on mount, set as hidden field defaults
const params = new URLSearchParams(window.location.search);

// In useForgeForm / useForm defaultValues:
defaultValues: {
  utm_source:   params.get("utm_source")   ?? "(direct)",
  utm_medium:   params.get("utm_medium")   ?? "(none)",
  utm_campaign: params.get("utm_campaign") ?? "(none)",
  utm_content:  params.get("utm_content")  ?? "",
}

// Paired with hidden inputs:
<input type="hidden" {...register("utm_source")} />
<input type="hidden" {...register("utm_medium")} />

5. Routing Leads Intelligently via Webhooks

Not every submission deserves the same response time. Configure a Forge webhook with a filter condition: if companySize >= "201-1000" POST to your enterprise sales Slack channel immediately. All other leads go to your CRM queue. This pattern alone can cut average response time to enterprise leads from hours to minutes.

6. The Four Metrics That Actually Matter

• Completion rate: Submissions ÷ form views. If below 50%, your step 1 is too heavy
• Drop-off by field: Forge analytics shows exactly which field causes the most exits
• Time to complete: If median time is under 60 seconds, your qualification is too thin
• Lead-to-SQL rate: Cross-reference submissions with your CRM to see if completions are actually qualified