Definition
Last reviewed June 3, 2026
In a product-led motion, the buyer typically self-serves into the product before talking to sales. The signal that tells a rep this account is ready to convert is no longer a form fill, it is what the user is doing inside the product. PQL scoring is how that behaviour is translated into a number a CRM can route on.
Common positive signals include: invited two or more teammates, integrated a key external tool, hit a usage threshold (10+ deals created, 1,000+ rows imported, etc.), spent time on the pricing or upgrade page, or used a workflow only available on the paid plan. Negative signals include: free email domain, single user, no activity for 14+ days. Each signal carries a weight informed by historical conversion data.
INSIDEA wires PQL scoring as a custom property on the HubSpot contact and company record, fed by behavioural events streamed from the product (via Segment, Hightouch, or a direct API). The score thresholds drive lifecycle stage transitions, lead routing rules, and SDR / AE workflows. The full architecture is part of the SaaS HubSpot implementation; see /hubspot/industries/saas for the canvas.
FAQs
MQL is qualified by marketing engagement (downloads, webinar attendance, form fills). PQL is qualified by in-product behaviour (feature adoption, team activation, paid-feature usage). PQL is the more predictive signal for product-led SaaS.
HubSpot has native lead scoring properties that can carry the PQL number, but the input signals must be streamed in from the product. INSIDEA usually pairs HubSpot with Segment or Hightouch for the behavioural event layer, then writes the scoring logic as a calculated property.
There is no universal threshold. The honest path is: pull your last 6 to 12 months of converted accounts, look at the in-product behaviour they showed in the 14 days before converting, and reverse-engineer the score weights from that data. INSIDEA's SaaS engagements typically take 1 to 2 weeks of historical analysis before locking the scoring model.
Most teams use PQL crossing a threshold (commonly 60 or 70 on a 100-point scale) as the lifecycle stage transition from Lead to Marketing Qualified Lead. A higher threshold (often 85+) routes to an SDR or AE for live outreach. The transitions and the routing rules live in HubSpot workflows.
Related terms
A lifecycle stage is a fixed property on a contact or account record that describes where that record is in the relationship with the business: subscriber, lead, MQL, SQL, opportunity, customer, evangelist, or other. Lifecycle stages let RevOps measure conversion at every transition, automate routing, and report a clean funnel without inventing one in a spreadsheet.
RevOps, short for revenue operations, is the function that aligns sales, marketing, and customer success around a single revenue motion. It owns the CRM, the data model, the lifecycle stages, the forecasting cadence, and the systems that connect them. Done well, RevOps is the operating system that lets a leadership team see, predict, and improve revenue without guesswork.
Book a demo and discovery call to get a look at:
Book a Call With Us
How INSIDEA works