Two questions so this lands right. What's your bar for a PQL — a usage threshold, a specific activation event, or a model score? And when one fires, do you route to a named AE by account, or round-robin a pool?

Activation event plus a usage threshold — hit the 'aha' action and cross 3 active seats in a week. Route by account if there's an owner, else round-robin. And start strict; I'd rather miss a few than flood the team.

Got it — high bar, account-aware routing, conservative to start. I'll build the score in dbt off the Snowflake usage tables so it's versioned and auditable, then sync to Salesforce via Hightouch. Piloting on one segment before the whole funnel.

Built and scoring correctly on historical data. Since it writes leads into Salesforce and pings AEs, I'd pilot on one segment and check that the PQLs are real before opening the floodgates. Agree?

Yes — pilot on the self-serve segment and show me whether the PQLs actually convert.

Strong. Keep it on the pilot segment and we'll widen to the full funnel next month.

In rolloutagent · warehouse-pql

PQL Routing Agent

Daily schedule

Snowflake usage

dbtdbt score

SFHightouch → Salesforce

Ping AE

Score versioned in dbt · pilot segment: self-serve · strict bar by design

In rollout. Your best signups now reach an AE the day they get hot, scored off a definition anyone can read in dbt — not lost in the warehouse. Ready to widen on your word. Details in the report.