The MQL debate needs an acceptance record
A recorded acceptance decision makes lead-quality disputes inspectable. It is a signal, not a complete diagnosis of demand performance.
A common lead-quality dispute starts this way: marketing hits the MQL target, sales says the leads are weak, and neither side can produce a consistent disposition record. One side suspects poor follow-up; the other suspects loose qualification. Without record-level evidence, both explanations remain plausible.
One missing event is often the seller’s acceptance or rejection decision and its reason. Recording it narrows the investigation. It does not, by itself, settle whether the scoring rule, routing, seller capacity, response time, or data quality caused the result.
Acceptance closes the loop
A sales accepted lead is an MQL that a seller has explicitly accepted as workable. Explicitly means an affirmative act on the record, and rejection requires a structured reason: wrong segment, no authority, no timing, duplicate, competitor, existing customer.
The field produces a reason-code distribution. Suppose, hypothetically, that 40% of rejections are coded "wrong segment." That is a signal to inspect ICP mapping, routing, seller interpretation, and reason-code quality; it is not proof that the scoring model alone caused the mismatch. The same discipline applies to "no timing" and "duplicate" outcomes.
The rate is one signal
Cohort MQL-to-SAL conversion is useful beside time to disposition, rejection-reason mix, and downstream outcomes. It can move because of scoring, segment mix, routing, seller capacity, response time, training, territory changes, or data hygiene. Rising volume with a falling rate is a prompt to inspect those mechanisms, not definitive evidence of one cause.
Acceptance is reciprocal
An MQL is a handoff, and the handoff contract should name the receiver’s obligation: work the record within a defined window and dispose of it with a reason. Without adoption and monitoring, the acceptance field may remain incomplete and the new metric will inherit the old ambiguity.
Ship the SLA and definition together: one specifies what qualifies, the other what the receiver owes in response. Then audit completion and compare reason codes with downstream conversion. The pair creates an inspectable handoff; it does not guarantee lead quality or seller compliance.
Terms used in this note
Write the stop rule before the pilot starts
A market-entry pilot with no decision rule written before exposure cannot end. It gets extended until it is the default motion, without anyone choosing that.
Your pricing is a list, not a logic
A price list says what things cost today. It cannot say what to charge the deal in front of you, which is why realised price drifts and nobody owns the drift.
You just inherited RevOps. Start with a charter.
Being told to "own revenue operations" is not a mandate. Until authority is written down, every decision you make is reversible by whoever objects loudest.