GTM Engineering
Source-grounded pack with GTM Experiment Runtime Controller, GTM Object Model Designer, and GTM Observability Audit, plus 2 more.
Get this packGrounded in the complete GTM Engineering series.
Open the pack, choose a workflow, and follow its setup and input instructions. You can also open each workflow below.
10 source essays · 5 usable skills · reviewed Jul 2026
Use this pack when
Choose this pack when the work touches GTM Engineering and you need a bounded workflow with explicit inputs, a defined output, and human review gates.
Choose the job in front of you.
5 source-grounded skills. Load one workflow at a time.
GTM Experiment Runtime Controller
Use this workflow when a GTM workflow, automation, or AI agent changes targeting, scoring, routing, tasks, records, outreach, pipeline, renewal, or expansion and needs durable experiment memory, permissions, gates, evals, logs, feedback, and stop controls.
Output specification
Return a GTM runtime control spec with:
GTM Object Model Designer
Use this workflow when a revenue workflow depends on ambiguous accounts, people, opportunities, workspaces, customers, renewals, tasks, ownership, lifecycle states, or system boundaries and needs an executable GTM object model.
Output specification
Return a GTM object model spec with:
GTM Observability Audit
Use this workflow when a revenue workflow fails through delay, bad data, wrong routing, stale signals, ignored tasks, lost handoffs, rejected agent outputs, or hidden exceptions and the team needs inspectable system health plus a sequenced repair backlog.
Output specification
Return a GTM observability audit with:
Routing and CRM Production Designer
Use this workflow when account, lead, customer, partner, renewal, expansion, or agent-generated work routes unpredictably, or when the CRM causes side work and poor data because its operator surface does not match the GTM motion.
Output specification
Return a routing and CRM production spec with:
Signal and Enrichment Contract Registry
Use this workflow when GTM signals or enriched fields drive alerts, scoring, routing, suppression, personalization, renewal, or prioritization without clear meaning, provenance, freshness, confidence, overwrite, ownership, and outcome feedback.
Output specification
Return a signal and enrichment registry with:
Keep consequential decisions explicit.
These workflows structure analysis and artifacts; they do not authorize autonomous external, personnel, financial, legal, security, or other high-impact action.