Example A — Large individual tenant P0
Signals: individual, 100 clusters, QPS unavailable, valid card.
Activity 33 + Fit 0 + Urgency 0 = Total 33
Why P0: cluster count is at least 50. The direct P0 rule applies even though the score is only 33.
APAC Tenant Scoring and Priority Rules
A concise reference for how tenants are scored, prioritized, and routed.
Aligned with the production implementation as of 15 July 2026.
Score: 0–100, based on Activity, Fit, and Urgency.
Priority: P0, P1, or P2. Priority is rule-based, not a simple score range.
Evaluation order: check P0 rules first, then P1; otherwise assign P2.
Business overrides: a HubSpot Target Account is always final P0, but keeps its normally calculated score.
1. Score
Total Score = Activity (max 40) + Fit (max 30) + Urgency (max 30)
Activity — maximum 40 points
| Signal | Points |
|---|---|
| Average QPS ≥ 1 | +25 |
| 0.001 ≤ average QPS < 1 | +12 |
| At least 1 cluster | +10 |
| At least 3 clusters | +8 extra |
| At least 10 clusters | +5 extra |
| Has a valid credit card | +10 |
| QPS ≥ 1 and no valid credit card | +5 |
Cluster points are cumulative: 1+ cluster earns 10, 3+ earns 18, and 10+ earns 23. Add all applicable signals, then cap the result at 40.
Fit — maximum 30 points
| Entity type | Points |
|---|---|
| Core AI company | 30 |
| AI-related company | 20 |
| Non-AI company with a business email domain | 15 |
| AI-related institution | 15 |
| Non-AI institution | 8 |
| Non-AI company with a public email domain | 5 |
| Unknown or unmatched | 3 |
| Individual | 0 |
Fit selects one row only; the points are not cumulative.
Urgency — maximum 30 points
| Signal | Points |
|---|---|
| Created within 24 hours and is a core AI company | +20 |
| Created within 48 hours and is an AI-related company | +15 |
Plan is poc | +15 |
| Average QPS ≥ 50 | +15 |
| At least 3 clusters, no valid card, and a known organization | +12 |
A known organization is a recognized company or institution. Individual and unknown records do not qualify. The 24-hour and 48-hour checks use elapsed time, not a CST calendar day.
2. Priority
Priority is evaluated in this order:
- If any P0 rule matches, assign P0.
- Otherwise, if any P1 rule matches, assign P1.
- Otherwise, assign P2.
P0 — any one rule is sufficient
| P0 rule |
|---|
| Cluster count ≥ 50 |
| Average QPS ≥ 50 |
| Average QPS ≥ 10 and core AI company |
| Created within 24 hours and core AI company |
poc plan and core AI or AI-related company |
| Total score ≥ 75 and a known organization |
P1 — only when no P0 rule matches
| P1 rule |
|---|
| Total score ≥ 45 |
| Created within 48 hours and AI-related company |
| Created within 24 hours, non-AI company, and business email domain |
| Cluster count ≥ 10 and a known organization |
| At least 3 clusters, no valid card, and a known organization |
P2
No P0 or P1 rule matched.
Important: priority is not calculated from fixed score bands. A low-score tenant can be P0 because of a direct P0 rule, while a 67-point tenant can remain P1 if it does not match any P0 rule.
3. Target and Sales-owned Rules
- HubSpot Target Account: keep it in Active, calculate the score normally, and set the final priority to P0.
- Otherwise, APAC Sales-owned: if
sales_owner_emailmatches the configured APAC Sales list, store it in Sales-owned and calculate score and priority normally. - Otherwise: store it in Active and calculate score and priority normally.
Target takes precedence over Sales-owned. Daily and weekly summaries do not scan the Sales-owned table. A small fixed fast-path set goes directly to Sales-owned as P0 and skips normal scoring.
4. Real Production Examples
The following examples are from the production data snapshot on 15 July 2026. Tenant IDs, names, email addresses, and other identifying details are omitted.
Example B — AI company running a POC P0
Signals: AI-related company, poc plan, 0 clusters, QPS 0, no card.
Activity 0 + Fit 20 + Urgency 15 = Total 35
Why P0: an AI company on a POC plan directly qualifies for P0.
Example C — Active company without a card P1
Signals: non-AI company with business email, 4 clusters, average QPS 3.21, no card.
Activity 40 + Fit 15 + Urgency 12 = Total 67
Why P1: it exceeds 45 points and matches the 3-cluster/no-card rule, but it matches no P0 rule.
Example D — High QPS but unknown entity P2
Signals: unknown entity, 1 cluster, average QPS 39.62, no card.
Activity 40 + Fit 3 + Urgency 0 = Total 43
Why P2: QPS is below 50, the score is below 45, and no other P0 or P1 rule matches.
Example E — Low-signal Target Account Final P0
Signals: non-AI company with business email, 0 clusters, QPS 0, no card, verified HubSpot Target match.
Activity 0 + Fit 15 + Urgency 0 = Total 15
Why final P0: the calculated priority is P2, then the Target Account rule overrides the final priority to P0. The score remains 15.