PLG Lead Scoring in HubSpot: Score Leads on Product Usage

Quick answer: PLG lead scoring in HubSpot assigns point values to product usage signals (activation milestones, feature usage, engagement frequency) instead of traditional marketing touches. Sync product data directly to HubSpot contact properties, then build scoring workflows that update automatically when users hit key behaviors.

Product Engagement Score (0-40 points) - Activation status, feature usage depth, engagement frequency. The core dimension for PLG.

Fit Score (0-30 points) - Company size, industry, team size. Still matters but weights lower than usage.

Intent Score (0-30 points) - Pricing page visits, help doc consumption, upgrade clicks. Buying signals layered on top.

PQL threshold - 70+ combined points typically triggers sales handoff. Tune based on your win rates.

Why Traditional Lead Scoring Fails for Product-Led Growth Companies

Traditional lead scoring models assign points for form fills, webinar attendance, email opens, and content downloads. That works when every lead enters through marketing campaigns. It breaks completely in product-led growth.

PLG users sign up for your product first. They skip the gated content. They don't attend webinars before trying your tool. A VP at a 500-person company who completes activation in 48 hours and invites three teammates scores the same as a solo founder who signed up and never logged in again - both have zero marketing engagement points. Your scoring model can't tell them apart.

The MQL Problem in Self-Serve Models

Marketing Qualified Leads (MQLs) assume leads need nurturing before they're ready to buy. Self-serve PLG inverts that. Users experience your product's value before talking to sales. A user who has built three dashboards, integrated two data sources, and invited their team is further along the buying journey than someone who downloaded a whitepaper, regardless of their job title.

Self-serve signups create volume. Hundreds or thousands of contacts per month, most with incomplete firmographic data. Traditional scoring tries to route these based on company size and industry gleaned from enrichment tools, while the most predictive data - what they're actually doing in your product - sits in your application database, invisible to HubSpot.

Why Product Usage Beats Marketing Engagement for PLG

A user who logs in daily, uses power features, and invites teammates is demonstrating intent with behavior. They're investing time. They're deriving value. They're expanding usage across their organization. These signals predict conversion and expansion better than any combination of email clicks and form submissions.

The buying journey is fundamentally different. Users start at the bottom of the funnel. They already have the product. Scoring needs to identify who has reached activation, who has formed a habit, who is expanding to a team, and who is hitting usage ceilings that signal readiness for a paid plan or enterprise features.

Essential Product Usage Signals for PLG Lead Scoring

Product usage data splits into four categories: activation, feature usage, engagement patterns, and team expansion. Each category contributes different signals to your scoring model.

Activation & Onboarding Signals

Activation milestones are binary: a user either completes the core setup flow or they don't. These are the strongest early predictors. A user who connects their first data source, creates their first report, or sends their first campaign has crossed the setup friction and experienced initial value.

Track these as boolean properties on HubSpot contacts:

