What the rate actually measures
SQL-to-opportunity conversion is the first real test of pipeline creation quality. An SQL that does not become an opportunity was either not actually qualified or was not worked effectively. Either way, it is a pipeline creation failure.The rate is calculated as:
``` SQL-to-opportunity rate = Opportunities created / SQLs received × 100 ```
Measure it over a consistent period, typically monthly or quarterly, and track it by source, rep, and segment. A blended rate hides the real story. An enterprise rep converting 30 of 40 SQLs looks very different from an SMB rep converting 20 of 100.
What different rates signal
The table below shows diagnostic logic, not external benchmarks. Use your own historical baseline as the target. The rate ranges are illustrative starting points for building an internal framework.
| Rate range (illustrative) | Likely diagnosis |
|---|---|
| Very low (e.g., below 30%) | SQL definition is too loose or reps are not working leads |
| Low (e.g., 30% to 50%) | Below internal target, investigate source quality and follow-up SLAs |
| Mid-range | Healthy for many B2B motions, validate against your own history |
| High | Strong, verify volume is not being sacrificed for selectivity |
| Very high (e.g., above 85%) | SQL bar may be too restrictive, review definition |
Diagnosing a low rate
A low SQL-to-opportunity rate usually has one of three root causes.
The SQL definition is too permissive. If marketing or an SDR team is marking leads qualified based on firmographic fit alone, without behavioral or intent signals, many of those leads will not convert. Tighten the definition to require a minimum activity threshold alongside fit criteria.
Follow-up speed is too slow. Conversion rates drop sharply when qualified leads go uncontacted. Build an SLA for first contact after SQL creation and track it alongside the conversion rate. The two move together.
The ICP has drifted. If the accounts you are qualifying no longer match the segment your product closes well in, the conversion rate will reflect the mismatch before your win rate does. Use a low SQL-to-opportunity rate as an early warning signal for ICP drift.
Connecting to pipeline health
SQL-to-opportunity conversion is the entry point for pipeline conversion rate analysis. Fixing conversion at this stage has compounding effects downstream because every additional opportunity created at acceptable quality feeds all subsequent stage conversions. Review it alongside MQL vs SQL definitions to ensure your hand-off criteria are generating real pipeline, not activity volume dressed up as pipeline. High sales qualified lead volume with a low conversion rate is a cost, not a win.
Frequently Asked Questions
What is a good SQL-to-opportunity conversion rate?
There is no universal number. The right benchmark is the one your team establishes from its own historical data, segmented by source, motion, and ACV band. A rate that drops significantly from your own baseline is the signal worth acting on. When diagnosing a low rate, start with the SQL definition and follow-up speed before comparing against external figures.
What causes a low SQL-to-opportunity rate?
Two causes dominate. First, the SQL definition does not match real buyer intent. If any lead with a job title match is called qualified, volume will be high but conversion will be low. Second, rep follow-up is too slow. Response time to inbound intent is a documented conversion factor: the faster a qualified lead is contacted, the more likely it advances. If your SQLs go uncontacted for an extended window after creation, the rate will drop regardless of lead quality.
How is SQL-to-opportunity different from MQL-to-SQL?
MQL-to-SQL measures the hand-off between marketing and sales: how many marketing-qualified leads does sales accept? SQL-to-opportunity measures what happens after sales accepts: how many SQLs does the rep convert into a live, staged opportunity? Both matter, but they diagnose different problems. Low MQL-to-SQL points to misalignment between marketing and sales on definitions. Low SQL-to-opportunity points to rep execution or lead quality after the hand-off.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like what is a good sql-to-opportunity conversion rate? into prescriptive action for your team.
Schedule a Demo