A qualification form should improve the next conversation. Collecting more information is not automatically better if it makes a suitable customer abandon the process or asks questions nobody uses.

The working map
  1. 01Define a useful fit
  2. 02Ask questions that change an action
  3. 03Deliver a clear response
  4. 04Check both kinds of error
01

Define a useful fit

Write down the conditions that make a project appropriate: the problem, the decision owner, the timing and the resources needed. Distinguish a genuine requirement from a preference. A budget range can help scope a conversation without pretending that every customer knows the right figure in advance.

Make the service boundaries visible before the form. People should not have to submit personal information to discover that the offer does not cover their situation.

02

Ask questions that change an action

For each field, explain how the answer affects routing, preparation or the decision to proceed. If it changes nothing, consider removing it. Use plain language and allow a reasonable “not sure yet” where uncertainty is legitimate.

Do not collect sensitive information simply because it might become interesting later. Keep the intake proportionate to the service and handle the information appropriately.

03

Deliver a clear response

Explain what happens after submission, who will respond and what the conversation will cover. If the work is outside scope, close the loop rather than leaving the person waiting indefinitely.

04

Check both kinds of error

Review unsuitable enquiries that passed through and suitable prospects who struggled with the form. Qualification can fail by admitting the wrong work or by rejecting good work too early. Use actual conversations to improve the questions. A stronger sales process helps people make a sound decision; it does not merely make the seller's calendar look selective.

Share this article

Continue the thread

System Maps

Write the revenue model before choosing the tactic.

System Maps

Make a referral easy to explain.

System Maps

Test the assumption before building the company around it.