'Low-quality leads' with no shared definition of quality

'Low-quality leads' with no shared definition of quality

The most common friction in partner-sourced lead programs isn't bad leads — it's the absence of an agreed definition of 'good.' Sales calls partner leads weak; partners call sales lazy; neither has written down the rubric they're arguing about.

Why the vacuum is costly:
— Without a shared standard, lead rejection becomes subjective and political. Reps reject leads that are inconvenient, not unqualified.
— Partners can't improve targeting because rejection feedback is vague ('not a fit').
— Disputes consume partner-manager time and poison the relationship.

The fix — codify a joint qualification standard before launch:
— Write an explicit rubric: firmographic thresholds, required intent signals, and a budget-authority-need-timeline floor.
— Build a structured rejection-reason taxonomy so every rejected lead returns an actionable code, not a shrug.
— Review acceptance rates and rejection reasons together monthly; treat persistent disagreement as a rubric defect, not a partner defect.

Caveat: overly rigid rubrics reject good edge-case leads. Build an exceptions lane and review overridden rejections to refine the standard.

Open question: if you asked your top partner and your top rep to define a 'qualified lead' separately, how far apart would the two answers be — and have you ever checked?