What PQL scoring rules convert freemium users to MQL status for sales outreach?

Behavioral Scoring Framework for PQL Conversion

The foundation of any PQL-to-MQL scoring system is a point-based rubric that quantifies user actions within the product. Behavioral signals should carry approximately 60% of the total weight in a standard scoring model, as they directly demonstrate product engagement and latent purchase intent. Each action a freemium user takes must be assigned a point value based on its historical correlation with paid conversion.

Common behavioral scoring elements include seat expansion, where each unique user invited to the account earns 5 points, capped at 20 invites to prevent gaming the system. API integrations created represent a deeper technical commitment and should receive 15 points per integration. The most powerful behavioral signal is workflow or automation configuration, which earns 20 points because it indicates the user has embedded the product into their operational processes. Cross-functional login activity—where users from different departments access the same account—adds 10 points, signaling organizational adoption beyond a single champion.

Resource limit breach attempts are the highest-scoring behavioral signal at 25 points. When a freemium user tries to exceed their plan's storage, seat count, or feature access limits, they are explicitly demonstrating that their needs have outgrown the free tier. This action correlates strongly with upgrade intent and should trigger immediate score elevation.

To implement these rules effectively, you need product analytics tools like Amplitude, Mixpanel, or Segment that track feature-level events. Set up event tracking for each scoring action and compute rolling PQL scores daily. The scoring engine should feed directly into your CRM via webhook to auto-create MQL campaigns when thresholds are met. Bridge Group data shows that 43% of PQLs converting to MQL within 14 days close with 16% higher deal velocity than inbound leads, validating the importance of timely scoring.

Firmographic Fit and Demographic Scoring

While behavioral signals dominate the PQL scoring model, firmographic fit provides the necessary context to ensure sales resources are deployed against accounts with genuine capacity to purchase. Firmographic signals should carry approximately 40% of the total scoring weight, preventing your team from chasing high-engagement users at companies that cannot afford or authorize a paid plan.

Company size is the primary firmographic factor. Organizations with 101–500 employees should receive 15 points, as this range typically has both budget authority and a genuine need for scalable tools. Companies smaller than 10 employees often lack budget, while enterprises over 1,000 employees may require lengthy procurement cycles that are inefficient for early-stage outreach. Industry match adds 10 points when the user's vertical aligns with your target markets—for example, a SaaS product focused on financial services should award bonus points to fintech users.

Tech stack integration count is a nuanced but powerful signal. Each integration the user has connected to your product earns 5 points, with no cap. A user who has integrated your product with Salesforce, Slack, and Zapier has invested significant setup time and created switching costs that make them more likely to convert. This also indicates they are using your product as part of a broader workflow rather than in isolation.

Geographic and departmental signals can further refine scoring. Users from enterprise headquarters locations or from departments with budget authority (finance, operations, engineering leadership) should receive an additional 5–10 points. Departmental data can often be inferred from email domain patterns or from the user's self-reported role during sign-up.

The combination of behavioral and firmographic scores creates a composite PQL score typically measured on a 0–100 or 0–200 point scale. A user who scores high on both dimensions is far more likely to convert than one who excels in only one area. For example, a user with 80 behavioral points but only 10 firmographic points may be an individual contributor at a small company—engaged but unlikely to have purchasing power. Conversely, a user with 30 behavioral points but 50 firmographic points may need more product engagement before sales outreach is appropriate.

Confidence Thresholds and Conversion Windows

Simply reaching a point threshold is insufficient for MQL conversion—the scoring model must also enforce a time-based confidence window to ensure the user's interest is current. A common and effective rule requires that the user achieve a minimum of 85 total points AND demonstrate feature depth activity within the past 7 days. This prevents stale scoring where a user who was highly engaged three weeks ago but has since gone dormant is incorrectly treated as a sales-ready lead.

The 7-day engagement window should measure the user's most recent core action, not just a login. A user who logs in but performs no meaningful action should not satisfy this requirement. Instead, require that they have completed at least one of the high-scoring behaviors (workflow creation, API integration, team invite, or resource limit breach) within the rolling 7-day window.

