# Product Qualified Lead Email Plays

> Score product qualified leads, then run the email and sales handoff plays each score triggers, with thresholds, routing rules and a sample scoring model.

Source: https://saas-marketing.net/playbooks/product-qualified-lead-email-plays/
Topic: SaaS Email Marketing
Type: playbook
Published: 2026-09-11
Last updated: 2026-09-11
Publisher: SaaS Marketing (saas-marketing.net)
License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/playbooks/product-qualified-lead-email-plays/

## Short answer

A PQL email system has three parts: a weighted usage score, thresholds that trigger different plays, and routing rules that stop marketing and sales contacting the same account twice. Score activation, seats invited, usage volume, integrations connected, admin role and firmographic fit. Below threshold, run self serve nurture. At threshold, send assisted onboarding. Above it, hand to a rep within four business hours. Recompute weekly with decay so stale spikes stop firing plays.

## Key takeaways

- PQL scores must decay weekly, because a usage spike from three weeks ago is not current buying intent.
- Integration connected and second seat invited are the two signals that predict conversion most reliably in PLG accounts.
- Set a four hour sales SLA on above threshold accounts, and suppress marketing email the moment a rep owns one.
- Suppress every PQL play on accounts with an open opportunity, or reps will be undercut by a nurture email.
- Report PQL sourced pipeline separately from marketing sourced, or the two will double count each other.
- Most PQL models fail on identity resolution, not on scoring maths, so fix the account to contact mapping first.

---

Most PLG teams have the data and no system. Product events land in Amplitude or PostHog, someone builds a Looker board of "highly engaged trials", and a rep occasionally scrolls it on a Friday. Nothing fires automatically, nobody owns the contact, and the same account gets a nurture email and a cold rep email in the same afternoon.

This playbook closes that gap. A weighted score, three thresholds, three plays with the actual copy, and the routing rules that stop the two channels colliding. The opinion up front: recompute scores weekly with decay, because a [product qualified lead](/glossary/product-qualified-lead/) who went quiet in August is not a buyer in September.

## What does a working PQL scoring model look like?

Six weighted signal groups, scored out of 100, with behaviour decaying and fit staying fixed. Here's a model that works for a mid market collaboration or data product with a free tier.

| Signal | Points | Why it earns that weight |
| --- | --- | --- |
| Activation milestone completed | 20 | The account got to first value. Everything below is meaningless without it. |
| Second seat invited | 15 | One person exploring is curiosity. Two people is an internal use case. |
| Five or more seats active in 14 days | 15 | Team adoption, which is where expansion revenue lives. |
| Integration connected | 15 | Highest switching cost signal in the model. Someone wired you into their stack. |
| Usage at 70 percent of plan limit | 10 | The upgrade conversation writes itself. |
| Admin or manager role on the acting user | 10 | Budget proximity. A viewer role scores zero here. |
| Firmographic fit, 50 plus employees in target industry | 10 | Static, no decay. |
| Pricing page visit in last 7 days | 5 | Weak on its own, useful as a tiebreaker. |

Thresholds: below 40 is self serve nurture, 40 to 64 is assisted onboarding, 65 and above goes to a rep. Those cut points are a starting position, not a law. Tune them to rep capacity, which we'll get to.

Apply 25 percent weekly decay to every behavioural row and none to firmographic fit. An account that hit 72 in week one and did nothing since lands at 41 by week four and drops out of the sales queue on its own. That is the behaviour you want.

The full mechanics of building this, including how to handle products where activation is fuzzy, sit in our [PQL scoring model guide](/guides/pql-scoring-model/). If you're still arguing internally about whether these replace MQLs, the [MQL vs PQL comparison](/comparisons/mql-vs-pql/) settles most of it.

## Play one: self serve nurture below 40

Goal is activation, not a meeting. These accounts have not received value yet, and a rep email to someone who hasn't finished setup is a waste of both calendars.

Four emails over 14 days, triggered by what's missing rather than by day count.

**Email 1, sent 24 hours after signup if activation is incomplete.** Subject: "Stuck on the import step?" Body, roughly 80 words: name the exact step they abandoned, give one link straight back to it, offer a 90 second Loom walkthrough. Sign from the product, not a person.

