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.
Drop-off by Field