For users who score above 85 but lack recent activity, implement a grace period of 3 days where the system holds them in a "pending MQL" status. If they re-engage within that window, they convert automatically. If not, their score begins to decay at a rate of 5–10 points per week of inactivity. This decay function ensures that only currently engaged users occupy your sales team's queue.

The confidence threshold can also be tiered based on sales team capacity. When your SDR team has bandwidth, lower the threshold to 70 points to generate more leads. During peak periods or when conversion rates are already high, raise it to 100 points to focus only on the highest-intent users. This dynamic thresholding allows you to balance lead volume with sales capacity without changing your underlying scoring model.

Some organizations implement a two-stage PQL system where users scoring 30–59 points enter a "warm nurture" track with automated educational emails, those scoring 60–84 points receive a product tour from a customer success representative, and only those scoring 85+ with recent activity convert to MQL for direct sales outreach. This graduated approach ensures that lower-scoring users are still cultivated without consuming sales resources.

Time-Based Decay and Re-Engagement Scoring

User engagement naturally fluctuates, and a static PQL score fails to account for waning interest. Implementing time-based decay ensures your scoring model reflects current user behavior rather than historical peaks. The standard approach applies a 5–10 point reduction per week of inactivity after the first 14 days of the user's lifecycle. This means a user who scored 120 points in week one but hasn't logged in for three weeks would see their score drop to approximately 90–100 points, potentially moving them below the MQL threshold.

The decay should accelerate after 45 days of inactivity. Users who have been dormant for 45+ days and have not responded to any automated re-engagement emails should lose 15 points per week until they either re-engage or fall below a minimum score floor of 20 points. Users below this floor should be moved to a suppressed list and not contacted by sales, preventing your team from chasing leads with near-zero conversion probability.

Complement decay with re-engagement scoring rules that can rapidly elevate a dormant user back to MQL status. The most powerful re-engagement signal is a return after 30+ days of inactivity. If a user who went dark for a month suddenly logs back in and performs a core action within 24 hours, award them a 50-point "comeback bonus." This dramatic score increase ensures they immediately re-enter the sales queue, as this behavior often correlates with a specific trigger event such as a new feature release, a competitor outage, or a seasonal business need.

Response to triggered email is another valuable re-engagement signal. When a user clicks a link in a re-engagement email and subsequently completes a key action within 48 hours, add 30 points to their score. Email engagement combined with product action is a stronger signal than either alone, indicating the user was prompted to return rather than stumbling back accidentally.

Support ticket escalation is perhaps the highest-intent re-engagement signal. If a dormant user submits a support ticket asking about pricing, enterprise features, or migration assistance, immediately boost their score by 40–60 points. This user is actively evaluating a purchase and should be contacted within hours, not days.

Feature release adoption also deserves a scoring bonus. When a user who has been inactive for 21+ days returns and immediately uses a newly released premium feature available as a limited preview to freemium users, award 35 points. This indicates they are monitoring your product roadmap and see future value in your platform.

Negative Scoring Rules to Filter Low-Quality Users

Not every freemium user should be pursued for MQL conversion. Aggressively contacting users with low engagement or negative signals damages brand reputation and wastes sales resources. Negative scoring rules—points deducted for specific behaviors or lack thereof—ensure your sales team only reaches out to users with genuine purchase intent.

The most common negative rule targets account creation without activation. Users who sign up but never complete the core "Aha!" action within 14 days should lose 30–50 points from their baseline. If they remain in this state for 30+ days, deduct an additional 20 points. These users are likely tire-kickers or those who signed up out of curiosity with no real need.

High support volume without progress is another negative signal. Users who submit 5+ support tickets in their first 30 days but still haven't completed the onboarding checklist should lose 25 points. Excessive support requests without self-sufficiency often indicate poor product-market fit or a user who expects white-glove service on a free plan—a low-conversion profile.

Repeated plan downgrade interest suggests price sensitivity. If a user visits the pricing page 10+ times but never upgrades, and their feature usage remains limited to the free tier's most basic functions, deduct 15 points. This pattern indicates a mismatch between their needs and your paid plans.

Account sharing across multiple free accounts is a clear abuse signal. If your analytics detect that the same IP address or email domain is associated with 3+ separate freemium accounts without a team plan, deduct 40 points. These users are gaming the system to avoid paying and rarely convert to legitimate paid accounts.

