Turn lead-quality disagreements into working agreements

Break one broad label into distinct stages

Ask each team what it means by a lead. If marketing counts all forms while sales counts opportunities with confirmed requirements, the totals answer different questions. Separate the states you need to monitor, such as enquiry received, initial criteria met, accepted by sales, and need confirmed through a conversation.

For every state, write the evidence required and the person responsible for the decision. Avoid phrases such as sufficiently interested without an explanation. Use language people can apply to real examples. The stage names do not have to follow a particular framework as long as everyone understands when a status changes and why.

• What must happen before an enquiry enters this stage?
• Which information shows that the condition is met?
• Who updates the status and handles the next action?

Make rejection reasons useful to the next decision

Poor quality is too broad to help someone improve a campaign. Separate unrelated needs, locations outside service coverage, missing information, later timing, and difficulty making contact. Those reasons may require different actions. Leave room for a short explanation when a case does not fit the usual categories instead of forcing an inaccurate label.

Planning example: a B2B service team in Jakarta receives enquiries from suitable companies, but some ask for work outside its offer. Those cases suggest reviewing the service explanation. Other prospects simply have later project timelines. Keep the groups separate so a delay does not cause the team to reject the entire segment.

Connect the measures and preserve ownership

Show movement between stages by source and time period. Marketing can examine account relevance and message clarity, while sales brings evidence of acceptance and buyer needs. Shared measures do not mean everyone owns every outcome. Write down the work each side controls so an agreed improvement has a person capable of carrying it out.

Consider the sales cycle when comparing campaigns. New enquiries have not had the same evaluation time as older groups. Comparing their final outcomes without that context can create a misleading picture. Where the sample is small, state the limitation and use examples to understand the process rather than declaring a broad performance trend.

• Source and entry date give the comparison context.
• Defined stages make the numbers interpretable.
• An accountable owner makes the improvement actionable.

Close the review with a testable change

Keep the agenda focused: a change that needs explaining, conversation examples that illuminate it, and possible actions. Include accepted enquiries as well as declined ones. Check whether the problem lies in audience selection, page information, opening questions, or response handling before settling on a solution based on who raised the complaint.

Record the decision, owner, and evidence to review next. For example, clarify a service boundary on the page and examine the types of questions that follow. Avoid changing everything at once if the team wants to understand the effect. Revisit previous decisions before turning the next meeting into a new list of tasks.