← 返回
未分类 中文

GTM Inbound Strategy

Design inbound GTM systems — lead routing logic, PLG activation flows, nurture tracks, and ICP-based triage. Use when leads aren't converting, building or op...
设计Inbound GTM系统——包括线索路由逻辑、PLG激活流程、培育流程和基于ICP的分诊。适用于线索未转化时,构建或优化...
davidslavich davidslavich 来源
未分类 clawhub v1.0.0 1 版本 100000 Key: 无需
★ 0
Stars
📥 426
下载
💾 1
安装
1
版本
#latest

概述

GTM Inbound Strategy

Design or optimize the inbound GTM system from lead capture through conversion.

Output is a routing model + activation/nurture sequences with explicit SLAs.

Steps

  1. Classify lead sources — assign signal strength and routing priority:
    • Demo request → 🔴 High: route to AE (SLA: 4 hours)
    • Trial/PLG signup → 🟡 Medium: PLG activation flow
    • Gated content / event → 🟡 Medium: nurture + intent watch
    • Newsletter / organic → ⚪ Low: long-play nurture
  1. ICP triage — FIRE quick-score every inbound lead within 24 hours

(see gtm-qualification-scoring for the full rubric):

  • F ≥ 7 AND I ≥ 7 → sales-qualified, route to AE now
  • F ≥ 6, I < 6 → marketing-qualified, enter nurture + intent watch
  • F < 6 → self-serve or long-play nurture — no SDR time
  1. PLG activation flow (if applicable) — define the "aha moment" first: the

single action that predicts retention. Build the sequence to reach it in ≤ 3 steps.

Default cadence: Day 0 confirm → Day 1 first-value prompt → Day 3 usage check →

Day 7 case study → Day 14 sales touch (if ICP match) → Day 21 re-engagement.

  1. Nurture tracks — assign to one of three tracks:
    • Track A (High-Fit, Low-Intent): educate, 1x/week for 6 weeks
    • Track B (High-Intent, Unknown-Fit): qualify fast, 2x/week for 2 weeks
    • Track C (Low-Fit, Low-Intent): brand affinity, 2x/month
  1. Define SLAs — every routing rule needs a time window and an owner.

"Route to sales" without an SLA is not a system.

Output

# Inbound GTM Motion: [Product / Segment] | [Date]

Lead Source Map: [Source · Signal strength · Routing priority]
FIRE Triage Thresholds: [Specific F/I thresholds for this ICP]

Routing Logic:
IF [source + FIRE condition] → [action] (SLA: [time], Owner: [role])
[repeat for each routing rule]

PLG Activation Flow: [Day-by-day: channel · content · goal · aha moment]
Nurture Tracks: [Track A / B / C — cadence, content type, goal]
Handoff SLAs: [Lead tier → response time → who owns it]

版本历史

共 1 个版本

  • v1.0.0 当前
    2026-03-31 16:23 安全 安全

安全检测

腾讯云安全 (Keen)

安全,无风险
查看报告

腾讯云安全 (Sanbu)

安全,无风险
查看报告

🔗 相关推荐

business-ops

Trello

steipete
使用 Trello REST API 管理看板、列表和卡片
★ 162 📥 41,574
business-ops

Calendar

ndcccccc
日历管理与日程安排。创建事件、管理会议,并实现多日历平台同步。
★ 7 📥 23,514
business-ops

Stripe

byungkyu
Stripe API 集成,支持托管 OAuth,实现对客户、订阅、发票、产品、价格和支付的可写金融集成。
★ 27 📥 26,304