Define Handoff

Establishes marketing-to-sales routing design, SLAs, and enablement requirements.

Published by @gtmagents·from gtmagents/gtm-agents·0 agent reads / 30d·0 saves·

Command: define-handoff

Inputs

  • segment – target segment/persona (enterprise, mid-market, SMB, partner).
  • goal – business target (pipeline, expansion, product activation, ABM campaign).
  • response-sla – desired first-touch SLA (e.g., 2h, 1d).
  • capacity – optional SDR/AE capacity notes to shape routing rules.
  • dependencies – optional systems/content that must be ready (scoring, sequences, talk tracks).

GTM Agents Pattern & Plan Checklist

Derived from GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325.

  • Pattern selection: Handoff design usually follows a pipeline (intake → routing → SLA modeling → enablement → approvals). If routing + enablement prep can run in parallel, log a diamond segment with merge gate.
  • Plan schema: Save .claude/plans/plan-<timestamp>.json with objective, tasks, dependencies (data, tooling), context passing (scoring configs), error handling, and success metrics (SLA %, acceptance rate, conversion lift).
  • Tool hooks: Reference docs/gtm-essentials.md stack—Serena for CRM/MAP script diffs, Context7 for platform docs, Sequential Thinking for review cadence, Playwright for QA of lead forms/sequences.
  • Guardrails: Default retry limit = 2 for automation/build failures; escalation ladder = RevOps Director → Sales Manager → CRO.
  • Review: Use docs/usage-guide.md#orchestration-best-practices-puerto-parity checklist before execution to confirm agents, dependencies, deliverables.

Workflow

  1. Brief Intake – confirm funnel stage definitions, qualification criteria, scoring thresholds.
  2. Routing Blueprint – map lead ownership logic (account owner, round-robin, pod based) and required enrichment data.
  3. SLA Modeling – calculate achievable response times vs capacity, flag risks, define escalation ladder.
  4. Enablement Requirements – list assets, talk tracks, sequences, and dashboards each pod needs.
  5. Approval Packet – consolidate documentation for RevOps + sales leadership sign-off.

Outputs

  • Handoff design doc (routing matrix, SLA tables, escalation tree).
  • Data + tooling checklist (fields, integrations, automation flows) with owners.
  • Enablement kit request list with due dates.
  • Plan JSON entry stored/updated in .claude/plans for audit trail.

Agent/Skill Invocations

  • revops-director – leads routing/SLA design.
  • routing-logic skill – enforces qualification + assignment best practices.
  • enablement-kit skill – ensures supporting assets are ready.

GTM Agents Safeguards

  • Fallback agents: document substitutes (e.g., Sales Manager covering RevOps Director) when specialists unavailable.
  • Escalation triggers: if SLA breaches or routing failures exceed guardrails twice in 48h, trigger escalation to Sales + Marketing leadership per GTM Agents rip-cord.
  • Plan maintenance: update plan JSON whenever segments, routing logic, or enablement requirements change so audit trail mirrors GTM Agents standards.

More on the bench

SKILL0

Launch

When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas.

marketing-growth-copy+2
9
SKILL0

Marketing Ideas

When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' or 'ideas to grow.' This skill provides 139 proven marketing approaches organized by category.

marketing-growth-copy+2
7
SKILL0

Launch Strategy

When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'GTM plan,' 'launch checklist,' or 'launch momentum.' This skill covers phased launches, channel strategy, and ongoing launch momentum.

marketing-growth-copy+2
2