When Is a Lead Sales-Ready? A RevOps Lead-Scoring Framework for B2B Teams

"Sales-ready" is one of the most argued-over words in a B2B business. Marketing thinks a lead is ready the moment it fills in a form. Sales thinks half the leads it gets are a waste of time. Both are usually right, because most teams have never written down what sales-ready actually means and then built that definition into the CRM. It lives in people's heads, so it changes depending on who is having the conversation.

A sales-ready lead is one that has been qualified and scored against agreed criteria, then passed to sales at the point where a direct conversation is likely to convert. The hard part is not the definition. It is making the definition objective, measurable and automatic, so a lead crosses the threshold the same way every time regardless of who is looking at it. That is a RevOps configuration problem, not a sales motivation problem.

The four signals that decide if a lead is sales-ready

A reliable threshold combines four dimensions. Score each one, weight them against your own conversion data, and you get a defensible answer rather than a gut feel.

1. Fit: do they match your ICP?

Fit is the firmographic and demographic match between the lead and your ideal customer profile. For a mid-market B2B business that usually means company size, revenue band, sector, region and the seniority of the contact. A perfect-fit account that has done very little is often a better use of sales time than a poor-fit account that has read every blog post. Capture fit data at the point of conversion and enrich what you can, so you are not relying on a prospect to self-report their headcount accurately.

2. Interest: are they paying attention?

Interest measures engagement with your content and channels: email opens and clicks, repeat site visits, content downloads, webinar attendance and social engagement. On its own interest is a weak signal, because anyone can open an email. It becomes useful when it accumulates and when it points at high-intent assets such as pricing or comparison pages.

3. Behaviour: what are they actually doing?

Behaviour is the set of specific actions that correlate with becoming a customer. Visiting a pricing page, requesting a demo, returning to a product page several times in a week, or replying to a sales sequence are all worth far more than a single newsletter open. The way to find these signals is to look back at closed-won deals and ask which actions reliably preceded them. Those actions, not your assumptions, should carry the most weight in your model.

4. Journey stage: where are they in the buying process?

The same action means different things at different stages. A pricing-page visit during awareness is curiosity. The same visit after two sales calls is a buying signal. Mapping leads to awareness, consideration or decision stops you from passing an early-stage lead to a closer who will burn the relationship, and stops you from nurturing a decision-stage lead who wanted to talk to someone today.

Turn the threshold into an MQL-to-SQL handoff

Once you can score a lead across those four signals, "sales-ready" stops being an opinion and becomes a line on a chart. That line is your MQL-to-SQL handoff. A marketing qualified lead has cleared the marketing-owned bar (usually fit plus enough interest). A sales qualified lead has cleared the additional behaviour and journey-stage criteria that justify a salesperson's time.

The handoff fails for predictable reasons, and almost all of them are operational rather than human:

• No shared definition. Marketing and sales score leads differently, so MQLs get bounced back and trust breaks down.
• No threshold in the system. The criteria exist in a slide deck but were never built into the CRM as scoring properties and workflows, so nothing happens automatically.
• Silent handoffs. A lead crosses the threshold but no task, notification or routing rule fires, so it sits unworked.
• No feedback loop. Sales never reports back why a lead was disqualified, so the model never improves.

Fixing these is a configuration job. The score needs to live in CRM properties. The threshold needs to trigger a workflow that creates the deal, assigns the owner, notifies the rep and starts an SLA clock. Disqualification reasons need to be captured as structured data and fed back into the scoring model. Done properly, the handoff is invisible to the people involved and self-correcting over time.

Build the model on your data, not a template

Borrowed scoring models rarely work, because they encode someone else's customers. The signals that predict a sale for a mid-market manufacturer are not the ones that predict a sale for a SaaS scale-up. The reliable approach is to start from your closed-won and closed-lost history, identify the fit attributes and behaviours that actually separated the two, and weight your model accordingly. Clean, well-structured CRM data is the prerequisite for any of this. If contact and company records are patchy or inconsistent, the score will be too, which is why scoring projects and data engineering tend to go hand in hand.

It is also worth remembering that a lead which is not sales-ready is not a dead lead. It is a nurture lead. The point of scoring is not to discard the rest of your pipeline, it is to route each lead to the right next step automatically: the hot ones to sales, the warm ones to nurture, the poor-fit ones out of the way.

Where this fits in your revenue operations

Lead scoring is one part of a connected revenue operation. The score depends on data flowing in cleanly from your forms, website and connected tools, which is why teams that get the most from scoring usually have their core systems integrated rather than leaking data between disconnected apps. If you want the detail on connecting your marketing and sales stack to your CRM, our guide to connecting anything to HubSpot covers the patterns.

If your MQL-to-SQL handoff is leaking leads or sales does not trust the ones it gets, the fix is rarely more effort from the team. It is a clear, agreed definition of sales-ready built into the CRM as scoring, routing and reporting that runs on its own. That is the heart of what managed RevOps exists to deliver.

See how managed RevOps builds your lead-scoring and handoff