# APAC PQL — stakeholder ASKs

Decisions we need from APAC GTM/leadership before the model goes operational. Each ships with a
**recommended default** so the conversation is "confirm/adjust", not "start blank".

## 1. ICP / Account Fit definition
**Recommend:** ICP = corporate/AI-core & AI-related domains. Suppress free-email + no-behavior.
**But APAC nuance (data-backed):** free-email is common among real APAC devs — strict suppression
would discard **~1,046 import-driven accounts**. We route free-email + real behavior to a
**verify-identity** queue (P2), not the bin. **Confirm:** the APAC AI-category rubric, and that
verify-identity (not hard-suppress) is the right call for personal-domain builders.

## 2. Target countries / markets
**Recommend:** India + APAC-Others this round; **CN and JP excluded** (Japan staged later, numbers
captured). India broken out for volume. **Confirm:** market in/out list and whether Japan joins next round.

## 3. Deployment form — bot vs. platform
**Recommend: bot.** Feishu/Slack daily + weekly P0/P1 digest → CRM/HubSpot tasks. Fastest to value,
mirrors EMEA's working motion; a dashboard tab can follow. **Confirm:** channel (Feishu vs. Slack) and CRM target.

## 4. Follow-up resources + per-tier SLA
**Recommend SLA:** **P0 same-day · P1 ≤48h · P2 automated nurture.** **Need from you:** owner
headcount per market — capacity caps queue size (e.g. windows like spending-limit-30d exist because
EMEA runs on two operators). With today's data the live P1 queue is **~459**; P0 is **0** until
enrichment lands.

## 5. Priority use cases / signal types
**Recommend ranking:** **data import (migration) > sustained QPS / first DDL > card / spending-limit
> multi-cluster.** **Confirm:** which workloads matter most for APAC (AI/vector, HTAP, migration off
MySQL) so we weight and message accordingly.

## 6. Success metrics / expected outcomes
**Recommend:** PQL→SQL conversion by market/signal/channel · P0 handoff acceptance rate ·
time-to-first-touch vs. SLA · import/card→opportunity rate. Baseline from the journey reference.
**Confirm:** the target numbers (if ready) so we can set thresholds against them.

---

## Asks that block the model (engineering/data — not GTM decisions, but need sponsorship)
These determine how much of the funnel is even visible. From [`apac-data-inventory.md`](apac-data-inventory.md):

| Ask | Unlocks | Owner |
|-----|---------|-------|
| **Fit enrichment** (domain/AI-category) | **P0 entirely** (latent 180+ today) | data / platform |
| **O11Y ingestion** (QPS, first DDL) | strongest workload signals | data + O11Y team |
| **Spending-limit events** (30d window) | commercial signal + P1 floor | data |
| **`track_step` write-back** | suppression + PQL→SQL measurement | GTM / CRM |