Sales Qualified Opportunity (SQO): The Metric Most B2B Dashboards Get Wrong

Open ten different B2B revenue dashboards and there's a fair chance you'll find ten different definitions of "opportunity." Some count anything sales has logged in the CRM. Others count every SQL automatically. Very few apply a consistent, defensible standard for what actually earns a deal a place in the pipeline. That inconsistency is exactly why SQO, as a metric, is so often reported wrong.

Sales Qualified Opportunity: The Quick Answer

A Sales Qualified Opportunity (SQO) is a deal that sales has formally qualified as a genuine, resourced opportunity worth actively pursuing, based on confirmed budget, authority, need, and timeline, and that has been logged in the CRM with an assigned value, stage, and close date.

An SQO is not the same as an SQL. An SQL confirms that a lead is worth a sales conversation. An SQO confirms that the conversation has happened and the deal is real enough to forecast against. Every SQO should have originated as an SQL, but not every SQL becomes an SQO — some are disqualified during that first proper sales conversation once budget, timeline, or authority turns out not to be there.

Why This Gets Confused with SQL So Often

The two metrics sit right next to each other in the pipeline and are often collapsed into one step, particularly in smaller sales teams without a formal CRM discipline. The practical difference is what each one commits an organisation to. An SQL is a judgement that a lead is worth pursuing. An SQO is a commitment: sales resource is now allocated to actively working this deal, and it's forecast as part of revenue projections.

Reporting SQLs as though they were SQOs inflates forecast reliability in a way that eventually catches up with the business. Deals that were never properly qualified sit in the pipeline looking like real revenue until they quietly stall or go dark, at which point forecast accuracy collapses and the finance team stops trusting the sales dashboard altogether.

The Four Qualification Criteria Behind a Genuine SQO

Most SQO definitions are built around some version of BANT, though more complex enterprise sales organisations often use fuller frameworks such as MEDDIC.

Budget confirms the prospect has, or can access, the funds required, and that the deal size is realistic against what they've indicated they can spend. Authority confirms the primary contact either has decision-making power or has a clear path to the people who do, since a deal with no line of sight to the actual buying committee is not a qualified opportunity regardless of how enthusiastic the initial contact is. Need confirms the prospect has a specific, articulated problem your solution addresses, rather than a vague interest in "exploring options." Timeline confirms there's a defined window in which a decision will be made, since an opportunity with no timeline tends to sit in the pipeline indefinitely, dragging down average sales cycle length and distorting every other pipeline metric calculated against it.

An SQO should only be logged once all four are reasonably confirmed, not once a discovery call has simply taken place.

Why Most Dashboards Get This Wrong

The most common error is auto-converting every SQL into an SQO the moment a sales rep books a first call, regardless of what that call actually reveals. This inflates the pipeline with deals that were never properly qualified and that later get marked as lost, which distorts win rate, pipeline velocity, and forecast accuracy all at once, since each of those metrics depends on the SQO count being accurate in the first place.

The second common error is inconsistent qualification standards across reps. Without a documented checklist, one rep's SQO is another rep's still-being-qualified lead, which makes pipeline data unreliable the moment it's aggregated across a team, even if each individual rep is applying reasonable judgement.

The third error is failing to disqualify deals that stop meeting SQO criteria. A deal that loses its timeline, or where the champion leaves the company, should be marked as lost or moved back a stage rather than left sitting in the pipeline at its original value, quietly inflating forecast numbers that finance and leadership are relying on.

How to Fix SQO Reporting

Fixing this starts with writing the qualification checklist down as something explicit, rather than leaving it as an informal judgement call each rep applies differently. That checklist should map directly to required fields in the CRM, so a deal genuinely cannot be logged as an SQO without budget, authority, need, and timeline all being recorded against it.

It also requires regular pipeline hygiene reviews, where stalled or unresponsive opportunities are reassessed and either disqualified or reconfirmed, rather than left to accumulate as dead weight in the pipeline. Many B2B organisations find that a significant share of their "open" pipeline at any given time no longer meets SQO criteria at all, and simply hasn't been cleaned up.

Finally, SQO conversion rate — the percentage of SQLs that become genuine SQOs — is worth tracking as its own metric. A declining SQO conversion rate is one of the clearest early indicators that lead quality earlier in the funnel is slipping, often before that shows up anywhere else in the pipeline data.

Why Getting SQO Right Changes What Leadership Sees

Once SQO is defined and applied consistently, forecast accuracy improves immediately, because the number of deals in the pipeline reflects genuine, qualified opportunities rather than a mix of real deals and hopeful conversations. It also makes every downstream metric more trustworthy. Win rate, pipeline velocity, and average deal size are all calculated using SQO as an input, so cleaning up this one definition has a compounding effect on the reliability of the entire revenue dashboard.

How Digital Squad Can Help

Getting SQO reporting right depends on the systems behind it being connected and consistently applied, not just the definition being written down somewhere.

Digital Squad supports this through data analytics, building dashboards that connect CRM data to marketing and campaign performance so SQO conversion rates and pipeline hygiene issues are visible rather than buried in spreadsheets. We also support this through marketing automation, ensuring the lead scoring and routing that feeds SQLs into sales is consistent enough that qualification standards can actually be applied fairly across a team, and through content marketing, developing the sales enablement material, such as case studies and proposal content, that helps reps confirm need and authority earlier and more reliably during qualification conversations.

If your pipeline data doesn't hold up under scrutiny once finance starts asking questions,get in touch for a discovery session with our team.

FAQs

Is an SQO the same as a sales opportunity in the CRM?

It should be, but only if the CRM enforces the qualification criteria behind it. Many CRMs allow any deal to be logged as an opportunity regardless of whether budget, authority, need, and timeline have actually been confirmed, which is where the metric breaks down in practice.

What's a healthy SQL to SQO conversion rate?

This varies significantly by industry and deal complexity, so there's no universal benchmark. What matters more is tracking the rate consistently over time and investigating any sustained decline, since that usually signals a lead quality issue further up the funnel.

Should marketing or sales own the SQO definition?

Sales should own the final qualification decision, since they're the ones committing resource to the deal, but the criteria should be agreed jointly with marketing so both teams are working from the same standard when reviewing pipeline health together.