Inbound Form and Qualification Pack
Send your form's field-level drop-off data, get every field traced to a decision or priced for the submissions it costs.
Free download · No account needed
Drop-off by Field
Nettleford Systems, a fictional B2B SaaS company. 8,400 people started the "Request a Demo" form; every field's abandonment priced against how many actually reached it.
| Field | Reached | Abandoned | Category |
|---|---|---|---|
| Full name | 8,400 | 84 (1.0%) | Floor |
| Job title | 7,946 | 318 (4.0%) | Decision |
| Phone number | 7,628 | 1,335 (17.5%) | Cut |
| Company size | 6,293 | 315 (5.0%) | Decision |
| What are you hoping to solve? | 5,829 | 1,224 (21.0%) | Cut |
| How did you hear about us? | 4,605 | 391 (8.5%) | Cut |
| Final submissions | 4,214 | - | 50.2% overall |
The 3 Cut fields alone caused 2,950 of 4,186 total abandonments, 35.1% of every form start. Cutting them projects completion at 85.3%: 2,950 more finished submissions from the same traffic.
Field Register
Every field checked against the actual routing or qualification rule that reads it, not against how useful it feels.
| Field | Category | Decision it feeds |
|---|---|---|
| Company name | Decision | Matches an existing customer account |
| Job title | Decision | Exec-sponsor flag; routes ICs to SDR nurture |
| Company size | Decision | SMB / Mid-Market / Enterprise queue |
| Country / region | Decision | Territory rep pool |
| Phone number | Cut | None; the calendar tool collects it at booking |
| "What are you hoping to solve?" | Cut | None; asked live on the discovery call instead |
| "How did you hear about us?" | Cut | None; UTM parameters already answer it |
6 of 9 fields survive with a named decision or a foundational role behind them. Only the 3 above, all with no decision at all, got cut.
Routing Trigger Map
What each surviving field's value actually triggers, out of the 4,214 completed submissions.
| Field | Value | Routes to | Share |
|---|---|---|---|
| Company size | 1-99 employees | SMB self-serve queue | 44.3% |
| Company size | 100-999 employees | Mid-Market AE queue | 39.8% |
| Company size | 1000+ employees | Enterprise queue, named AE | 15.9% |
| Job title | C-level / VP / Head of | Exec-sponsor flag added | 13.9% |
| Country / region | NAMER | Territory A rep pool | 60.0% |
Company size and job title are read together: an Enterprise-tier account with an individual-contributor contact still routes to the Enterprise queue, but only the title adds the exec-sponsor flag.
Every guide on inbound form length converges on the same number: three to five fields, cut anything past that, ship it. The rule doesn't hold up as an absolute truth. One documented test cut a form from nine fields to six and lost 14% of its conversions, because the three fields removed were the ones visitors wanted most to answer. The real question was never how many fields a form has. It's whether each one feeds a decision your routing or qualification rules actually make.
This pack does that tracing directly. Every field on the live form gets checked against the actual routing, scoring, or qualification rules that exist today, not against how useful it feels. A field with a real decision behind it stays, no matter how much it costs in abandoned submissions, since the decision needs the value to run. A field with no decision behind it gets cut, and its information moves to wherever it can be collected without a gate: a later touchpoint, a downstream tool, or nowhere, if genuinely nothing depended on it.
On a worked run for Nettleford Systems, a B2B SaaS company, 8,400 people started a nine-field demo request form and only 4,214 finished it, a 50.2% completion rate. Three fields fed no rule at all and caused 2,950 of the 4,186 total abandonments, 35.1% of every start. Cutting just those three projects completion at 85.3%, 2,950 more finished, qualifiable submissions from the same traffic. It pairs with the routing rules those surviving fields ultimately feed and the account register a routed lead's owner still has to resolve.
What's in the pack
Field Register
Every field checked against the actual routing or qualification rule that reads it, not against how useful it feels.
Drop-off by Field
Every field's abandonment priced against how many people reached it, plus what cutting the no-decision fields would recover.
Field Rationale
The one-sentence reason every field is on the form, or the reason it was cut and where its information went instead.
Routing Trigger Map
Every surviving field's values wired to the exact queue, tier, or flag it triggers, checked against real volume.
Progressive Profiling Plan
Where every cut field's information gets captured instead, plus the standing bar any new field has to clear.
Field-earns-its-place rule
The standing rule that blocks a new field from going live without a named decision behind it.
How to use it
- 1
Send the form and its rules
The live form's field-level drop-off data, plus the routing, scoring, or qualification rules those fields are supposed to feed.
- 2
Trace fields and price drop-off
Every field checked against the rule that actually reads it, then priced by what it costs in abandoned submissions.
- 3
Cut or defer the rest
Fields with no decision behind them removed from the form, each with a stated destination for the information they were collecting.
- 4
Wire the routing map
Every surviving field's values mapped to the queue, tier, or flag it triggers, checked against real completed submissions.
Frequently asked questions
How is this different from generic advice to keep forms under five fields?
Generic advice sets a target field count with no way to check it against your own rules. This pack traces every field to a named decision instead. On the worked example, two Decision fields, company size and country, survive despite carrying real abandonment. Three lower-cost fields got cut anyway, because no rule read them at all.
We don't have field-level drop-off, just an overall completion rate. Can we still use this?
Start with the overall rate and the current field list, and trace each field to a decision anyway. That gets every field correctly categorized even without a precise price on each one. Add field-level analytics once available, since that is what turns a cut candidate into a cut backed by a real number.
Why keep company size and country on the form? They have some of the highest abandonment rates.
Because a routing decision needs their value to run at all. Company size decides which queue owns the account, and country decides the territory. Cutting either one doesn't lower cost overall, it just moves the same question to right after signup, when the routing decision is already waiting on it.
What happens to the phone number and free-text fields once they're cut from the form?
Nothing gets lost, it just moves. The calendar tool collects a phone number at booking, since every completed submission proceeds straight to scheduling anyway. The free-text question about what a visitor hopes to solve gets asked live on the discovery call instead, where a human is already listening for the answer.
Does this replace our lead scoring model or what happens to a lead after it's disqualified?
No, and the boundary is deliberate. Which attributes deserve weight once a lead exists belongs to lead scoring, and this pack only decides which of those attributes are worth asking for before that lead exists at all. What happens when a qualified lead later gets disqualified is a separate, later question that reason codes and recycle timers answer instead.
Once the form itself is fixed, how do we know leads are actually getting a fast response?
That's a separate, downstream question this pack doesn't answer. A cleaner form gets more qualifiable people through the door and routes them correctly once they arrive. How quickly a rep actually reaches them from there is what a speed to lead audit traces, rule by rule and owner by owner.
Once a field's routing decision picks a queue, how is the specific rep inside it chosen?
A separate decision this pack hands off deliberately. Company size and country decide which queue a lead reaches. Weighted round robin rules decide which specific rep inside that queue gets it, weighted by each rep's actual hours and capacity rather than a flat rotation.
Find out what your own form fields are actually costing you
Send your form's drop-off data. The first thing back is every field priced against what it costs to keep.
Price my form fields