No response to triggered outreach is a passive but powerful negative signal. If your automated email sequence sends 3+ educational or value-add emails and the user opens none of them within 21 days, deduct 20 points. Complete email disengagement strongly indicates the user has abandoned the product.

Balance negative rules carefully. Too aggressive and you'll filter out users who convert slowly—those who need 60 days to evaluate. A good rule of thumb is that negative scoring should only reduce a user's score by a maximum of 40% of their peak score. This ensures that even users with negative signals can recover if they demonstrate renewed engagement.

Quantifiable Feature Adoption Milestones as PQL Triggers

The most reliable PQL scoring rules move beyond simple sign-up completion and measure deep, repeated engagement with features that correlate most strongly with long-term retention and eventual paid conversion. For freemium users, the key is identifying which product behaviors signal that the user has achieved their "Aha!" moment—the point where the product's core value becomes undeniable.

Core action frequency is the foundational milestone. Users who perform the primary value-driving action at least 3–5 times within the first 7 days typically score 30–45 points higher on a 100-point PQL scale than those who only do it once. This threshold indicates the user has integrated the tool into their workflow rather than just testing it. For a project management tool, this might be creating 5 projects. For an analytics tool, it might be running 10 reports.

Collaboration triggers are powerful because they demonstrate social proof and increased switching costs. When a freemium user invites at least one teammate or external collaborator, their PQL score should increase by 20–35 points. Teams of 3+ active users within a single account often convert at 2–3x the rate of single-user accounts. The presence of multiple users creates network effects and makes it harder for the organization to abandon the product.

Data volume thresholds indicate investment. Users who import or generate a meaningful amount of data—500+ records in a CRM tool, 10+ projects in a project management app, or 1,000+ API calls in a dev tool—within the first 14 days should receive a 15–25 point PQL boost. This indicates they've invested time in setup and are now dependent on the product for ongoing operations. The cost of migrating this data to a competitor becomes a barrier to churn.

Feature breadth is a leading indicator of perceived value. Users who activate 4+ distinct features within their first 30 days score 40–60 points higher on average. A narrow usage pattern—only using the free tier's basic search—suggests low perceived value, while broad adoption signals the user sees the product as a comprehensive solution. Track which features are most commonly used by your best-converting users and weight those features highest in your scoring model.

Implementation and Validation of Scoring Rules

Deploying a PQL scoring model requires careful implementation across your product analytics, CRM, and sales automation stack. The scoring engine should compute scores daily using a rolling window of user activity. Tools like Amplitude or Segment can calculate these scores in real-time and push them to Salesforce via webhook, where they auto-create MQL records and trigger campaign assignments.

Begin by establishing your baseline scoring matrix based on historical data. Analyze your best-converting freemium users from the past 6–12 months and identify the top 3–5 features they all used before converting. Assign those features the highest point values. A typical starting matrix might award 40 points for 5+ core actions in 7 days, 30 points for inviting 2+ team members, 25 points for importing 1,000+ records, 50 points for activating 5+ features, and 20 points for completing the onboarding checklist.

Validate your scoring rules by measuring MQL-to-opportunity conversion rates. Aim for a 10–20% MQL-to-opportunity rate as a benchmark. If your rate is below 10%, your threshold may be too low, allowing low-quality users through. If above 20%, you may be too conservative and missing potential conversions. Adjust point values or add new rules based on which actions correlate most strongly with upgrades.

A/B test your scoring model by running two parallel scoring versions for 30 days. Version A uses your current rules, while Version B adjusts point values or thresholds by 10–15%. Compare the conversion rates and deal velocity of MQLs generated by each version. The version that produces higher-quality leads—measured by opportunity creation rate, pipeline value, and close rate—should become your new default.

Cohort analysis is essential for ongoing optimization. Track how different user segments score and convert. You may discover that users from certain industries or company sizes require different scoring thresholds. For example, enterprise users might need a lower behavioral threshold because their longer sales cycles mean they evaluate products more slowly, while SMB users need higher behavioral scores because they typically decide faster.

Regularly review your scoring model quarterly. As your product evolves and new features are released, the behaviors that predict conversion will change. A feature that was rarely used six months ago might become your strongest conversion signal after a product update. Keep your scoring model aligned with your current product reality by analyzing the most recent 90 days of conversion data before each quarterly review.

