Trigger-Based Sequence for Product Signals

This sequence is built for Heads of Growth and RevOps at PLG SaaS companies. Use it when a user or workspace hits a specific product usage threshold (a PQL signal) but hasn't converted to a paid plan.

The goal is not to hard-sell, but to open a consultative conversation based on an action they just took inside your product. This is about converting intent into revenue, at scale.

This is a tight, fast-moving sequence designed to capitalize on a moment of high intent. It blends automation with a consultative tone.

1. Steps: 5
2. Duration: 12 days
3. Channels: Email + LinkedIn

This sequence lives and dies by the trigger. The only personalization required is the {{product_signal}} token. This should be a clear, concise description of the user's action, for example:

1. invited 5 teammates
2. created your 10th project
3. synced your CRM integration

The rest of the sequence is templated. The power comes from the timing and context, not from deep, manual research. This is designed for scalable execution across thousands of PQLs per month.

A PQL sequence can generate thousands of automated emails per day. Sending this from your primary corporate domain is a catastrophic risk. Here’s the infrastructure required:

1. Safe Send Limits: Keep sends to 30-50 emails per inbox per day to avoid tripping spam filters.
2. Dedicated Domains: Use secondary domains (e.g., getcompany.com instead of company.com) exclusively for this outreach. If one gets burned, your core operations aren't affected.
3. Inbox Rotation: To send 1,000 emails a day, you need 20-30 inboxes (1000 / 40 sends avg). Manually managing this is impossible; automation is required to rotate sends across the pool.

For PLG SaaS, your recipients are often using corporate inboxes (user@customer.com). If Microsoft or Google flags your primary sending domain because of high-volume outbound, it could impact deliverability for all your company's email, including critical product notifications, password resets, and support messages. This is an existential risk to a product-led business.

Tools like SuperSend exist to handle this infra and orchestration so your growth team can focus on converting PQLs, not duct-taping an email sending architecture.