A Customer Success Qualified Lead (CSQL) is an expansion opportunity inside an existing account that a CSM has flagged as ready for a commercial conversation — an upsell, cross-sell, seat add, or tier upgrade — and handed to the revenue team to close. It is the CS-sourced equivalent of an MQL: a lead that has cleared a defined bar and earned a sales follow-up. The defining trait is origin. A CSQL comes from the post-sale relationship — usage signals, a roadmap conversation, a new stakeholder, a stated need — not from a marketing campaign or an SDR’s outbound sequence.
What a CSQL is not
A CSQL is not a renewal. Renewal is the baseline contract continuing; a CSQL is incremental ARR on top of it. Conflating the two lets teams claim expansion credit for revenue that was already going to recur.
A CSQL is also not a raw product signal. A spike in seat utilization is an input to a CSQL, not the CSQL itself. The lead exists only once a human (the CSM) or a calibrated scoring model has judged the account both able and willing to buy more, and has named the specific motion. “This account is at 95% of licensed seats” is a signal; “this account needs 40 more seats before their Q3 onboarding wave and the champion has confirmed budget” is a CSQL.
And a CSQL is not an MQL or an SQL. An MQL is a contact who engaged with marketing; an SQL is a net-new prospect sales has accepted. A CSQL is an existing customer the CS org knows by name. The qualification evidence is operational reality, not form fills.
The qualification criteria
A workable CSQL definition gates on three things, all required:
- A product or relationship signal. Seat utilization over a threshold (commonly 80-90% of licensed seats), a feature-gate hit, a new department onboarding, a stated need in a QBR, or a new senior stakeholder appearing in the account.
- Account health that supports expansion. Selling more into an unhealthy account accelerates churn. Gate the CSQL on a healthy or improving health score, current on payments, and no open critical support escalation.
- A named motion and a champion. The CSM names what is being sold (seats, module, tier) and identifies who inside the account will sponsor it. Without these two, sales inherits a hunch, not a lead.
Write the definition down and version it. A CSQL that means something different to CS than it does to sales produces attribution fights and a conversion rate nobody trusts.
The handoff to sales
Decide who closes before you generate the first CSQL. Three common models: the CSM closes small expansions directly (fastest, but pulls CSM time from retention); an Account Manager or expansion AE owns all CSQL-to-close (cleanest separation); or a hybrid where the CSM closes under a dollar threshold and routes larger deals. Pick one and instrument it.
The handoff itself is a structured record, not a Slack message. Capture it as a stage in the CRM or a CS platform like Gainsight or Planhat: the signal that triggered it, the named motion, expected ARR, the champion, and a health snapshot. Define an SLA — the receiving rep accepts or rejects within a set window (48-72 hours is typical) — and a rejection reason taxonomy so CS learns which CSQLs convert and which were premature.
Attribution
CSQL attribution is where the model earns or loses trust. Track three rates: CSQL-to-accepted (did sales agree it was real), accepted-to-closed-won, and CSQL-sourced ARR as a share of total expansion ARR. If CS gets credit for influence and sales for the close, double-counting inflates both numbers; agree on a single sourced-versus-influenced rule up front. Most teams credit CS as the source and the closing rep with the win, reported on separate lines so neither org games the other’s number.
Common pitfalls
- Defining CSQL only on usage. A utilization threshold with no health gate and no champion floods sales with leads that don’t convert. Guard: all three criteria required, every time.
- No rejection loop. Without a rejection-reason taxonomy and a feedback path back to CS, the bar never calibrates. Guard: make accept/reject with a reason a required CRM field, reviewed monthly.
- Counting renewals as CSQLs. Inflates expansion metrics and hides flat accounts. Guard: CSQL ARR is incremental only — renewal baseline is excluded by definition.
- CSM time crowded out by closing. If CSMs own the close, retention work quietly suffers. Guard: cap CSM-closed deals by dollar value and route the rest to an AM.
Related
- NRR vs GRR — CSQL pipeline is what drives the expansion term in NRR