Related questions

How do you calculate a PQL score for freemium users?

A PQL score is calculated by assigning points to product behaviors like completing a core workflow, inviting team members, or hitting usage limits, combined with firmographic fit points. Scores are computed daily using a rolling window and must include a recency requirement to ensure current engagement.

What usage thresholds indicate a freemium user is ready for sales outreach?

Common thresholds include 5+ core actions within 7 days, 2+ team invites, 1,000+ records imported, or activation of 4+ distinct features. These thresholds should be validated against your historical conversion data and typically correspond to a composite score of 85+ points on a 100-point scale.

Should PQL scoring include negative rules to filter users?

Yes, negative scoring rules are essential. Deduct points for account creation without activation, excessive support tickets without progress, repeated pricing page visits without upgrade, or account sharing across multiple free accounts. This prevents sales teams from wasting time on low-conversion users.

How do you prevent stale PQLs from reaching sales?

Implement time-based decay that reduces a user's score by 5–10 points per week of inactivity after 14 days. Require feature depth activity within the past 7 days for MQL conversion. Users below a 20-point floor should be moved to a suppressed list and not contacted by sales.

What tools are needed to implement PQL scoring?

You need product analytics tools like Amplitude, Mixpanel, or Segment to track feature-level events. A scoring engine to compute rolling PQL scores daily, and a CRM like Salesforce to receive scores via webhook and auto-create MQL records. Integration between these systems is critical for real-time scoring.

FAQ

What is a PQL scoring rule? A PQL scoring rule is a predefined condition that assigns points to freemium user actions—like completing a key workflow or hitting a usage threshold. These rules rank users based on product engagement, not just demographic fit, to identify which are ready for sales outreach.

How do I set a usage threshold for MQL conversion? Common thresholds include reaching a specific number of logins per week (e.g., 5–10) or performing a core action a set number of times. The exact number varies by product, but a typical range is 3–7 key actions within a 30-day window, validated against your historical conversion data.

Should I include time-based rules in my PQL scoring? Yes, time-based rules—such as "active for at least 14 days" or "completed onboarding within 7 days"—help filter out trial-only users. These rules often combine with action counts to ensure the user has both intent and sustained engagement before sales outreach begins.

What role does feature adoption play in PQL scores? Feature adoption rules award points for using high-value features, like integrations or advanced reporting. For example, a user who activates a premium feature like API access might receive 20–30 points, signaling deeper product need and sales readiness. Broader feature adoption correlates with higher conversion rates.

Can negative scoring rules be used to exclude users? Absolutely. Negative rules subtract points for behaviors like account inactivity for 7+ days or excessive use of free-tier limits. This prevents sales teams from chasing users who are unlikely to convert, keeping the MQL list focused on high-intent prospects with genuine purchase potential.

How do I validate my PQL scoring rules over time? Regularly review conversion rates of scored users to actual paid customers—aim for a 10–20% MQL-to-opportunity rate. Adjust point values or add new rules based on which actions correlate most strongly with upgrades, using A/B testing or cohort analysis every quarter.

Sources

• https://www.joinpavilion.com/compensation-report
• https://www.bridgegroupinc.com/blog/sales-development-report
• https://openviewpartners.com/blog/
• https://www.gartner.com/en/sales/research
• https://www.saastr.com/
• https://amplitude.com/blog/product-qualified-leads
• https://mixpanel.com/blog/pql-scoring/
• https://www.intercom.com/blog/product-qualified-leads/
• https://productled.com/blog/pql-scoring-model
• https://www.hubspot.com/products/crm/lead-scoring

Related on PULSE

• [What's the right pricing strategy for a freemium → paid conversion?](/knowledge/q84)
• [How do you bridge attribution between self-serve trial users and enterprise procurement upgrades?](/knowledge/q9837)
• [How do we model expansion revenue from self-serve users in the first 90 days?](/knowledge/q669)
• [How do you coach a channel rep to manage partners, not end users?](/knowledge/q14047)
• [How Do I Get My Support Reps to Convert Chats to Sales?](/knowledge/q16036)
• [What's the framework for a CRO to decide whether to build two separate sales motions?](/knowledge/q9558)