PLG Sales: How to Turn Product Signals Into Revenue (2024)

Quick answer: PLG sales is a sales motion triggered by product usage signals, not traditional lead gen. Instead of cold outreach to MQLs, sales reps contact users who already demonstrate value from your product - users who invite teammates, adopt key features, or hit usage thresholds. The goal is to convert self-serve users into paid customers or expand existing accounts based on product behavior.

PQL identification - Define thresholds for engagement, activation, and feature adoption that signal buying intent.

Product data in your CRM - Sync usage events, feature adoption, and account health scores into HubSpot so sales can act on signals.

Automated routing - Workflows that assign PQLs to reps based on account size, geography, or product segment.

Product-informed outreach - Personalized messaging that references actual product behavior ("I saw you invited your team").

Measurement - Track PQL-to-opportunity conversion, time to close, and product-influenced revenue.

What Is PLG Sales (Product-Led Sales)?

PLG sales is a sales approach where product usage data triggers and informs the sales motion. Users sign up, adopt the product on their own, and sales contacts them only after they demonstrate real engagement or buying signals through their behavior. This is the opposite of traditional sales-led growth, where marketing generates leads through content and ads, sales qualifies them through discovery calls, and only then does the prospect see the product.

The shift is from MQLs (marketing-qualified leads scored on demographic fit and content downloads) to PQLs (product-qualified leads scored on actual product usage). A PQL has already experienced value. They know the product solves their problem because they used it to solve their problem.

PLG Sales vs. Sales-Led Growth vs. Pure PLG

Approach	Lead Source	Qualification	Sales Involvement	Best For
Sales-led growth	Marketing campaigns, outbound	BANT, discovery calls	High-touch from first contact	Enterprise deals, complex sales cycles
Pure PLG	Self-serve signup	Usage thresholds only	None, product drives conversion	Low ACV, high volume, simple products
PLG sales	Self-serve signup	Product usage signals	Low-touch at PQL threshold	Mid-market expansion, freemium-to-paid conversion

PLG sales sits in the middle. Users can adopt the product without talking to sales, but sales steps in when product signals indicate an upsell opportunity or the user needs help expanding. Companies like Slack, Dropbox, and Notion all started with self-serve adoption, then layered sales teams to capture larger accounts.

Why Product-Led Companies Need Sales Teams

Pure self-serve works until you hit two realities:

Large accounts rarely self-serve all the way to enterprise contracts. A team of 500 will not put a corporate card into a self-serve checkout for $50,000/year. They want a contract, procurement, security reviews, and custom terms.
Expansion revenue requires human touch. A user might adopt your product for personal use, but converting their entire department or company requires education, implementation planning, and executive buy-in that product alone cannot deliver.

PLG sales captures revenue that self-serve leaves on the table. The product still drives initial adoption and proves value, but sales accelerates expansion and closes larger deals. The trigger for sales involvement is product usage, not a form fill or cold call.

When to introduce a PLG sales motion:

You have self-serve users consistently hitting usage thresholds (inviting teammates, using core features daily, reaching free plan limits).
Your product has a clear expansion path (team plans, enterprise features, usage-based pricing tiers).
Average contract value for teams is high enough to justify sales costs (typically $5,000+ annual contract value).
You see users churning or stalling at growth inflection points because they lack guidance.

How to Identify and Score Product-Qualified Leads (PQLs)

A PQL is a user whose product behavior indicates they are ready to buy or expand. The specific criteria depend on your product, but the framework is universal: engagement (how often they use it), activation (whether they reached an "aha moment"), and adoption (which features they use).

The PQL Scoring Framework: What to Measure

Engagement score - Frequency and recency of product use. A user who logs in daily for two weeks is more qualified than someone who logged in once three months ago. Track:

Days active in the last 30 days
Sessions per week
Time since last login

Activation score - Whether the user completed key setup steps or reached core value. For a collaboration tool, this might be creating their first project or inviting a teammate. For a data tool, running their first query. Track:

Completed onboarding steps (connected data source, invited team, created first X)
Reached core value metric (sent first message, generated first report, processed first transaction)

Adoption score - Which features they use and how deeply. Users who adopt advanced features or multiple features are more likely to pay. Track:

Number of distinct features used
Usage of paid-tier features (if you have feature gating)
Power-user actions (API usage, custom integrations, advanced settings)

Fit score - Demographic and firmographic data that indicates they match your ICP. This is traditional lead scoring, but applied to product users. Track:

Company size (employee count, revenue if available)
Industry or vertical
Job title or role
Email domain (corporate vs. personal)

Intent score - Explicit signals that indicate buying intent. Track:

Viewed pricing page
Requested upgrade or contacted support about paid features
Hit free plan limits (storage, seats, usage caps)
Added payment method

A complete PQL score combines these dimensions. A user with high engagement and activation but low fit (personal Gmail account, solo user) is probably not a PQL. A user with high fit and intent but low activation might need a different sales play (a product demo to drive adoption before asking for a sale).

Example: Building a PQL Model for Your Product

Let's say you run a project management SaaS. Your PQL definition might be:

Required criteria (all must be true):

Created at least one project with 3+ tasks
Invited at least one teammate
Active in the last 7 days

Scoring thresholds (additive):

+10 points: 5+ days active in last 30 days
+10 points: Used 3+ distinct features (task assignment, file upload, comments)
+15 points: Corporate email domain
+15 points: Company has 20+ employees (from data enrichment)
+20 points: Viewed pricing page in last 14 days
+20 points: Invited 3+ teammates

PQL threshold: 50+ points and all required criteria met.

This model scores users who are actively using the product with their team and show signs of expansion intent. You can weight the dimensions differently based on what predicts conversion in your data. Some companies weight intent signals (pricing page views, upgrade requests) 2x higher than engagement because they are stronger predictors.

Common PQL Scoring Mistakes to Avoid

Scoring on vanity metrics - Total logins or page views do not predict buying intent. Score on actions that correlate with value delivery and expansion.

Ignoring fit - High usage from a solo freelancer with a personal email is not a PQL if your product is built for teams. Always include fit criteria.

Static thresholds - Your PQL definition should change as you collect conversion data. If users who invite 5+ teammates convert at 40% but users who invite 2-4 teammates convert at 8%, raise the threshold.

No decay - A user who was highly active six months ago but has not logged in since is not a PQL. Include recency in your score and age out old signals.

Scoring too early - If you score users on day one, before they have time to activate, your PQL list will be full of false positives. Give users at least 7-14 days to demonstrate real usage patterns before scoring.

For a detailed guide on building PQL scoring models and implementing them in HubSpot workflows, see our existing guides.

Syncing Product Data Into HubSpot (or Your CRM)

Your product analytics tool (Mixpanel, Amplitude, PostHog, Heap) shows you who your PQLs are, but your sales team lives in HubSpot. If product usage data stays in analytics and does not flow into your CRM, sales cannot act on it. You need product signals on contact and company records in HubSpot so reps can see usage history, scores can trigger workflows, and you can route PQLs automatically.

What Product Data to Sync to HubSpot

Usage events - Track when users perform key actions. Examples:

User logged in
User invited teammate
User created project
User viewed pricing page
User hit free plan limit

You do not need every event. Sync the 10-15 events that matter for scoring and sales context.

Feature adoption properties - Boolean or count fields on the contact record:

invited_teammate (true/false)
projects_created (number)
days_active_last_30 (number)
last_login_date (date)
core_feature_adopted (true/false)

Account health scores - Calculated properties at the company level:

account_engagement_score (0-100)
account_activation_status (activated, not activated)
pql_score (0-100)

Product activity timeline - A feed of recent product events attached to the contact record. HubSpot does not have a native timeline view for custom events, but you can push events as engagement objects or notes so reps can see "User invited 3 teammates on Oct 15, viewed pricing on Oct 18, created 5 projects on Oct 20."

3 Ways to Get Product Data Into Your CRM

