# Fewer Fields on a Demo Request Form: A/B Test Example

Page: https://alidemirbas.com.tr/en/lab/ab-test-library/tests/fewer-fields-on-a-demo-request-form-ab-test-example

## Hypothesis

If the form keeps only the fields needed for an initial assessment, visitors may submit a request with less effort. As long as sales can fill in the missing context during follow-up, the qualified opportunity rate per assigned visitor may rise.

## When to run this test

Form analytics with drop-offs clustered on certain fields, long completion times, or session recordings of visitors abandoning the request form halfway point to a form whose length wears people down. If trimming it helps, form submissions rise while the qualified lead share holds. Before you start, confirm that sales does not genuinely need the fields you remove and can collect that information in follow-up when it is needed; if they cannot, a shorter form only moves the problem to the sales side.

## Primary metric

**Qualified opportunity rate**: Measure qualified opportunities per eligible assigned visitor over the same follow-up period.

## Other metrics

- **Form submission rate**: Compare valid submissions among eligible visitors who see the form.
- **Form completion time**: Measure time among visitors who start the form; report non-completions separately.
- **Qualified lead share**: Report the share of submitted leads that qualify and qualified opportunities per assigned visitor.
- **Sales prequalification time**: Compare time spent prequalifying each lead using the same method and period.

## What to check before and during the test

- **Change**: Remove fields predefined as unnecessary for initial qualification; keep the remaining fields and follow-up flow the same.
- **Keep constant**: Keep remaining field copy, validation, CTA and follow-up process unchanged.
- **Volume**: Track completed forms and valid submissions.
- **Quality**: Make the qualification denominator explicit; the primary decision is qualified opportunities per assigned visitor.
- **Separate tests**: Test individual required fields or post-submission data collection separately.

## What to watch when reading the result

- Decide on the qualified opportunity rate per assigned visitor; a higher form submission rate is not enough on its own. Look at qualified lead share, sales prequalification time and the close rate over the same follow-up period; if missing information slows screening, the gain on the form can disappear in sales.
- The result measures removing a predefined set of fields together, not the effect of any single field. Keep the form design unchanged and check that the remaining required fields are clearly marked in both arms, or the difference may not come from the number of fields.
- Qualified opportunities are far rarer than form submissions. If the difference is unclear, use the [sample size calculator](https://alidemirbas.com.tr/en/calculators/sample-size-calculator) to see how many visitors this comparison needs, and leave requests whose follow-up period has not ended out of the decision.

## Frequently Asked Questions

### Which form fields can be removed?

Remove only predefined fields unnecessary for initial qualification. Ensure sales-critical information can still be collected when needed. Keep remaining wording, validation, CTA and follow-up unchanged. Use qualified opportunities per assigned visitor as the primary outcome.

### Will a shorter form reduce lead quality?

It may, but that is not inevitable. Submissions, qualification share and screening time explain the result. Use the same qualification rule and follow-up period.

### Which sales-team signal should I monitor?

Compare screening time per request consistently. Missing information may erase gains from easier submission. Check close rates as well as form conversion.

### Can this reveal the effect of one particular field?

No. It measures removal of a predefined set. Individual field requirements and post-form collection need separate tests. Keep form design unchanged.