- **Email 2, day 4, if still not activated.** Show one concrete outcome from a customer in their industry, with the number. Not a case study PDF. Two sentences and a link to the relevant docs page.

**Email 3, day 8, triggered by their most used feature.** If they've been living in one part of the product, show the adjacent thing that usually comes next. This is the highest performing email in most self serve programs because it's genuinely useful.

**Email 4, day 14.** A single question: what were you hoping to do that you haven't done yet? Plain text, reply to a real inbox, and route replies to support rather than sales.

Putting a demo CTA in email one. An unactivated user has no reason to want a demo and every reason to unsubscribe. The [activation sequence guide](/guides/activation-email-sequences/) covers the sequencing logic in more depth, and the pattern is consistent: earn the meeting after the value, never before.

## Play two: assisted onboarding between 40 and 64

These accounts are working but haven't spread. The play is human help without a sales pitch, delivered by whoever owns onboarding.

Two emails plus one in app prompt.

**Email 1, sent from a named onboarding person, plain text.** Roughly 60 words. "I saw you connected Slack and you've got two people in the workspace. The teams that get the most out of this usually add their reporting lead in week two. Want me to walk them through it? Fifteen minutes, here's my calendar." Reference the actual integration they connected. Generic versions of this email get ignored.

**Email 2, five days later, only if no reply.** Send an asset instead of asking for time. A three minute Loom of the specific workflow their usage pattern suggests they're building. No calendar link. Close with "reply if you want me to set this up with your team."

The in app prompt runs alongside: an invite teammates nudge shown to admin users only, positioned at the moment they complete a task that would be better shared.

Around 30 to 40 percent of accounts in this band will cross 65 within a month if the play works. That crossing is the handoff trigger, not a manual decision.

## Play three: direct sales outreach above 65

Assign the account to a rep inside four business hours and let the rep write the first email themselves. Templated HTML from an account executive reads as a campaign, gets filtered like one, and replies at a fraction of the rate.

Give the rep a briefing card, not a sequence. It should contain: the top three scoring signals with dates, which integration is connected, seat count and who the admin is, the plan limit they're nearest, and the last three product events. Salesforce and HubSpot can both render this on the lead record with a bit of work, and it's worth the work.

The rep's first email should be four sentences. Reference one specific thing the account did. Ask one question about what they're trying to achieve. Offer one concrete next step. No deck, no "quick chat", no calendar link in email one.

**Handoff mechanics that prevent double contact**

## How do you stop marketing and sales emailing the same person?

One owner at a time, enforced in the system rather than in a meeting. That's the whole answer, and almost every PLG team gets it wrong for at least a year.

Three rules that make it work:

- A PQL flag sets a suppression property on every contact at the account, and your ESP segments exclude that property by default rather than by opt in.
- Sales ownership expires. Fourteen days without logged activity releases the account back to marketing automatically.
- Transactional and product notification email is exempt. Security alerts and usage warnings keep sending regardless of ownership.

The hard case is the account with an open opportunity and a separate self serve team using the free tier. Enterprise accounts do this constantly. Suppress the PQL play at the account level, route the usage signal to the opportunity owner as an internal notification, and let the rep decide. The routing detail here overlaps heavily with [PQL scoring and routing](/guides/product-qualified-lead-scoring/), which covers the CRM side properly.

The failure is almost never the weights. It's that your event stream identifies users by email while your CRM identifies accounts by domain, and free email domains collapse forty unrelated trials into one account. Fix the mapping in Segment or your warehouse before you tune a single point value.

## How should PQL pipeline be reported?

As its own source, sitting next to marketing sourced and sales sourced rather than inside either. Three numbers, reviewed monthly.

| Metric | Definition | What good looks like |
| --- | --- | --- |
| PQLs created | Accounts crossing the sales threshold in the period | Roughly matches rep capacity, within 20 percent |
| PQL to opportunity rate | Opportunities created within 30 days of the flag | 20 to 40 percent with a tight threshold |
| PQL sourced pipeline | Opportunity value where the PQL flag preceded the first sales touch | Reported separately, never merged into marketing sourced |

The trap is double counting. An account that downloaded a template in March and crossed the PQL threshold in June will be claimed by both teams. Pick a precedence rule, write it down, and apply it consistently: we'd say the most recent qualifying event before opportunity creation wins, because it's the one the rep acted on.

Worth tracking alongside these: the share of PQLs that decay out of the queue without being worked. If it's above 20 percent, your SLA is broken or your threshold is too loose for the team you have. The broader set of measures is covered in [PQL metrics](/glossary/product-qualified-lead/).

## What does this cost and where does it fail?

Build cost is real. Expect four to six weeks of combined data engineering and lifecycle work to get events flowing reliably, the score computing on schedule, and the CRM flags writing back. Teams that try to do it in a fortnight ship a score nobody trusts.

Three failure modes worth naming. First, reps stop believing the flag after two weeks of bad accounts, and belief is very hard to rebuild, so tighten the threshold before launch rather than after. Second, the score becomes a committee artefact with fourteen signals and no one able to explain why an account scored 63. Keep it to eight rows maximum. Third, nobody owns the model after launch, weights never change, and a product update in month five makes activation mean something different without the score noticing.

Set a quarterly review with one job: check whether the signals still predict conversion, using last quarter's closed deals. If integration connected has stopped predicting anything, drop its weight.

## What to do next

Build the score before you write a single email. Pick your six signals, agree what activation means with product, and confirm the account to contact mapping holds. Run the model in read only mode for two weeks and eyeball the top 20 accounts each week: if a rep would be happy to call them, the thresholds are right.

Then ship play three first, because it's where the revenue is, and add plays one and two once the routing is proven. Pair this with [churn prevention campaigns](/playbooks/churn-prevention-email-campaigns/) on the other side of the lifecycle, borrow structure from the [onboarding teardowns](/guides/saas-onboarding-email-teardowns/), and make sure the whole thing sits inside your broader [email program](/saas-email-marketing/) rather than beside it.

## Frequently asked questions

### What is a product qualified lead?

A product qualified lead is an account that has shown buying intent through product usage rather than through a form fill. Typical signals include completing activation, inviting teammates, connecting an integration, or hitting a plan limit. Unlike an MQL, which measures interest in your marketing, a PQL measures value already received from the product itself.

### What signals should a PQL model score?

Six categories cover most SaaS products: activation milestone completed, seats invited, usage volume against plan limits, integrations connected, the role of the user acting, and firmographic fit such as company size and industry. Weight integrations and seat invites highest, because both represent switching cost and internal advocacy rather than individual curiosity.

### How often should PQL scores be recalculated?

Weekly, with decay applied. A score that only accumulates turns every long lived trial into a false positive. Apply roughly 20 to 30 percent decay per week to behavioural components while leaving firmographic fit static, so an account that went quiet a month ago drops below threshold instead of sitting in a rep's queue forever.

### Should marketing or sales email a PQL first?

It depends on the threshold. Below the sales threshold, marketing owns the account and sends product led nurture. Above it, the account is assigned to a rep and marketing suppresses all campaign email for that contact. The only rule that matters is that exactly one owner exists at any moment, written down and enforced in the CRM rather than agreed verbally.

### How is PQL sourced pipeline different from marketing sourced?

Marketing sourced pipeline starts with a marketing touch such as a form fill or a demo request. PQL sourced pipeline starts with a usage threshold crossing on a self serve account. Report them separately. If you fold PQLs into marketing sourced, you lose the ability to tell whether the product or the campaigns created the opportunity, which is the one thing a PLG board wants to know.

### What PQL to opportunity conversion rate is realistic?

It varies hugely with how tight your threshold is. A loose threshold produces many PQLs converting in the low single digits. A tight one produces far fewer converting at 20 to 40 percent. Tune the threshold against rep capacity: pick the score that produces roughly the number of accounts your reps can work properly in a week, then hold it for a quarter before changing it.

### Do PQL emails need to come from a sales rep or from the company?

Below threshold, send from the product or a named lifecycle sender. At and above threshold, send from the assigned rep's own address with plain formatting and no tracking pixels, because a templated HTML email from an account executive reads as a campaign and gets treated like one. The reply rate difference is usually large enough to see in a month.