completed_onboarding (true/false)
reached_aha_moment (true/false, defined by your product's core value delivery)
first_value_achieved (true/false, the moment a user gets a meaningful outcome)

Time to activation matters. A user who activates in 24 hours shows higher intent than someone who takes two weeks. Sync days_to_activation as a number property, then weight faster activation higher in your scoring.

Feature Usage Depth & Breadth

Not all features signal the same buying intent. Users who engage with core workflow features show deeper adoption than users who only touch settings or help documentation. Distinguish between:

Core features - The workflow capabilities that deliver your product's primary value. Heavy usage here indicates the product is embedded in the user's day-to-day.
Power features - Advanced capabilities that differentiate your paid tiers. Usage here often precedes upgrade or expansion conversations.
Administrative features - Settings, user management, billing pages. Lower predictive weight but still useful context.

Sync feature usage as counts or boolean flags:

core_feature_uses_30d (number)
used_advanced_feature_x (true/false for each power feature)
feature_breadth_score (count of distinct features used)

Feature breadth (how many different capabilities a user touches) often correlates with stickiness better than depth in a single feature. A user spreading across multiple features is building the product into more workflows.

Engagement Frequency & Recency

Daily active users convert and expand at higher rates than weekly or monthly actives. Engagement frequency shows habit formation. Sync these properties:

last_active_date (date, updates in real time)
days_since_last_active (calculated field: today minus last_active_date)
session_count_7d (number of login sessions in the last 7 days)
session_count_30d (number of sessions in the last 30 days)

Recency decay matters. A user who was highly active three months ago but hasn't logged in for 30 days should score lower than someone active yesterday. Use days_since_last_active as a negative scoring factor: subtract points for dormancy.

Team Expansion Indicators

Individual users hit usage limits. Teams buy plans. Track collaboration signals:

team_invites_sent (number)
team_members_active (count of other users from the same email domain who are also active)
shared_workspaces_created (count)
seats_in_use (number, if your product has seat-based usage)

A user who invites teammates is pulling others into your product. This is the single strongest signal for expansion pipeline. Weight it heavily.

How to Sync Product Data into HubSpot for Lead Scoring

Product usage data lives in your application database or analytics tool (Mixpanel, Amplitude, PostHog). HubSpot needs that data as contact properties to score leads. You have three options.

The Data Warehouse Problem for PLG Scoring

The traditional enterprise approach pipes product events into a data warehouse (Snowflake, BigQuery), transforms them with dbt, then uses a reverse ETL tool (Census, Hightouch) to sync aggregated properties back to HubSpot.

This works but has costs:

Warehouse costs - Snowflake or BigQuery bills start at hundreds per month, often more
Reverse ETL costs - Census starts at $350/mo, Hightouch at similar
Engineering dependency - Someone has to build the event pipeline, write the transforms, maintain the sync jobs
Lag - Batch syncs run hourly or daily. Real-time scoring requires streaming pipelines, adding complexity

For companies already running a warehouse for product analytics, this path makes sense. For everyone else, it's overkill. Most PLG teams don't need a data warehouse to get product usage into HubSpot.

What Product Properties to Sync to HubSpot

Create custom contact properties for each scoring signal:

Activation properties:

activation_status (enum: Not Started, In Progress, Completed)
activation_date (date)
days_to_activation (number)

Feature usage properties:

core_actions_30d (number)
power_feature_usage (enum: None, Light, Moderate, Heavy)
features_used_count (number, distinct features touched in last 30 days)

Engagement properties:

last_active_date (date)
days_since_last_active (number, calculated)
weekly_active_sessions (number)
engagement_frequency (enum: Daily, Weekly, Monthly, Dormant)

Team properties:

team_size (number, active users from same domain)
team_invites_sent (number)
is_workspace_owner (boolean)

Negative signals:

days_inactive (number)
support_tickets_30d (number)
visited_cancel_page (boolean)

All boolean and enum fields let you build simple workflow branches. Number fields enable threshold-based logic.

Real-Time Sync Options Without Engineering Work

Tools like Zoody sync product events and properties directly to HubSpot without a warehouse. You define which events and properties matter for scoring, and the tool pushes them to HubSpot contact records in real time as users perform actions.

This approach cuts out the warehouse layer:

No dbt transforms to maintain
No reverse ETL bill
RevOps teams configure the sync themselves without engineering tickets
Updates hit HubSpot immediately when users perform scored actions

You still need event tracking somewhere (Segment, Mixpanel, your own backend). The difference is skipping the warehouse transform step and syncing straight to HubSpot.

HubSpot's native Operations Hub can call external APIs in workflows, but building a real-time sync requires writing custom code actions for every event type and handling rate limits, retries, and property mapping. Most teams don't have bandwidth for that.

Building Your PLG Lead Scoring Framework in HubSpot

Effective PLG lead scoring models balance three dimensions: product engagement (what users do in your product), fit (firmographic match to your ICP), and intent (buying signals like pricing page visits).

Three-Dimensional PLG Scoring Model

Assign 100 total points across three categories:

Product Engagement Score (0-40 points) - The primary dimension. Product usage predicts conversion better than any other signal in PLG.

Fit Score (0-30 points) - Still matters, but weights lower than traditional scoring. Company size, industry, and tech stack compatibility.

Intent Score (0-30 points) - Buying signals layered on top of usage. Pricing page visits, help documentation consumption, feature requests for paid-tier capabilities.

This weighting makes product engagement the deciding factor while still filtering out poor-fit accounts. A 500-person enterprise that never activates scores lower than a 50-person company with strong activation and daily usage.

Product Engagement Score Criteria & Point Values

Award points for activation, feature usage depth, engagement frequency, and team expansion. Here's a starter framework:

Activation milestones:

Completed onboarding flow: +15 points
Reached aha moment (first core value action): +10 points
Activated within 48 hours of signup: +5 bonus points

Feature usage:

Used core feature in last 7 days: +5 points
Used 3+ distinct features in last 30 days: +5 points
Used power/advanced feature: +10 points

Engagement frequency:

Daily active (3+ sessions in last 7 days): +10 points
Weekly active (1+ session per week for 4 weeks): +5 points
Dormant for 14+ days: -10 points

Team expansion:

Invited 1+ teammates: +10 points
3+ team members active: +15 points
Created shared workspace or collaboration object: +5 points

Negative signals:

No activity in 30+ days: -15 points
Visited cancellation or downgrade page: -10 points
2+ support tickets in 30 days: -5 points

Adjust these values based on your product. A daily-use tool should weight engagement frequency higher. A project management tool might weight team expansion more heavily.

Fit and Intent Scoring for PLG Context

Fit scoring uses firmographic data, but with PLG-specific adjustments:

Company size (0-15 points):

Enterprise (500+ employees): +15 points (if you sell to enterprise)
Mid-market (50-500): +10 points
SMB (10-50): +5 points
Solo/very small (<10): +0 points (unless your ICP is SMB, then invert)

Industry match (0-10 points):

Target industry: +10 points
Adjacent industry: +5 points
Low-fit industry: +0 points

Tech stack compatibility (0-5 points):

Uses integrations you support: +5 points

Intent signals show buying readiness:

Pricing & upgrade signals (0-15 points):

Visited pricing page: +5 points
Clicked upgrade CTA in-product: +10 points
Requested enterprise features: +15 points

Help & research signals (0-10 points):

Read paid-tier documentation: +5 points
Attended product webinar/demo: +10 points

Engagement with sales (0-5 points):

Replied to sales email: +5 points
Booked demo call: +5 points (often moves to SQL at this point anyway)

Setting PQL Thresholds and Score Triggers

Most PLG companies set PQL thresholds around 70-80 combined points. This typically captures:

Strong activation (15-25 points)
Regular usage (10-15 points)
Some team expansion or power feature usage (10-15 points)
Reasonable fit (15-20 points)
Some intent signals (5-10 points)

Create HubSpot workflows that trigger on score thresholds:

PQL (70+ points) - Notify sales, move to PQL lifecycle stage, add to high-priority view. Automating PLG sales handoff at this threshold prevents leads from going cold.

Expansion-ready (80+ points) - Existing customers who hit this threshold are upsell candidates. Route to account managers.

Churn risk (below 30 points, previously higher) - Score decay indicates disengagement. Flag for customer success intervention.

Don't route everything to sales at 70 points on day one. Start with a higher threshold (80-85) for the first month, review what converts, then lower the threshold to capture more volume once you validate the model.

Implementing and Optimizing Your PLG Scoring Model

Building the framework is half the work. Implementation in HubSpot requires creating properties, workflows, and views that update scores automatically as product usage data flows in.

HubSpot Configuration Walkthrough

Step 1: Create custom properties

In HubSpot Settings > Properties > Contact Properties, create:

plg_engagement_score (number, 0-40)
plg_fit_score (number, 0-30)
plg_intent_score (number, 0-30)
plg_total_score (number, 0-100, calculated as sum of the three above)

Also create the underlying product usage properties listed earlier (activation_status, last_active_date, team_invites_sent, etc.). These feed into scoring workflows.

Step 2: Build scoring workflows

Create separate workflows for each scoring dimension. This keeps logic modular and easier to debug.

Product Engagement Score workflow:

Trigger: Contact property activation_status changes, or last_active_date updates, or team_invites_sent increases
Actions:
If activation_status = "Completed", set plg_engagement_score to 15 (or increment by 15 if building additively)
If days_since_last_active < 7, add 10 points
If team_invites_sent > 0, add 10 points
If power_feature_usage = "Heavy", add 10 points
Calculate and set plg_engagement_score (total of all criteria)

Use workflow "Set property value" actions with conditional branches for each criterion. If you have HubSpot Professional or Enterprise, use calculated properties instead of workflows where possible for real-time updates.

Fit Score workflow:

Trigger: Contact property company_size or industry changes
Actions: Set plg_fit_score based on company size and industry match

Intent Score workflow:

Trigger: Contact visits pricing page (page view event), or support_ticket_count changes
Actions: Set plg_intent_score based on pricing visits, help doc consumption, sales engagement

Total Score workflow:

Trigger: Any of the three sub-scores changes
Action: Set plg_total_score = plg_engagement_score + plg_fit_score + plg_intent_score

Step 3: Create PQL views and sales handoff triggers

Create a contact view filtered by plg_total_score >= 70 and lifecycle stage not in [Customer, Evangelist, Other]. This becomes your PQL queue.

Build a workflow that triggers when plg_total_score crosses 70:

Move lifecycle stage to "Product Qualified Lead"
Create task for sales rep (assigned by territory or round-robin)
Send internal Slack notification to sales channel
Optionally send an in-app message or email to the contact offering a demo

Measuring Model Performance

Track these metrics weekly:

Score distribution - How many contacts fall into each score band (0-30, 30-50, 50-70, 70-85, 85-100)? If 80% of your contacts score below 30, your activation rate or engagement retention needs work before scoring helps.

PQL-to-SQL conversion rate - What percentage of contacts scoring 70+ convert to Sales Qualified Leads (active sales conversations)? Target 30-50% in the first few months.

PQL-to-customer conversion rate - What percentage of PQLs ultimately close? This tells you if your threshold is set correctly. If fewer than 10% close, your threshold is too low.

Time to PQL - Median days from signup to crossing the PQL threshold. Faster is better. If it takes 60+ days, your activation flow or early product experience needs improvement.

Win rate by score band - Do contacts scoring 85+ close at higher rates than those scoring 70-75? If not, your scoring criteria aren't predictive. Recalibrate.

Build a HubSpot report with closed-won deals, grouped by plg_total_score at the time they became PQL. This shows which score bands actually convert.

Continuous Optimization Based on Win/Loss Data

Every quarter, analyze which signals predicted closed-won deals:

Export all contacts that became customers in the last 90 days
Look at their plg_engagement_score, plg_fit_score, and plg_intent_score at the time they converted to PQL
Identify patterns - did most winners have team expansion signals? Did power feature usage matter, or was simple activation enough?

Adjust point values based on what you learn. If 90% of winners had team_invites_sent > 0 but only 40% used power features, increase the weight on team expansion and decrease power feature points.

Common mistakes to avoid:

Over-complicating criteria - Start with 5-7 signals. Add more only if the initial model fails to differentiate winners from non-converters.

Static scores - Update scores in real time (or at least daily). A user who was a PQL last week but hasn't logged in for 14 days should drop below the threshold.

Ignoring account-level rollups - If multiple users from the same company sign up, your scoring should aggregate to the company record, not just individual contacts. A company with five moderately engaged users is more valuable than one with a single power user.

Not testing before going live - Run your scoring model on historical data first. Score last quarter's signups, then check which ones converted. If your model would have flagged 200 PQLs and only 5 closed, recalibrate before sending 200 tasks to sales.

FAQ

What is PLG lead scoring and how is it different from traditional lead scoring?

PLG lead scoring assigns point values to product usage behaviors (activation milestones, feature usage, engagement frequency, team expansion) instead of marketing engagement actions (form fills, email opens, content downloads). Traditional scoring assumes leads need nurturing before they're ready to buy. PLG scoring recognizes that self-serve users start with the product and demonstrate buying intent through how they use it, not how they interact with marketing content.

What product usage signals should I include in my HubSpot lead scoring model?

Include activation status (whether the user completed onboarding and reached your product's aha moment), engagement frequency (daily vs weekly vs dormant usage patterns), feature usage depth (especially power features that indicate advanced needs), and team expansion indicators (invites sent, shared workspaces created, number of active teammates). Also track negative signals like days inactive, support ticket volume, and visits to cancellation pages. Weight activation and team expansion highest - they're the strongest predictors of conversion in most PLG models.

How do I get product usage data into HubSpot without a data warehouse?

You can sync product usage data directly to HubSpot using tools like Zoody that connect your product events to HubSpot contact properties without requiring a data warehouse or reverse ETL pipeline. Alternative approaches include using HubSpot's API to push data from your application backend (requires engineering work), or building the full warehouse stack with Census or Hightouch (higher cost and complexity but more flexibility). For most PLG teams, direct-sync tools offer the fastest path to scoring on product usage without engineering dependencies.

What is a good PLG lead score threshold for sales handoff?

Most PLG companies set their PQL threshold between 70-80 points on a 100-point scale. This typically captures users who have activated (15-25 points), show regular engagement (10-15 points), demonstrate some team expansion or power feature usage (10-15 points), match your ICP reasonably well (15-20 points), and show buying intent signals (5-10 points). Start with a higher threshold (80-85) for the first month to avoid overwhelming sales, then lower it incrementally as you validate conversion rates. Track PQL-to-customer conversion by score band to find the threshold that balances volume with quality.

Can I build PLG lead scoring in HubSpot without engineering resources?

Yes, if you already have product usage data flowing into HubSpot. Create custom contact properties for each scoring signal, then build workflows that set score values based on property changes (activation status updates, last active date changes, team invites sent). The challenge is getting product data into HubSpot in the first place - that typically requires either engineering work to build an API integration, a reverse ETL tool with warehouse dependencies, or a direct-sync tool like Zoody that RevOps teams can configure themselves. Once the data is in HubSpot, building the actual scoring workflows requires no code.

{
 "meta_description": "Build a PLG lead scoring model in HubSpot using product usage data. Score leads on activation, feature usage, and team expansion without a data warehouse.",
 "word_count": 2455,
 "tag": "PLG",
 "faq_schema": {
 "@context": "https://schema.org",
 "@type": "FAQPage",
 "mainEntity": [
 {
 "@type": "Question",
 "name": "What is PLG lead scoring and how is it different from traditional lead scoring?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "PLG lead scoring assigns point values to product usage behaviors (activation milestones, feature usage, engagement frequency, team expansion) instead of marketing engagement actions (form fills, email opens, content downloads). Traditional scoring assumes leads need nurturing before they're ready to buy. PLG scoring recognizes that self-serve users start with the product and demonstrate buying intent through how they use it, not how they interact with marketing content."
 }
 },
 {
 "@type": "Question",
 "name": "What product usage signals should I include in my HubSpot lead scoring model?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "Include activation status (whether the user completed onboarding and reached your product's aha moment), engagement frequency (daily vs weekly vs dormant usage patterns), feature usage depth (especially power features that indicate advanced needs), and team expansion indicators (invites sent, shared workspaces created, number of active teammates). Also track negative signals like days inactive, support ticket volume, and visits to cancellation pages. Weight activation and team expansion highest - they're the strongest predictors of conversion in most PLG models."
 }
 },
 {
 "@type": "Question",
 "name": "How do I get product usage data into HubSpot without a data warehouse?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "You can sync product usage data directly to HubSp