Product-led growth gets talked about as a marketing strategy. It is actually a data strategy. The moment a user signs up for your free trial, they start telling you exactly how likely they are to pay, through every click, every feature they open, and every session they skip.
Most SaaS sales teams have no idea any of that is happening. None of it is in their CRM.
What is a Product-Qualified Lead?
A Product-Qualified Lead, or PQL, is a user who has reached a meaningful milestone inside your product. They activated a key feature, hit a usage threshold, invited a teammate, or upgraded their storage. Whatever the milestone is, they are doing the thing your product is designed to do.
That makes them different from every other lead type in your funnel. A Marketing-Qualified Lead clicked an ad or downloaded an ebook.
A Sales-Qualified Lead filled out a demo form. Neither has actually used your product. A PQL has, and in most PLG companies, that difference shows up as a 3% conversion rate versus a 25% one.
Furthermore, PQLs are consistently underused. Not because companies do not want to act on them, but because the signal lives somewhere the sales team cannot reach.
Why the PQL signal gets wasted without CRM integration
Product analytics tools capture this data well.
Segment, Mixpanel, PostHog, and Amplitude track every session, every feature interaction, and every drop-off point with precision. The dashboards are detailed. The data is there.
However, your sales team is not in those dashboards. They are in the CRM. And in most PLG SaaS companies, those two systems do not talk to each other.
The result is a structural disconnect. Your product knows which users activated three core features in a seven-day trial.
Your reps are calling people who downloaded a whiteboard template six weeks ago. Meanwhile, the user who is two steps from converting sits uncontacted in your product database, not in your pipeline.
This is not a prioritisation problem. It is a data infrastructure problem. Specifically, it is fixable.
Here is what four common PQL triggers look like in practice.
1. Trial activation trigger
A user activates three core features within seven days of signing up. Salesforce creates a task for a rep to reach out with a targeted expansion message. The rep sees the activation data directly on the Lead record.
2. Churn risk alert
A user’s engagement drops below their baseline for 14 consecutive days. Salesforce creates a CS alert before the churn event. The CS team can intervene with full context on what the user did and did not do.
3. Account expansion signal
Five or more users at the same account invite colleagues during the trial period. Salesforce scores the Account higher and moves it into an expansion workflow automatically.
4. Free-to-paid attribution
A free-to-paid conversion is tracked as a closed Opportunity, connected to the original trial Lead record. Marketing attribution becomes real, not estimated.
| Situation | Without PQL data | With PQL data in Salesforce |
|---|---|---|
| Who reps contact first | Demo form leads, regardless of product activity | Users who activated key features, ranked by engagement score |
| What reps see on a Lead record | Name, email, company, source | Features activated, sessions logged, days since last login, PQL status |
| Churn detection | Customer cancels, CS finds out after the fact | Usage drop triggers CS alert at day 14, before churn event |
| Free-to-paid attribution | Estimated or modelled based on last-touch channel | Closed Opportunity linked directly to original trial Lead record |
| Account expansion signals | No visibility until a user reaches out or upgrades manually | Automatic score increase when 5+ teammates invited during trial |
| PLG funnel visibility | Sign-up volume and revenue, nothing in between | Full funnel: signup, activation rate, PQL rate, closed-won from trial |
How to build this in Salesforce
The most practical starting point is a set of Custom Fields on the Lead or Contact record that reflect product activity. You do not need a full Customer Data Platform to get started. You need a clean data feed and clear trigger logic.
Step 1: Define your PQL criteria
Before any configuration, decide what product-qualified means for your specific product. Pick two or three behaviours that correlate with paid conversion in your existing data. Common examples include activating a specific feature, reaching a usage volume threshold, or completing an onboarding checklist.
If you do not have conversion data yet, start with Salesforce Trailhead’s PLG resources or the Salesforce Admins blog for benchmark guidance on typical SaaS activation signals.
Step 2: Connect your product data to Salesforce
The most common paths are a native integration from your analytics tool, a Salesforce-connected webhook from your product backend, or a middleware tool like Segment Connections or Census. Each approach writes product events into Salesforce fields or Custom Objects.
Step 3: Build the trigger logic in Salesforce Flow
Use Salesforce Flow to create the automation. When a product field meets your PQL criteria, Flow triggers an action. That action can be a task assignment, a lead status change, a CS queue alert, or an Opportunity creation.
Step 4: Create the reporting layer
Build a Salesforce Dashboard that shows your full PLG funnel in one view. Trial signups by source, activation rate by cohort, PQL conversion rate, and closed-won from trial. That view tells you whether your product experience is working as a sales motion, not just as a user acquisition tool.
The trial-to-paid dashboard that makes PLG measurable
Most PLG companies know their sign-up volume. They know their revenue. What they often do not know is the middle part: activation rates, PQL rates, and where the funnel breaks.
When you build this correctly in Salesforce, a single dashboard covers trial signups by source, activation rate by cohort, PQL conversion rate, and closed-won from trial. Additionally, you can slice that view by plan type, acquisition channel, or rep to understand what is driving results and what is not.
Without that view, you are making product decisions, pricing decisions, and hiring decisions based on incomplete data. That is a considerably more expensive problem than the cost of the integration.
The product experience you spent months building is either converting free users into paying customers, or it is not. Salesforce is how you find out which one it is.
Running a free trial or freemium model and want to actually know which users are close to converting? This is one of the most high-impact things you can build in Salesforce for a PLG SaaS. If you want to talk through what your specific setup would look like, reach out to us. Follow us on LinkedIn for weekly SaaS and Salesforce content.
