You've got users in your product who haven't converted to paid plans. They're using your free tier or trial, showing real engagement - they're not cold, they're not hot, they're somewhere in the middle. And most teams leave money on the table here because they don't know how to talk to these people.

PQL (Product Qualified Lead) cold email is different from traditional cold outreach. You're not prospecting into the dark. You have real usage data. You know what they built, how they're using your product, what features they've touched. That changes everything about how you write and what you can say.

Why PQL Leads Are Different (And Why Your Current Approach Fails)

A PQL isn't cold. But most teams treat them like cold leads - generic subject lines, generic value props, zero personalization beyond a first name. That's the mistake.

PQL leads have already made a decision: they trust you enough to use your product. They've invested time. They understand your core value. What they're missing is a reason to move from free to paid - or a realization that they need the features locked behind your paywall.

The email needs to reflect that context. It's not "here's why you should try our product." It's "here's what we noticed you doing, and here's what you're missing."

That specificity matters because it moves the conversation from theoretical to real. You're not pitching features. You're pointing at their actual usage and saying, "I see you building X. Most teams doing X actually need Y to scale it."

The PQL Email Framework

Here's the structure that works:

Line 1 (The Observation): Reference something specific about their usage. Not vague. Specific.

Line 2 (The Implication): What that usage pattern typically means they're trying to do.

Line 3 (The Gap): What your free tier or their current setup can't handle at scale.

Line 4 (The Offer): A quick call to see if it applies to them. No pressure.

Here's what that looks like in practice:

Hi [Name], I noticed you've built 12 workflows in [Product] and synced them to Slack - that's actually 3x more automation than most free users set up. Teams that build that much workflow automation usually hit a wall when they need to manage them across multiple team members or audit who changed what. Our paid plan includes team collaboration and full audit logs - most teams like yours end up needing it within a month or two. Worth a quick call to see if it's relevant? I've got 15 min Tuesday or Thursday afternoon. [Your Name]

Notice what's happening here: you're not selling. You're reflecting their reality back at them and pointing out the logical next step. The context is doing 90% of the work.

Getting the Usage Data Right

This whole approach only works if you actually know what they're doing. Most teams have this data - they just don't extract it cleanly for outreach.

You need: feature usage (what they've built or configured), frequency (how often they're in the product), and scope (how many team members, how many workflows, how much data).

Your product should expose this in an admin dashboard. Export it. Filter for accounts that hit specific thresholds - typically free users who've been active in the last 30 days and have hit some meaningful usage milestone (10+ workflows, 100+ API calls, 5+ team members invited, whatever makes sense for your product).

The threshold matters. You want users who've done enough to understand your product's core value but haven't hit the ceiling of what the free tier can do. Too early and they're not ready. Too late and they've already decided free is fine or they've moved to a competitor.

A good rule: target free users who've been active in the last 15-30 days and have hit 60-70% of your free tier's limits or feature depth.

Subject Lines That Work for PQL

Your subject line should signal that this email is about their specific account, not a generic pitch.

Bad: "Unlock more features in [Product]"

Good: References their usage or activity.

Noticed you've set up 12 workflows

Or even simpler:

Quick question about your [Product] setup

The open rates are better (35-45% vs 12-18% for generic lines) because it signals that someone actually looked at their account. You're not broadcasting. You're responding to their actions.

Timing and Sequence

Don't send one email and call it done. PQL users are busy - they're using your product, but they're not thinking about upgrading unless you remind them.

Send your first email 3-5 days after they hit your usage threshold (when the context is fresh but they've had time to do more with the product). If no reply in 6 days, send a second email - this one shorter, referencing the first, and with a slightly different angle.

Hey [Name], One more thing - the audit logs I mentioned in my last email usually save teams like yours 2-3 hours per week in troubleshooting. Happy to show you how fast it is to set up. [Your Name]

Wait another 5-6 days. If still nothing, one final email - this one acknowledging they might be busy and offering a specific, short time slot. Then move on.

Most PQL emails convert on the first or second touch. If they're not responding by touch three, something's off - either the timing is wrong, the person isn't the decision-maker, or they genuinely don't need the upgrade.

What Not to Do

Don't mention price in the first email. They're not ready to think about cost yet. They're still in "do I need this?" mode.

Don't be vague about what you're referencing. "I saw you're using our product" is worthless. "I saw you've created 47 custom fields and invited 8 team members" is compelling.

Don't ask for a call longer than 15 minutes. Most PQL users will take a 15-minute check-in. They won't block 30 minutes with someone they don't know.

And don't batch these out as automated sends without human review. You want to catch mistakes - wrong usage data, mis-identified decision makers, accounts you shouldn't be reaching out to. Spend 30 seconds on each one before it goes out.

The Real Gap: Scale and Execution

Knowing this framework and running it reliably at scale are two different things. You need to extract usage data cleanly from your product, segment it properly, write personalized copy for each segment, time the sends, track responses, and know when someone replies so you can actually follow up.

Most teams we talk to can do this for 10-20 accounts. Beyond that, the manual work breaks down - data gets stale, emails don't go out on schedule, follow-ups get lost. That's where the real conversion leaves the table.

Related Guides