What should a qualification form ask?
A user onboarding survey should ask only what changes the first path. Role, goal, company size, and what they used before are enough to pick a sequence. Everything else is a survey they skip. A qualification form is a fork, not a clipboard. If an answer cannot change a step, it does not belong on day one.
What should a qualification form ask?
A qualification form should ask only what changes the first path. Role, goal, company size, and what they used before are enough to pick a sequence. If an answer cannot change a step, it does not belong on the form.
I have watched teams ship a twelve-question welcome and then show everyone the same product tour. The answers sat in a profile. The path did not move. That is not qualification. That is a survey at the worst moment.
User onboarding starts after signup, not after a complete CRM record. The form has one job on day one: send this person down the path that matches why they came.
How is qualification different from a survey?
Qualification changes the next step; a survey collects answers you will read later. If you store the answer and the sequence stays the same, you asked too soon.
Save research for after they stay. NPS, “how did you hear about us,” and a wishlist of integrations are useful later. They are not useful while someone is still deciding whether leaving is cheap. Day one is a fork, not a clipboard.
A survey can live in week two. Qualification has to live in the first session, or the first session will be a tour of chrome they did not ask for.
Which four fields are enough to start?
Role, goal, size, and prior tool are enough to start because those four split the first hour. An enterprise lead coming from a competitor needs to map the old workspace. A manager of a team of 10 needs to invite someone and see a first win. Same product. Same aha if you named it well. Different first path.
You can add a field later when you have a third path that needs it. Do not add it because the CRM has a slot. UTM and other implicit signals can sit on the person without becoming another box they type.
Write the two first hours on paper before you open the form builder. If both hours still look the same after you fill in those four answers, you do not have a qualification problem yet. You have an aha you have not named.
How do you map answers to a first path?
You map each answer to a sequence before you ask the question. Role plus prior tool should pick more than a label on a person record. It should pick the next finishable win.
If they came from a competitor, the first checklist is import, map, and confirm the old workspace. If they manage a team of 10, the first checklist is invite, share, and ship one thing together. Users skip product tours when you skip that mapping and ship one script anyway.
Product knowledge is the other half. Form answers say who they are. Product context says what the path is allowed to claim. Without both, personalization is a first name in a tooltip and copy that could belong to any tool in the category. SaaS activation is this pairing: who they are times what you sell.
Do not invent a matrix. Two named segments and two sequences are enough to prove the form is doing work.
What should you do with a long welcome survey this week?
Cut the survey to the fields that change the first path, then park the rest. Map each remaining answer to a sequence before you ask it. If you cannot name the step, delete the question.
Open the live form. For each field, write the step it changes or write “none.” Delete every “none.” Publish the short form only after the two sequences exist. You can ask the parked questions after they stay.
A shorter form that branches is user onboarding. A long survey that everyone ignores is a profile project wearing an onboarding label.
How do you write a qualification form?
You write a qualification form by naming two first hours, keeping only the fields that change a step, and mapping each answer to a sequence before you publish.
- Write the aha for two segments that cannot share a first hour
- List the four fields that would change that first hour
- Delete every question that does not change a step
- Map each remaining answer to a sequence, then publish
Questions people ask
What should a qualification form ask?
Ask role, goal, company size, and what they used before. Those four change the first hour of user onboarding. An enterprise lead from a competitor needs to map the old workspace. A manager of a team of 10 needs to invite someone and see a first win. If a question cannot pick between those paths, it does not belong on the form. Save research, NPS, and how they heard about you for after they stay.
How is qualification different from a survey?
Qualification changes the next step in the onboarding path. A survey collects opinions you will read later. If you store the answer and the sequence stays the same, you asked a survey question at the worst moment, the first session. The form is a fork. Day one is not a research interview. Park extra questions until they have reached the named aha, then ask if you still need the data.
How many questions is too many?
More than you will use is too many. Four fields that compose a path beat twelve fields that decorate a profile. Each extra question is a chance they close the tab before they see the product. If you cannot name the checklist step or email the answer changes, delete the question. You can add a fifth field later when you have a third path that needs it. Do not add it because the CRM has an empty slot.
Which answers change an enterprise path versus a team of 10?
Role, goal, size, and prior tool split those two first hours. An enterprise lead coming from a competitor needs to map the old workspace onto yours. A manager of a team of 10 needs to invite someone and ship a first win. Same product. Same aha if you named it. Different first sequence. If your form cannot tell those two people apart, you will ship one product tour to both, and one of them will skip it.
Should the form ask for a first name or job title?
Ask a first name only if the next email or in-app step uses it as more than a greeting. Ask job title only if title picks a sequence. Most teams already know role from a shorter field. A first name in a tooltip is not personalization. Product knowledge is the other half of the pairing. Form answers say who they are. The path is only allowed to claim what you sell.
What if we already have a long welcome survey?
Cut it to the fields that change the first path, then park the rest. Map each remaining answer to a sequence before you ask it. If you cannot name the step, delete the question. You can ask more after they stay. Day one is a fork in the sequence, not a research interview. A shorter form that branches beats a complete profile that everyone ignores.
When can you ask more questions?
Ask more after they stay, or when you have a new sequence that needs a new fork. A later path can collect industry, team count, or an integration list once those answers change a later checklist. Do not load day one with every field you might want next quarter. Qualification is the smallest set that picks the first hour. Everything else waits.