The SQL-to-SAO gap is where revenue team alignment breaks down
An SQL is a marketing claim; an SAO is a sales decision. The gap between those two moments is where SLA failures, attribution disputes, and pipeline quality problems originate.SQLs are leads that cross a threshold marketing has defined. That threshold might be based on a lead score, a behavior like requesting a demo, or a firmographic match against an ICP profile. When a lead crosses that threshold, marketing considers it handed off.
SAOs are what happens after the rep actually looks at the lead. The rep reviews it, decides it is worth pursuing, and formally accepts it into their pipeline as an opportunity. If the rep rejects it, it should not count toward pipeline.
The four states a lead can be in after SQL
| State | Meaning |
|---|---|
| SQL, not yet reviewed | In the handoff queue, no rep action taken |
| SQL accepted = SAO | Rep reviewed and committed to work it |
| SQL rejected | Rep reviewed and decided it does not meet their working threshold |
| SQL expired | Aged out without rep action, which is itself a problem |
Why you need both in your funnel reporting
Tracking only SQLs means measuring marketing's output against marketing's own criteria, with no visibility into whether sales considers it usable. Tracking only SAOs drops the funnel stages before the handoff entirely.
The correct motion is to track the full sequence: MQL, SQL, SAO, and Closed Won. Each conversion rate between those stages is a diagnostic: MQL-to-SQL measures lead scoring accuracy, SQL-to-SAO measures handoff quality, and SAO-to-close measures sales execution on qualified pipeline.
Defining the SLA between SQL and SAO
The SLA should specify three things: the criteria that constitute an SQL, the criteria that constitute an SAO, and the expected time between SQL creation and rep review. Without the time component, an SQL can sit in a queue for two weeks before a rep rejects it, which inflates pipeline figures and frustrates buyers.
The sales accepted lead definition and the MQL vs SQL distinction should both be documented and agreed upon before either metric appears in a revenue dashboard. Disagreement at the definition level surfaces as noise in the data.
Frequently Asked Questions
What is the difference between an SQL and an SAO?
An SQL is a lead that marketing has qualified as meeting the defined criteria for sales follow-up. An SAO is a lead that the sales rep has reviewed, accepted, and agreed to work as a real opportunity. SQLs are a marketing output; SAOs are a sales commitment.
Why is the SQL-to-SAO conversion rate important?
The SQL-to-SAO rate is the direct measure of lead quality from marketing's perspective. A low rate signals that marketing is sending volume that sales does not consider workable, which points to a disconnect in ICP definition, qualification criteria, or lead scoring thresholds.
Who is responsible for defining SQL and SAO criteria?
SQL criteria are typically owned by marketing, often in collaboration with sales. SAO criteria are owned by sales. The SLA between the two teams should specify both thresholds, the expected follow-up window, and what happens when a rep rejects an SQL.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like sql vs sao into prescriptive action for your team.
Schedule a Demo