Subscriber count is an easy vanity metric. Product pull is not.
If every subscriber gets equal attention, your team spends time on noise and ignores high-intent demand.
Operator Insight
The core argument: qualification should be a behavioral scoring system calibrated weekly against downstream outcomes.
Qualification Score (0-100)
Qualification Score = R + U + I + E
Rrole fit (0-30)Uurgency signals (0-25)Iintent depth (0-25)Eengagement reliability (0-20)
Default Signal Weights
| Signal | Points | Why it matters | Source |
|---|---|---|---|
| ICP role selected (founder/operator/dev lead) | +15 | Role predicts implementation authority | Form data |
| Work email verified | +10 | Reduces low-intent signups | Verification event |
| Company context submitted | +5 | Indicates evaluation seriousness | Onboarding form |
| Click on implementation asset | +12 | Better intent than generic blog click | UTM + events |
| Return visit in 7 days | +8 | Ongoing buying/research cycle | Analytics |
| Reply with concrete use case | +10 | Strong near-term intent | Inbox event |
| Deep session (>2 min, multi-page) | +5 | Better than bounce engagement | Analytics |
| Disposable/personal alias pattern | -10 | Often correlates with low business intent | Email heuristics |
| No activity after 7 days | -8 | Intent decay signal | Lifecycle job |
Concrete example: a contact with role fit, verified work email, asset click, and use-case reply often scores 55+, which is where high-touch follow-up should begin.
Qualification Bands and Actions
| Band | Meaning | Action in 24h | Owner |
|---|---|---|---|
75-100 | High-intent ICP | Send implementation sequence + invite short diagnostic call | Growth lead |
55-74 | Promising, incomplete | Trigger clarification workflow | Lifecycle owner |
35-54 | Low confidence | Keep in nurture, no manual outreach | Marketing ops |
0-34 | Noise | Suppress from high-touch pipeline | Marketing ops |
7-Day Calibration Playbook
- Validate event instrumentation quality.
- Manually audit top 20 scores.
- Compare score bands to actual downstream actions.
- Adjust one weight only.
- Publish rubric update and lock for one week.
Tradeoffs and Limits
- Role self-report can be inflated; require behavioral corroboration.
- Channel shifts can distort score reliability; audit by source weekly.
- Overweighting clicks can reward curiosity instead of buying intent.
- Scoring systems fail if downstream conversion events are not instrumented.
Source Citations
- HubSpot: Lead Scoring Models
- Google Analytics 4 Event Measurement
- Mailchimp: Email Marketing Benchmarks
- NIST AI RMF Playbook
CTA
Use the scoring model directly: Get the Subscriber Qualification Pack