Native integrations - Some product analytics tools have pre-built HubSpot integrations. Mixpanel and Amplitude both offer limited syncs, but they typically only push cohort membership (yes/no flags like "is in high engagement cohort"), not raw event data or custom properties. These work for simple use cases but do not give you full control.

Reverse ETL - Tools like Hightouch and Census sync data from your data warehouse (Snowflake, BigQuery, Redshift) to HubSpot. This is the most flexible approach. You define your PQL logic in SQL, run it on a schedule, and push the results to HubSpot as contact properties or company properties. The tradeoffs:

Cost: Hightouch starts at $350/month (plus warehouse costs)
Engineering dependency: You need someone to write SQL, maintain the pipeline, and debug sync issues
Latency: Syncs typically run every 15-60 minutes, not real-time

Reverse ETL is the right choice if you already have a warehouse and a data team, but overkill if you are a 10-person company with a RevOps manager running HubSpot solo.

Purpose-built tools - Zoody syncs product usage data directly into HubSpot without a warehouse. You send events from your product to Zoody's API, define which properties to track, and Zoody pushes them to HubSpot in real time. No SQL, no engineering work. $149/month, flat rate. The limitation is that it only works with HubSpot (no Salesforce, no multi-CRM setups), and it does not replace your product analytics tool (you still need Mixpanel or Amplitude for user-facing dashboards and funnels).

How to Structure Product Properties in HubSpot

Create custom properties at the contact level and company level. Contact properties track individual user behavior. Company properties aggregate behavior across all users in an account.

Contact-level properties:

pql_score (number)
last_active_date (date)
activation_completed (single checkbox)
team_invites_sent (number)
projects_created (number)
pricing_page_views (number)
account_engagement_tier (dropdown: low, medium, high)

Company-level properties:

company_pql_score (number, rolled up from all contacts)
total_active_users (number)
power_users_count (number, users with engagement score > 50)
company_activation_status (dropdown: not activated, activated, power user)
total_team_seats_used (number)

You calculate company-level rollups using HubSpot workflows or by aggregating in your analytics tool before syncing. For example, a workflow can count the number of contacts at a company with activation_completed = true and write that to company.activated_users_count.

Building Your PLG Sales Workflow: From Signal to Close

Once you have product data in HubSpot and a PQL definition, you need automated workflows that route PQLs to sales and notify reps when to act.

Automating PQL Routing in HubSpot

Create a workflow that triggers when a contact's pql_score crosses your threshold (50, 75, 100, whatever you defined). The workflow should:

Update lifecycle stage - Move the contact from "Lead" to "Product-Qualified Lead" (you need to add PQL as a custom lifecycle stage if it does not exist).
Create a deal - Auto-create a deal in your sales pipeline with the contact as the primary contact. Name the deal "[Company Name] - PQL Expansion" and set the amount to your average contract value for this segment.
Assign owner - Route the deal to a sales rep based on:

Company size (assign enterprise accounts to senior AEs, SMB to inside sales)
Geography (if you have regional reps)
Product segment (if different reps specialize in different use cases)

Send notifications - Send a Slack message or email to the assigned rep with context: "New PQL: [Contact Name] at [Company]. Invited 5 teammates, created 8 projects, viewed pricing 3x. Last active today."
Set task - Create a task for the rep to reach out within 24 hours. Speed matters because the product signal is fresh.

Example workflow in HubSpot:

Enrollment trigger: Contact property pql_score is greater than or equal to 50 AND lifecycle_stage is not "Product-Qualified Lead" (prevents re-enrollment).

Actions:

Set property: lifecycle_stage = "Product-Qualified Lead"
Create deal:

Pipeline: "Sales Pipeline"
Stage: "PQL - Outreach"
Deal name: [Contact's company name] - PQL Expansion
Amount: $10,000 (your average deal size)
Owner: Same as contact owner

Set contact owner: Use "Rotate to owner" action to assign based on company.employee_count (if > 100, assign to enterprise team; else assign to SMB team).
Create task:

Title: "Reach out to PQL: [Contact name]"
Due date: 1 day from now
Assigned to: Deal owner

Send internal email notification to deal owner with usage summary.

You can also trigger workflows on specific high-intent actions, not just score thresholds. For example, if a user views the pricing page 3 times in one week, create a "Hot PQL" deal and notify sales immediately.

Crafting Product-Informed Outreach

The sales rep's first message should reference the user's product behavior. Generic "I wanted to reach out to see if you are interested in our product" emails get ignored. Product-informed emails get replies.

Bad email:

Hi [Name],

I wanted to reach out and see if you would be interested in learning more about [Product]. We help teams like yours with [generic value prop].

Would you be open to a quick call?

Good email:

Hi [Name],

I saw you invited 5 teammates to [Product] last week and created 8 projects. It looks like your team is getting value from the tool.

Most teams at this stage hit a few friction points: managing permissions across projects, reporting on team activity, and integrating with Slack. Our Team plan includes [specific features that solve these].

Worth a 15-minute call to walk through how other teams your size are using it?

The second email proves the rep actually looked at the account. It names specific usage patterns and ties them to paid features. It does not ask the user to explain their use case from scratch because the rep already knows it from the product data.

Other sales plays for PLG:

Usage-based pricing conversations - "You are at 80% of your free plan limit. Here is what the next tier looks like."
Feature unlock demos - "I saw you tried to use [gated feature] yesterday. Let me show you how it works on the paid plan."
Team expansion - "You have 6 active users. Our Team plan includes up to 20 seats for the same price as paying for 6 individual seats."

The goal is to remove friction and accelerate expansion, not to cold pitch someone who has not used the product yet.

Example: End-to-End PLG Sales Workflow

Let's walk through a real scenario.

Day 1: User signs up for your collaboration tool, creates an account, and invites two teammates.

Day 3: User creates their first project and completes onboarding. Zoody syncs activation_completed = true to their HubSpot contact record.

Day 7: User logs in daily, creates 5 projects, invites 3 more teammates (total of 5). Zoody updates projects_created = 5 and team_invites_sent = 5. The user's pql_score hits 60 (engagement + activation + adoption).

Day 7, 2pm: HubSpot workflow triggers on pql_score >= 50. Workflow updates lifecycle stage to "Product-Qualified Lead", creates a deal, assigns it to an AE based on company size, and sends a Slack notification to the AE.

Day 7, 4pm: AE sees the notification, reviews the contact's product activity timeline in HubSpot, and sends a personalized email: "I saw you invited your team and created 5 projects this week. Most teams hit a few friction points around [X]. Worth a quick call?"

Day 8: User replies, agrees to a 15-minute call.

Day 10: AE runs a demo focused on paid features (advanced permissions, reporting, integrations). User sees value, agrees to upgrade.

Day 12: Deal moves to "Closed Won." User converts from free to a $3,600/year Team plan.

Total time from signup to close: 12 days. Total AE touches: one email, one demo call. The product did the heavy lifting, and sales stepped in at the right moment with context.

Measuring and Optimizing Your PLG Sales Motion

You need dashboards that track how well your PQL definition, routing, and outreach are working. Without measurement, you cannot tell if a PQL score of 50 is the right threshold or if you should raise it to 75.

PLG Sales Metrics That Matter

PQL-to-opportunity conversion rate - What percentage of PQLs turn into actual sales opportunities (deals created)? If you generate 100 PQLs per month and only 10 turn into deals, your PQL criteria are too loose or your routing is broken.

PQL-to-customer conversion rate - What percentage of PQLs eventually close? This is your most important metric. Track it by PQL score threshold (do PQLs with a score of 75+ convert at a higher rate than PQLs with a score of 50-74?), by sales rep, and by product segment.

Time to close - How long does it take to close a PQL compared to a traditional MQL? PLG sales cycles are typically faster because the user already adopted the product. If your PQL sales cycles are as long as MQL cycles, something is wrong (either your outreach is too slow, your demo process is too heavy, or your PQL criteria are wrong).

Average contract value (ACV) - Track ACV for PQL-sourced deals vs. other sources. PQL deals might be smaller (converting a 5-person team) or larger (expanding a 50-person team that started as a single free user). This tells you where to focus sales effort.

Product-influenced revenue - What percentage of total revenue came from users who started as self-serve signups? This is the metric that justifies your PLG sales investment.

For a deeper guide on tracking PQL conversion and lifecycle stages, see how to track PQL to SQL conversion in HubSpot.

Building a PQL Performance Dashboard in HubSpot

Create a custom report in HubSpot with these charts:

PQL funnel - Bar chart showing:

Total contacts with lifecycle_stage = PQL
Total deals created from PQL contacts
Total deals closed from PQL contacts

PQL conversion rate by score - Table or bar chart:

Group PQLs by score range (50-59, 60-69, 70-79, 80+)
Show conversion rate to closed-won for each range
Use this to decide if your threshold should be higher or lower

Time to close by source - Line chart comparing:

Average days to close for PQL-sourced deals
Average days to close for MQL-sourced deals
Average days to close for other sources

ACV by source - Bar chart comparing average contract value across sources (PQL, MQL, outbound, etc.).

PQL velocity - Line chart showing PQLs created per week over the last 90 days. If this line is flat or declining while signups grow, your PQL criteria are too strict or your product is not driving activation.

You can build all of these in HubSpot's custom report builder using deal and contact data. If Zoody is syncing product properties to HubSpot, those properties are available as filters and dimensions in your reports.

Iterating on Your PQL Definition Based on Conversion Data

Your first PQL definition will not be perfect. After 30-60 days of running the workflow, pull a list of all PQLs and check:

What percentage converted to customers?
What percentage churned or went inactive after being marked as PQL?
What common traits do converting PQLs share (company size, feature usage, activation speed)?
What common traits do non-converting PQLs share?

If PQLs who invited 5+ teammates convert at 50% but PQLs who invited 2-4 teammates convert at 12%, raise the invite threshold. If PQLs who activated in their first 7 days convert at 35% but PQLs who took 14+ days convert at 8%, add activation speed to your scoring model.

PQL scoring is not set-it-and-forget-it. Revisit your criteria every quarter based on actual conversion data. The best PLG sales teams treat PQL scoring like a product feature, constantly iterating on signals and thresholds.

FAQ

What is PLG sales?

PLG sales is a sales strategy where sales reps contact users based on product usage signals rather than traditional lead gen. Users sign up, activate, and adopt the product on their own. Sales reaches out only after the user demonstrates buying intent through their behavior (inviting teammates, hitting usage limits, viewing pricing). The product qualifies the lead, and sales accelerates expansion or conversion to paid.

What does PLG stand for?

PLG stands for product-led growth, a go-to-market strategy where the product itself drives user acquisition, activation, and expansion. Users can sign up and start using the product without talking to sales. The product delivers value immediately, and growth happens through word-of-mouth, viral loops, and self-serve upgrades. PLG sales layers a sales motion on top of this model to capture larger deals and accelerate expansion.

What companies use PLG?

Slack, Dropbox, Zoom, Notion, Figma, Airtable, Calendly, Loom, and Miro all use product-led growth strategies. Most started with self-serve adoption and later added sales teams to close enterprise deals and expand accounts. B2B SaaS companies with freemium models, free trials, or usage-based pricing are the most common adopters of PLG.

What are examples of PLG?

Slack's free tier lets teams use the product for 10,000 messages, then sales contacts teams approaching the limit to upgrade. Zoom lets anyone host a 40-minute meeting for free, then upgrades them to paid for longer meetings. Figma offers free individual accounts and converts teams when multiple people from the same company sign up. Notion's free personal plan converts to paid when users invite teammates or need advanced features.

How do you identify a product-qualified lead (PQL)?

A PQL is identified by combining engagement (usage frequency), activation (completed key setup steps), adoption (used core features), fit (company size, role), and intent (viewed pricing, hit limits). Build a scoring