← Back to Skills Marketplace
davidslavich

GTM Inbound Strategy

by davidslavich · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
176
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install gtm-inbound-strategy
Description
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...
README (SKILL.md)

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
  2. 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 \x3C 6 → marketing-qualified, enter nurture + intent watch
    • F \x3C 6 → self-serve or long-play nurture — no SDR time
  3. 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.

  4. 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
  5. 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]
Usage Guidance
This skill is low-risk because it is instruction-only and asks for no credentials. Before using, avoid pasting sensitive or PII-heavy lead data into the tool/output; treat suggestions as advisory templates to be adapted to your systems; verify the FIRE rubric and any thresholds against your company data; and note the skill has limited provenance (no homepage/source code) — consider testing recommendations on non-production data and consulting your legal/compliance teams before operationalizing SLAs or automated routing rules.
Capability Analysis
Type: OpenClaw Skill Name: gtm-inbound-strategy Version: 1.0.0 The skill bundle contains only documentation and strategic instructions for designing Go-To-Market (GTM) inbound lead routing and marketing workflows. It includes no executable code, network requests, or malicious prompt injections, and its content is entirely consistent with its stated purpose.
Capability Assessment
Purpose & Capability
Name/description (inbound GTM, lead routing, PLG activation, nurture tracks) align with the SKILL.md steps and expected outputs. The instructions produce routing models, SLAs, and activation/nurture sequences — coherent with the stated purpose. Note: the skill has no published homepage/source beyond a metadata website URL, so provenance is limited but not inconsistent with purpose.
Instruction Scope
SKILL.md contains concrete, scoped steps (classify lead sources, FIRE triage, PLG cadence, nurture tracks, SLAs) and a clear output template. It does not instruct reading local files, accessing env vars, calling external endpoints, or exfiltrating data. A reference to an external rubric ('gtm-qualification-scoring') is present but appears to be a logical cross-reference for scoring, not a runtime dependency.
Install Mechanism
No install spec and no code files — lowest risk. Nothing is written to disk or fetched at install time.
Credentials
No required environment variables, credentials, or config paths are declared. The skill does not request unrelated secrets or system access.
Persistence & Privilege
always is false and model invocation is allowed (platform default). The skill requests no special persistent privileges or ability to modify other skills or system settings.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install gtm-inbound-strategy
  3. After installation, invoke the skill by name or use /gtm-inbound-strategy
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
iCustomer GTM Skill Packs v1.0.0
Metadata
Slug gtm-inbound-strategy
Version 1.0.0
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is 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... It is an AI Agent Skill for Claude Code / OpenClaw, with 176 downloads so far.

How do I install GTM Inbound Strategy?

Run "/install gtm-inbound-strategy" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is GTM Inbound Strategy free?

Yes, GTM Inbound Strategy is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does GTM Inbound Strategy support?

GTM Inbound Strategy is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created GTM Inbound Strategy?

It is built and maintained by davidslavich (@davidslavich); the current version is v1.0.0.

💬 Comments