The formula and the cohort rule
SAL to SQL rate equals SQLs divided by SALs in the same cohort, times 100. The cohort part matters more than the arithmetic. Leads take days or weeks to qualify, so counting this month's SQLs against this month's SALs compares two different populations. Tag every accepted lead with its acceptance date, then measure how many of that group reached qualified status within a fixed window, such as 30 or 60 days. Use the same window every time or the trend is meaningless.
Why this rate is the honest one
Acceptance is a judgment call, and judgment calls drift. A rep under quota pressure accepts more leads at the start of the quarter and fewer at the end. That drift distorts MQL acceptance rate and every rate that includes it. SAL to SQL sits downstream of the judgment, so it answers a narrower question: once a rep committed to work this lead, did the lead turn out to be real?
Two failure patterns produce a low rate, and they need different fixes.
- Accepting too generously. Reps take everything to avoid an argument with marketing, then quietly ignore half of it. Acceptance rate looks strong, SAL to SQL collapses, and the real qualification bar has just moved downstream where nobody measures it. - Working too thinly. Reps accept good leads and touch each one twice before moving on. The leads were qualified. Nobody stayed long enough to find out.
Pull touch counts on unconverted SALs to tell the two apart. Leads dropped after only a touch or two point at coverage. Leads worked hard and still dead point at the acceptance criteria.
Reading the rate against pipeline
A rising SAL to SQL rate with flat SQL volume means the team is being more selective, not more effective. Watch qualified pipeline dollars alongside the percentage, because a team can improve every conversion rate in the funnel by simply working fewer leads.
Segment by lead source before you act on any of this. Sources rarely convert alike, and a blended rate hides which channel is carrying the funnel. Once you know the rate by source, top-of-funnel volume becomes a real input to sales forecasting instead of a vanity number, and your view of pipeline coverage reflects what will actually reach a rep.
Frequently Asked Questions
How do you calculate SAL to SQL conversion rate?
Divide the number of leads that reached sales qualified status by the number of sales accepted leads created in the same cohort, then multiply by 100. Measure by cohort rather than by calendar month. If you count SQLs created in June against SALs created in June, you mix leads at different ages and the rate moves for reasons that have nothing to do with quality.
What is a good SAL to SQL conversion rate?
There is no cross-industry number worth targeting, because the rate depends entirely on how strict your acceptance criteria are. A team that accepts almost everything will show a low rate, and a team that accepts only pre-vetted leads will show a high one. Compare against your own trailing four quarters and segment the rate by source and by rep.
What does a falling SAL to SQL rate mean?
It usually points at execution rather than lead quality, because the lead already cleared the acceptance bar. Look at time to first touch, touch count before the lead is dropped, and whether reps are working the queue in order. A sharp drop concentrated in one team or one segment is almost always a coverage or capacity problem.
Should SAL to SQL be owned by marketing or sales?
Sales owns it. Marketing owns everything through acceptance, and once a rep accepts the lead the outcome depends on how it gets worked. Splitting ownership at the acceptance line is what makes the two rates diagnostically useful, because a problem in one points at a different team than a problem in the other.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like sal to sql conversion rate into prescriptive action for your team.
Schedule a Demo