How to Build a Product-Led Sales List in Common Room
Direct answer: A product-led sales list in Common Room combines a product qualified lead filter with at least one buying signal (job posting, pricing visit, or community question), capped at roughly 50 new accounts per rep per week.
Every PLG company builds the PQL list once and then discovers the same thing: reps call too many free users, conversion is 1-2%, and the sales team concludes product-led sales doesn’t work. The list was the problem, not the channel.
What separates a PQL from an active free user?
Activity is not intent. A user who logs in daily and runs 200 API calls may be a hobbyist. A user who logs in twice a week, invites a teammate, and exports a report is showing organizational behavior.
The distinction that matters: does the usage look like it belongs to a company that could pay? Invites, team seats, admin settings changed, and exports are all signals of an organization forming around the tool.
What should the score threshold be?
Set it by reverse-engineering your last 50 paying customers rather than picking a number from a blog post.
- Pull the last 50 self-serve conversions in your warehouse.
- For each, find the usage threshold they crossed in the 14 days before paying.
- Take the 25th percentile of that threshold — not the median. You want to catch accounts slightly before they decide, not after.
- Apply that threshold as a hard filter in Common Room, then add the buying-signal layer.
In our case, 50 conversions produced a filter of “3+ teammate invites and 5+ sessions in 14 days”. That segment held 340 accounts out of 11,000 free users — a workable size.
How do you layer in non-product signals?
Product data alone will find your power users. It won’t tell you which power users work somewhere that’s hiring, growing, or evaluating competitors.
| Layer | Signal | Why it matters |
|---|---|---|
| Org growth | 2+ open roles in the last 60 days | Budget exists and is moving |
| Evaluation | 2+ pricing page visits in 21 days | Someone is comparing options |
| Support load | 3+ help center articles on the same topic | Trying to scale past free tier limits |
| Community pull | Asked a setup question in Slack | Implementing, not browsing |
Two layers minimum. A list with only product filters is a filtered changelog, and reps learn to ignore it within a month.
How big should the weekly queue be?
Fifty per rep per week, hard cap. At a 1.5% meeting-booking rate that’s roughly one meeting per rep per week and it stays inside what a rep can actually personalize.
Queues over 100 get skimmed. Skimming produces generic outreach, generic outreach poisons your brand with your best users, and those users are the ones most likely to churn when they get a canned email from sales.
What breaks the model in practice?
Duplicate accounts. One company with five free workspaces produces five PQLs. Deduplicate on domain before the sync, or a rep will call the same office five times. Common Room’s account rollup helps, but you still need a domain-level filter.
Reps gaming the queue. Once a commission plan touches PQL conversion, reps start cherry-picking the easy accounts and ignoring the rest. Rotate assignment by round-robin rather than letting reps pick, at least for the first two quarters.
Sales becoming an interruption. If your best users start complaining about outreach in the community, you’ve already gone wrong. Set a rule: no outreach to accounts that have submitted a support ticket in the last 14 days. They’re dealing with something real, not shopping.
How do you measure whether it’s working?
Three numbers, checked monthly:
- Queue conversion: PQLs that book a meeting within 30 days. Target 4-8% for product-led, not the 20% of outbound.
- Free-to-paid lift in the queue vs the pool: should be at least 3x.
- Churn in the queue: if contacted users churn more than untouched ones, your outreach is hurting.
That third number is the one teams skip, and it’s the one that reveals whether product-led sales is helping or just adding noise to a funnel that was already converting.
Should you do product-led sales at all?
Only if the product has a real self-serve motion with meaningful free usage. If free users average two sessions and leave, there’s no behavior to qualify on and you’re doing outbound with extra data.
Teams under 5,000 free users should skip the tooling entirely and manually review a spreadsheet weekly. Common Room becomes worth paying for around the point where the manual review stops fitting in one person’s afternoon.
Key Takeaways
- Derive score thresholds from your last 50 conversions; use the 25th percentile.
- Combine product usage with at least one buying signal; activity alone is not intent.
- Cap queues at 50 per rep per week — bigger lists get skimmed and burn goodwill.
- Deduplicate by domain; one company often produces several free workspaces.
- Watch churn in the contacted cohort — rising churn means outreach is harming the funnel.
