A new enquiry sounds promising, so someone offers a start date. Only afterwards does the team discover that the client needs a service you do not provide, using access you cannot obtain.
Service enquiry qualification establishes whether the requested outcome fits your offer and what must be known before a responsible next step can be agreed. It is a human business decision, not a judgement that every uncertain enquiry should be rejected.
Photo by Aleksei Zhivilov on Unsplash.
Start with the client’s operational problem
Ask what is happening now, who it affects and what the client wants to change. A request for a tool or named deliverable may conceal a different underlying need. Keep their description alongside your interpretation so the team can check it.
Separate the decision to investigate from the decision to deliver. A bounded discovery conversation may be appropriate when the problem is unclear. It should not imply acceptance of the eventual assignment.
Use an enquiry decision card
Requested outcome and business reason.
Relevant service and any clear mismatch.
Expected timing and reason for the date.
People able to provide information and approve decisions.
Important constraints, access needs and dependencies.
Missing information that changes the next decision.
Fit decision: proceed to scoping, clarify, refer or decline.
Owner, next action and what the client has been told.
Do not collect a large document pack merely to appear thorough. Ask for enough information to make the next decision and explain why sensitive material needs an approved route.
An illustrative request for urgent automation
A founder asks for a system to remove client onboarding admin immediately. Qualification reveals conflicting handoff rules and no agreed owner of the client record. The useful next step may be a workflow review rather than a promise to implement automation that week.
The owner explains the narrower investigation and identifies who must participate. Your requirements approach can help translate a product request into a clear operational outcome before a supplier or tool is selected.
Keep authority visible at the commercial boundary
A helpful conversation should not become an informal contract assembled from enthusiastic messages. Use the appropriate commercial owner for price, terms and consequential promises. The coordinator can record the question and describe the agreed scoping route.
Check usable commitment capacity before offering a delivery slot. Apparent interest and a plausible service fit do not establish that the necessary people are available.
Make a decline useful
When the request is unsuitable, explain the boundary accurately and, where appropriate, suggest the kind of help needed without inventing a referral relationship. Keep any future follow-up consistent with what the client agreed.
If enquiries move straight from a friendly reply to an unsupported promise, Hili Consulting can help define qualification and scoping decisions that protect delivery.
