Skip to content

Qualify & Follow Up UK & US

How to Qualify a B2B Services Enquiry

Qualify a B2B service enquiry using fit, need, timing and delivery constraints. Separate unknowns from poor fit and record a clear next action.

Qualification should end with a defensible next action. For a small service business, that means deciding whether to progress, ask a useful question, defer to an agreed date or close a request you cannot fulfil. It does not require a score that pretends to predict a stranger’s value.

Use this guide when you are dividing limited time between incoming enquiries and proposals. By the end, you should have a reason, an owner and a dated action for one enquiry. The free qualification workbook provides a blank form and three fictional examples.

Define fit before you score

Write down what you can deliver before judging the enquiry. Use five practical checks: the service requested, the outcome sought, delivery location or model, available capacity and any essential commercial constraints. A confirmed requirement for on-site support can rule out a remote-only provider. An unfamiliar company name cannot.

Distinguish a business requirement from a preference. A minimum project size may be a policy you choose; it is not a universal definition of a good lead. Record who set it, why it exists and whether exceptions are allowed.

Common qualification frameworks organise questions about need, budget and decision making. Salesforce’s qualification training explains such frameworks; it does not validate this worksheet or turn a score into a win probability. Our recommendation is to use the smallest set of criteria needed for your next decision.

Ask for the next piece of useful information

Start with the buyer’s actual request and its source date. Summarise what is confirmed in plain language. Then identify the most important unknown: scope, trigger, timing, approval process or a delivery constraint.

For example, a fictional UK website enquiry says, “We need new service pages for a January launch.” The service appears to fit, but the exact launch date, scope, spending range and approver are unknown. A useful reply might be:

What needs to be different about the service pages at launch? Is there an agreed spending range, and who will review the scope with you?

That is a fictional wording example, not a prescribed email sequence. You can ask about timing next if the first answer shows a feasible project. A long questionnaire is not always necessary before a human reply.

If the buyer cannot give a budget, explain a relevant scope range from your own real offering when appropriate. Do not invent a market price. “Unknown” is different from zero, refusal and a confirmed mismatch.

Separate missing information from poor fit

Use separate fields for evidence, seller assumptions and missing information. “Buyer requested January” is evidence. “They probably need a full rebrand” is an assumption. “Launch day unknown” is a missing fact. Mixing them makes an uncertain request look more qualified than it is.

A lack of response does not establish why the buyer went quiet. If you eventually close the record administratively, use a label such as “No decision; reason unknown.” Keep a buyer-stated reason separate from your interpretation.

A contact and an opportunity are different records. Several people may participate in one purchase. Marketing-qualified and sales-qualified labels mean whatever the organisation has defined them to mean. HubSpot’s lifecycle documentation illustrates one product’s conventions; your team’s explicit progression rules still matter.

Decide: progress, clarify, defer or close

The following cases are fictional. They demonstrate decisions, not measured sales outcomes.

SituationDecisionEvidence and next step
A buyer has confirmed the service need, feasible timing and an agreed proposal-review meetingProgressPrepare the agreed scope for that meeting. Confirm the reviewing people and date.
A website project fits provisionally, but scope and approval are unknownClarifySam asks the two immediate questions on 29 Oct 2026, 14:00 Europe/London.
A US operations project is paused and the buyer requested a January check-inDeferAlex reviews and sends the requested check-in on 12 Jan 2027, 10:00 America/New_York. Reconfirm scope then.
On-site Chicago coverage is essential and the provider supplies remote consultancy onlyCloseExplain the specific mismatch. Record the closure and any appropriate reopening condition.

Progress does not mean “send a proposal regardless.” You may progress to a short discovery conversation. Defer needs a review trigger rather than indefinite automated chasing. Close should not depend on collecting further personal data that cannot change the decision.

Record the reason and next step

Use an internal reference, receipt date, delivery market, time zone and currency. Add the need, fit constraints, timing, commercial constraints and buying process. Reference the original message instead of duplicating unnecessary personal details.

Then record the decision and its evidence, one responsible owner, the next action and its due date. For a deferred request, specify what you will reconsider. For a closed request, record a reason and complete any promised closure message. The Excel sheet does not send reminders: set one in your calendar or CRM.

Review active and deferred records weekly. Check whether the next action still follows from current evidence. A change of owner needs an explicit handover; a record saying “sales team” does not identify who will act.

UK and US: a requested reply is not blanket marketing permission

Use explicit local times and location-based time zones for appointments. UK and US clock changes can occur on different dates; confirm the shared calendar invitation rather than relying on a fixed hour difference.

In the UK, ICO B2B marketing guidance distinguishes corporate and individual subscribers under PECR; sole traders and some partnerships receive different treatment. UK GDPR also matters when personal data is processed. Scottish partnerships are included in the ICO’s corporate examples. The ICO flags the guidance as under review after the Data (Use and Access) Act.

In the US, the FTC’s CAN-SPAM guide covers commercial email including B2B; the message’s primary purpose matters. These sources do not settle state privacy rules or the rules for telephone and SMS. A buying enquiry is not permission to add someone to an unrelated newsletter.

This is a practical workflow, not a legal review or an automated decision system. Avoid sensitive characteristics and unnecessary personal data. Qualification evaluates the service request and delivery constraints, not a person’s worth.

Put one enquiry through the workflow

Download the Lead Qualification Sheet, complete the evidence and missing-information fields, and choose one action. If you need software to keep owners and deadlines visible, use the CRM Selection Checklist before the three-person CRM comparison.