The PQA Signal Matrix

The PQA Signal Matrix

The PQA Signal Matrix（PQA 信号矩阵）

概述 / Overview

一种定义产品合格账户（PQA）的数据驱动方法。与侧重单点个人的 PQL 不同，PQA 聚焦于表现出特定行为特征的组织，这些行为与该客户开启企业级业务洽谈的成熟度高度相关。

来源 / Source

• 嘉宾: Elena Verna
• 职位: Growth Advisor & Former Interim Head of Growth at Amplitude
• 公司: Reforge / Amplitude / Miro / MongoDB

核心原则 / Core Principles

• Volume Thresholds: Establish a baseline of usage volume (e.g., Amplitude: number of events; Miro: number of boards).
• Velocity Spikes: Look for sudden changes in rate (e.g., adding 15 users in one day vs. 1 user a day). Velocity is often the best trigger for timing.
• Feature Breadth/Network Effects: The presence of 7+ users (or similar 'herd' metric) indicates internal viral spread and stickiness.
• Behavioral Tells: Track 'Admin' signals, such as an admin transfer, visiting the Terms of Service page, or hitting SSO walls.

适用场景 / When to Use

当你搭建首个 PLS 机制，或当销售团队抱怨“产品线索全是垃圾”时。

常见错误 / Common Mistakes

将 PQA（账户时机成熟）与 PQL（具体用户即买家）混淆。通常 PQA 信号已经存在，但你需要市场团队去定位真正的买单人（MQL），并将其与当前的产品使用行为挂钩。

实战案例 / Real-World Example

在 Miro，账户内发生的“管理员变更”是一个关键的行为信号。这表明客户正在进行评估或整合，正是销售团队介入的最佳时机。

金句 / Quote

"If you just stick your sales against that account, you're going to have a very terrible situation... 'Why is sales talking to me? I have no decision-making power.'"