Expansion Signal to PQL Handoff Playbook 2026

An expansion signal is a compound fact, not a single number. Set the trigger on the combination that predicts real appetite:

• Engagement score sustained at 85+ — not a one-week spike.
• Seat utilization above 80% of the purchased plan.
• Repeated collisions with plan limits: API quotas, records, projects, whatever your pricing meters.
• Fire it with the account's segment attached, so a strategic logo and a self-serve team don't land in the same queue.

The trigger carries all four fields with it. That payload is the difference between "an alert" and "a case" — everything downstream reads from it.

Not every busy account is a buyer. Score the signal against the expansion profile you see in accounts that actually upgraded — then emit the fields the handoff needs:

• PQL score — how closely this account matches your historical expanders.
• Expansion type — seats, tier, add-on, or a bigger consumption commit. The pitch differs; label it now. Consumption deals especially: overage patterns are the evidence, and the ask is a commit that saves them money.
• Champion contact — the most active power user, straight from the usage data. The AE should never have to ask "who do I talk to?"
• Current ARR & plan — sizing context, so the opportunity is created with a realistic amount instead of a placeholder.

Write the profile down and revisit it quarterly against closed expansions. A PQL definition nobody maintains drifts into a lead score nobody trusts.

One rule, read from the qualified record: does this account cross your sales-ready bar — PQL score above threshold, expansion type that needs a human (tier changes, multi-team seats), or ARR above your self-serve ceiling? If yes, it goes to the AE motion. If not, let the product keep selling: prompts at limit moments convert self-serve expansions without burning AE time on deals that would have closed themselves.

Create the expansion opportunity in the CRM automatically, pre-filled from the payload: expansion type in the name, amount sized from current ARR and seat gap, champion as the contact, and the usage evidence — score, utilization, limit collisions — in the description. An opportunity that starts as a formatted case file gets worked; one that starts as an empty record gets snoozed.

Post to #expansion and tag the account owner. The message should read like a briefing, not a notification: account, segment, what fired the signal, PQL score, expansion type, champion, and a link to the opportunity. A shared channel does double duty — leadership sees expansion signals flowing, and unclaimed ones are visible instead of buried in someone's inbox.

The expansion call is a review of facts the customer already knows, which is what makes it feel like service instead of sales. Open with the observed usage: "your team is at 47 of 50 seats and hit the API limit nine times this month." Then the ask is arithmetic, not persuasion.

• Touch the champion first — they feel the limits daily and will carry the case to the buyer.
• Bring the right-sized proposal from the expansion-type field: a seat bump is an email, a tier change is a meeting, and a consumption commit is a spreadsheet showing what last quarter's overages would have cost on the bigger plan.
• Log the outcome and reason code. Your PQL profile improves only if wins and losses flow back into it.

Accounts below the sales-ready bar get in-app prompts triggered by the same limit data: an upgrade nudge when they hit a quota, a "you're at 9 of 10 projects" note near the ceiling, pricing on the page where the limit lives. Suppress the prompts the moment an opportunity opens — nothing undercuts an AE mid-deal like the product flashing a self-serve discount.

The play ends when the expansion closes — or explicitly doesn't. Either way, record which signal fired, the PQL score at handoff, and the outcome. After a quarter you'll know your true conversion rate by expansion type, which thresholds are too eager, and which usage patterns predict the biggest deals. That's the data that turns a lead score into a pipeline machine.