A practical lead qualification checklist for service businesses

Qualify the next step before the whole opportunity

Early enquiries rarely contain a complete buying brief. Someone may know the problem but have no budget yet. An assistant may collect options for a director. A founder may ask about a deadline before deciding what the project includes. Treat missing information as unknown, not as proof of poor fit.

The familiar BANT framework covers budget, authority, need and timeline, as Salesforce explains in its guide. Those topics are useful, but a service firm also needs to establish delivery fit and scope. Ask only what is necessary at the current stage instead of turning the first reply into an interrogation.

1 The problem and the outcome

Record the problem in the prospect’s words. Separate the symptom from the requested service. “We need a chatbot” describes a proposed solution; “our team repeatedly answers the same booking questions” describes work you can investigate.

• What is happening today?
• What would a useful improvement look like?
• Who is affected, and how often does the problem occur?

A useful first question is: “What would you want to be easier once this is working?” Avoid adding a revenue or time-saving claim that the prospect did not give you.

2 The scope and delivery fit

Identify whether the request falls within what your business can actually provide. Include service type, location where relevant, current tools, required deliverables and important constraints. Some requests need a specialist you do not have; others need a smaller scope than the buyer initially describes.

• Which part of the work is included?
• What must remain outside the project?
• Are there access, security or specialist requirements that need review?

Ask “Which part would you like us to handle?” before assuming ownership of an entire process. Record tool names as reported by the prospect. A mentioned system is not yet a verified integration.

3 Timing and dependencies

Distinguish a preferred start date, a deadline and the reason behind it. A fixed event creates a different constraint from a general desire to move quickly. Ask what must happen before work can begin, such as access approval, content preparation or a decision from another team.

A useful question is: “Is there a date this needs to support, and what drives that timing?” If the requested date looks difficult, route the enquiry to the delivery owner. Do not let a qualification score turn a preference into a promised completion date.

4 The decision process

Find out how the prospect will choose a provider and who needs to participate. The person who first contacts you may be essential to the decision even if they do not sign the contract. Do not downgrade someone purely because of their title.

• Who will use or review the proposed work?
• Who needs to approve the scope or spending?
• What information will those people need to decide?

“Who else should be involved when we discuss the scope?” is usually a more helpful opening than asking whether the contact is the decision-maker. Store only relevant professional context.

5 Budget and commercial expectations

Budget helps establish whether the likely scope is feasible. It can also be unsettled because the buyer needs your input. Ask whether there is a working range, a spending limit or an approval process, and make it safe for the prospect to say they do not know yet.

For example: “Have you set a budget range, or are you using this conversation to work out what the project should include?” Keep an unknown budget visible. If your business has a genuine minimum engagement level, use an approved explanation rather than an invented estimate or a blunt rejection.

A compact record your team can use

Use a consistent record for each enquiry. The point is to show what is known, where it came from and what happens next. Avoid a dense collection of fields that nobody maintains.

• Need: the problem and desired outcome, with the source message.
• Fit and scope: relevant service, constraints and unresolved questions.
• Timing: preferred date, hard deadline if stated and dependencies.
• Decision process: current contact and other required participants.
• Budget: stated range, approval route or explicitly unknown.
• Next action: owner, action, due date and reason.
• Contact status: active, paused, closed or no further contact requested.

Keep facts separate from interpretation. “Prospect asked for a quote” is an observed fact. “Ready to buy” is an inference that may be wrong. Require evidence before the inference affects priority.

Route the enquiry without hiding uncertainty

A small team can begin with four routes: ready for discovery, clarification needed, revisit at an agreed time, or outside current scope. Give each route a defined owner. An AI-generated summary can propose a route, but ambiguous or consequential decisions should reach a person.

Illustrative example: a consultancy receives “We need help with onboarding before our November intake.” The problem and timing are partly known; volume, current process and scope are missing. The next action is a clarification about the onboarding steps and intake size. The record should not invent a budget or assume the sender can approve it.

If you introduce scoring later, first define the evidence for each score. Review incorrectly rejected or delayed enquiries as well as the leads that progressed. A high score should never conceal an unresolved delivery constraint.

Measure whether qualification helps the conversation

Track how many enquiries have a clear owner and next action, how often staff must reread the thread to understand the need, and how frequently routing is corrected. Review whether your questions produce useful answers. A lower meeting count may be reasonable if fewer unsuitable meetings are booked, but it needs context.

Being AI can assess enquiry triage and qualification summaries as part of a scoped managed workflow. Your team defines the criteria, approves customer messages and owns commercial decisions. Request a workflow diagnosis to turn your current checklist into a pilot with explicit boundaries and measures.