Write explicit fit criteria and a short qualification checklist before offering an agency or consultancy sales appointment: Practical Guide to Lead Qualification Checklist
Why the Checklist Comes Before the Calendar
Every appointment your agency offers costs the same scarce inventory: senior human hours. A booked call with a buyer who was never a fit burns that inventory twice, once for the seller who prepared, and once for the buyer who spent their time on a conversation that could never lead anywhere. A sales lead qualification checklist written before the appointment exists is the cheapest protection that inventory has.
The alternative is qualification by conversation, which feels consultative and performs terribly. Without written lead qualification criteria, every team member applies their own private standard. The friendly closer books anyone warm. The skeptic declines anyone cautious. Aggregate numbers become unreadable because the input rule changed with each person's mood. B2B lead qualification only becomes an operations discipline when the standard is written, short, and applied identically by everyone.
The worksheet below fits on one page and divides every fact you know about a lead into three piles: must-haves, useful context, and unknowns. The piles, not the conversation, decide what happens next.
The Fit-Decision Worksheet
Define each pile before the first lead touches it.
Pile 1: Must-Have Conditions
The conditions without which no appointment is offered, regardless of enthusiasm. For most agencies and consultancies, three to five conditions is the right number. More and the checklist becomes a wall; fewer and it qualifies nothing.
Typical must-haves, tuned to your actual business:
- Budget reality: The engagement size you actually deliver fits the buyer's stated or observable range.
- Timeline: The need lands inside a window in which you could realistically start.
- Decision access: The person you are talking to can decide, or can bring the decider to the next step.
- Service match: The problem is one your service actually solves, not adjacent hope.
- Working constraints: Any non-negotiable, such as region, language, compliance regime, or a required tool you do not support.
Write each as a checkable sentence. "Budget appears consistent with engagements we deliver" is checkable from a form field or a short exchange. "Seems serious" is not.
Pile 2: Useful Context
Facts that shape the conversation but never justify declining alone: company size, current tooling, team structure, how they heard about you, urgency flavor. Context informs preparation; it must not be allowed to masquerade as a gate. If you find yourself declining on context, the must-have list is wrong and should be amended formally, not improvised per lead.
Pile 3: Unknown Answers
Facts you do not have yet, each tagged with the cheapest way to learn it: a form field, a two-line email, or the call itself. Unknowns are legitimate and expected. The rule is only that they stay visible and get resolved in a named order, cheapest first.
Table 1: Worksheet Decision Rules
| Pile State | Decision | Action |
|---|---|---|
| All must-haves pass | Proceed | Offer appointment slots directly |
| Must-haves pass, unknowns cheap to resolve | Clarify | One short exchange to close unknowns, then decide |
| Any must-have fails | Decline | Polite decline with a fitting alternative if one exists |
| Unknowns expensive to resolve | Decline or park | Park with a revisit date if the unknown may resolve itself |
Proceed, Clarify, and Decline: Fictional Worked Cases
Test the worksheet on fictional cases until every team member rules identically. Consistency is the point of the exercise.
Case A, proceed. A 40-person e-commerce operator needs a retention email program rebuilt; their form states a project range you regularly deliver, the start window is six weeks out, and the writer is the managing director. All must-haves pass on paper. Offer slots the same day, and use pile-two facts, their current tooling, their team structure, to prepare the call.
Case B, clarify. A freelancer inquires about the same service. Budget and timeline look plausible; the unknown is service match, because the described problem might be a design issue your service does not cover. One two-line email asking them to describe the outcome they want resolves it cheaply. If the answer confirms fit, proceed; if not, decline with a referral to a better-suited provider. The clarify pile exists precisely so that ambiguous leads get one cheap, honest question, not a speculative hour.
Case C, decline. A startup wants a full service engagement at a budget a tenth of your floor, needed yesterday. The decline is polite, immediate, and useful: a short explanation of the mismatch and, where you can, one referral or one resource that actually fits their size. Declining well is a reputation act; the startup that was declined honestly this year remembers the referral, not the no.
Log every decision with its worksheet state. A declined lead whose must-have was budget recurs in your numbers as a pattern only if the decline was recorded with a reason.
The Consistency Test
Before the checklist touches a real lead, run it on paper cases.
- [ ] Same Rulings: Three team members rule identically on five fictional cases spanning proceed, clarify, and decline.
- [ ] Written Gates Only: Every decline traces to a named must-have, never to a mood or a hunch.
- [ ] Context Contained: No case was declined on pile-two facts alone.
- [ ] Unknowns Ordered: Clarify actions name the cheapest resolution first.
- [ ] Decisions Owned: Each case names the human who decided; the worksheet names a decision owner per lead, not a committee.
- [ ] Declines Reasoned: Every fictional decline has a one-line reason that would make sense in next month's numbers review.
Failures in the consistency test point at wording, not at people. If two people rule differently, the must-have sentence is ambiguous; rewrite it until a stranger could apply it.
Operating Protocol: Write, Test, Review
- Write the must-haves before the next booking link is shared. The checklist exists to gate the calendar; deployed after the calendar, it gates nothing.
- Re-review monthly using the decline log. The recorded reasons are your tuning data: too many declines on one gate means the gate or the marketing targeting is wrong, and either fix is now visible instead of anecdotal.
- Amend formally. When a must-have changes, the sentence is rewritten, versioned, and re-tested on the fictional cases. Silent drift back to per-person judgment is the failure mode to guard against forever.
A short, written, consistently applied lead qualification checklist is not bureaucracy. It is the mechanism that keeps senior hours pointed at buyers who can actually be served, keeps your aggregate numbers meaningful, and makes every decline a small act of reputation building rather than a wasted hour.
Reader signal