operationalize-pql-routing — Claude Code command for PQL scoring
operationalize-pql-routing turns product signals into a scoring and routing plan for product-qualified leads, then hands back a spec, an automation checklist and a follow-up playbook.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/operationalize-pql-routing.mdWhat operationalize-pql-routing does
Five steps run in order: reading telemetry, entitlement and intent fields for the segment; setting scoring weights with decay and enrichment; drawing a routing map with owners and queue priority; packaging messages, assets and SLAs per destination; wiring dashboards and alerts for backlog, conversion and SLA adherence.
You pass --segment, --threshold, --destinations and --alerts, plus an optional --playbook set to upsell, adoption, expansion or churn-save. Back comes a scoring and routing spec as JSON or CSV with a written explanation, an automation checklist for CRM, CS and revenue tools, and a follow-up plan naming sequences, assets and owners. Two subagents carry the work, pql-ops-lead and product-adoption-strategist; the pql-framework and usage-health-scorecard skills hold the scoring method and the conversion metrics.
The threshold is yours to pick, since the command does not work it out from your data. Set it too low and nothing gets filtered out. --playbook is the one argument you can drop, and the sequences go with it, leaving just the routing map.
What it helps with
- turn product signals into a weighted PQL score
- assign owners and queue priority per destination
- build a follow-up sequence for expansion or churn-save
- alert the team when an SLA slips
- export the routing spec as JSON or CSV
Example prompts for the agent
- Run
/product-led-growth:operationalize-pql-routing --segment startup --threshold 80 --destinations crm,cs --alerts trueand show me the routing map. - Use
/product-led-growth:operationalize-pql-routing --segment enterprise --threshold 80 --destinations crm,marketing --playbook expansion --alerts false, I need the expansion playbook. - Build the scoring spec with
/product-led-growth:operationalize-pql-routingfor the scaleup segment and give me the JSON plus the automation checklist.
How to install operationalize-pql-routing
Manually: put the files in place
.claude/commands/operationalize-pql-routing.mdCall it with /operationalize-pql-routing. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/operationalize-pql-routing.mdCall it with /prompts:operationalize-pql-routing. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/operationalize-pql-routing.prompt.mdManually: put the files in place
.gemini/commands/operationalize-pql-routing.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about operationalize-pql-routing
How do I install operationalize-pql-routing in Claude Code?
Place the command file at .claude/commands/operationalize-pql-routing.md inside your project, then call /product-led-growth:operationalize-pql-routing with the flags you need.
What does operationalize-pql-routing do?
It works through segment signals, scoring weights, a routing map, per-destination playbooks and monitoring with alerts. Output is a spec, an automation checklist and a follow-up plan.
Which arguments does the command take?
--segment, --threshold, --destinations and --alerts. --playbook is optional, and without it you get the routing map but no message sequences.
Source text
operationalize-pql-routing.md · Apache-2.0
--- name: operationalize-pql-routing description: Builds scoring, routing, and follow-up workflows for product-qualified leads. usage: /product-led-growth:operationalize-pql-routing --segment startup --threshold 80 --destinations crm,cs --alerts true --- # Command: operationalize-pql-routing ## Inputs - **segment** – cohort focus (startup, scaleup, enterprise, education, region). - **threshold** – minimum PQL/PQA score for routing. - **destinations** – systems/teams to notify (crm, cs, marketing, product-qualified team). - **playbook** – optional follow-up play (upsell, adoption, expansion, churn-save). - **alerts** – true/false to include Slack/email alerts for SLA breaches. ## Workflow 1. **Signal Review** – evaluate telemetry, entitlement, and intent fields for the segment. 2. **Scoring Model** – configure scoring weights, decay rules, and enrichment mapping. 3. **Routing Map** – define ownership, queue priority, and automation triggers. 4. **Playbook Assembly** – package messaging, assets, and SLAs for each destination. 5. **Monitoring Hooks** – establish dashboards + alerts for backlog, conversion, and SLA adherence. ## Outputs - PQL scoring + routing spec (JSON/CSV + narrative). - Automation checklist for CRM/CS/rev tools. - Follow-up playbook with sequences, assets, and owners. ## Agent/Skill Invocations - `pql-ops-lead` – owns scoring design + routing automation. - `product-adoption-strategist` – ensures messaging + enablement align to journey. - `pql-framework` skill – standardizes scoring methodology. - `usage-health-scorecard` skill – monitors conversion + health metrics. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents