Separate an enquiry from an opportunity
A form submission means someone has contacted you. It does not automatically mean the service fits their needs, timing or budget. Qualification is the conversation that helps both sides establish whether there is a useful next step.
Salesforce describes sales pipelines as a sequence of stages that can be adapted to the business. For a small service company, our proposed starting point is deliberately simple: new enquiry, contacted, qualified, proposal, won or closed. Add a stage only when it represents a meaningful change or action.
Give every lead a responsible person
Keep enquiries in a shared record rather than scattered across personal inboxes. Record the name, contact method, service requested, source, owner, status and next action date. Store only information needed for the conversation and restrict access to the people who need it.
Agree a realistic response routine during working hours. Do not publish a response-time promise that your team cannot meet. An automatic acknowledgement can explain that a request arrived, but should not be mistaken for a real conversation or a qualified opportunity.
Ask questions that establish fit
Begin with what the person wants to achieve and why it matters now. Clarify the work, timing, location when relevant and the decision process. Discuss budget in the context of the scope, rather than using it as the only reason to continue or dismiss a conversation.
- What needs to change, and what have you already tried?
- Which service or outcome are you looking for?
- When would you like to move forward?
- Who needs to be involved in the decision?
If there is no fit, say so clearly. A polite explanation or a suitable referral is better than keeping an unsuitable lead in the pipeline indefinitely.
Make the first reply useful
Here is an illustrative reply: “Hello Alex, thank you for your enquiry about the website. To understand the project, could you tell us what the site needs to do and when you would like it ready? We can then arrange a short conversation about the scope.”
Adapt it to information already supplied. Asking the same questions again makes a reply feel automated. Keep one clear action in each message and use the contact method the person has requested where possible.
Agree the next step before ending the conversation
After a meeting, summarise the problem, proposed scope, open questions and next action. A proposal should make responsibilities and exclusions clear. “I will send the revised scope on Tuesday, and we will review it on Thursday” is more actionable than “We will be in touch”.
Follow up with a reason: an answer to an open question, a clarification or an agreed review date. If there is no response, avoid an endless sequence of reminders. Ask whether the project is still relevant and respect a request to stop contact. Record why an opportunity closes so that marketing can learn from it.
Review the handover between marketing and sales
Track the number of enquiries, qualified opportunities, proposals and wins for a consistent period or cohort. Ten wins from 50 qualified opportunities is a 20% opportunity-to-sale rate in an invented example. It is not the same calculation as ten wins from all website visits.
Review lost reasons as well as conversion. If many people want a service you do not offer, improve the page or advert. If proposals stall because scope is unclear, improve the sales process. More leads are useful only when the business can respond, qualify and deliver.
Sources & further reading
Practical guidance by Hust. Hypothetical examples are labelled; no original research study is claimed.