Design Lifecycle Journey

Produces a customer lifecycle journey map with stages, triggers, plays, and owners.

Published by @gtmagents·0 agent reads / 30d·0 saves·Updated June 14, 2026

Command: design-lifecycle-journey

Inputs

segment – SMB, mid-market, enterprise, strategic, etc.
product – product line or package the journey targets.
objectives – adoption, expansion, advocacy, retention goals.
signals – optional health metrics or telemetry to align on.
tooling – optional stack info (Gainsight, HubSpot, Pendo, etc.).

Workflow

Insight Alignment – analyze current health, usage, NPS, and pipeline targets.
Stage Definition – outline onboarding, adoption, value realization, expansion, advocacy.
Trigger & Play Mapping – define triggers (usage dips, milestone hits) with recommended plays.
Owner & Channel Assignment – map CS, product, marketing, automation responsibilities.
Measurement Plan – set KPIs per stage and dashboards/alerts for monitoring.

Outputs

Journey map table (stage, trigger, play, owner, channel, KPI).
Trigger-to-play matrix for automation/CS tooling.
Measurement checklist with dashboard queries and alert rules.

Agent/Skill Invocations

lifecycle-strategist – orchestrates journey design.
customer-insights skill – supplies telemetry + signal definitions.
expansion-plays skill – recommends stage-specific offers.

More on the bench

Vendor Management

Evaluate, compare, and manage vendor relationships. Trigger with "evaluate this vendor", "compare vendors", "vendor review", "should we renew", "RFP", or when the user is making procurement or vendor decisions.

sales-gtm-revops+1

Qbr Builder

Create Quarterly Business Reviews with account health scores, usage analytics, ROI analysis, expansion opportunities, and risk mitigation

customer-success+1

Escalation

Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.

customer-success+2

Sharebench · Public bench

Connect via MCP.

Add the public bench to any AI tool. Your agents read every artifact you see — no signup needed.

1Pick your tool

# Add the public bench as an MCP server
claude mcp add --transport http sharebench-public https://mcp-public.sharebench.ai

# Settings → MCP → Add new MCP server
{
  "mcpServers": {
    "sharebench-public": {
      "url": "https://mcp-public.sharebench.ai"
    }
  }
}

# Custom GPT or Developer Mode
# Add a remote MCP connector with this URL:
https://mcp-public.sharebench.ai

# Append to ~/.codex/config.toml
[mcp_servers.sharebench_public]
url = "https://mcp-public.sharebench.ai"

2Ask your agent for an artifact

Once connected, just ask in plain language — your agent searches the bench and pulls in what it needs.“Pull the brand voice from sharebench and rewrite this draft.”