The language behind the GTMcraft operating system.
GTMcraft uses a small set of terms deliberately. Understanding them makes it easier to move from GTM problem, to diagnosis, to execution, to system.
GTMcraft
The operating systemThe GTM operating system for European B2B SaaS founders and GTM leaders scaling from €1M to €25M ARR. GTMcraft combines current GTM intelligence, execution-ready plays, AI skills and operator judgment to help teams find what to fix next and turn it into repeatable execution.
Constraint
The bottleneckThe specific bottleneck currently limiting a GTM outcome. A constraint is narrower than a general business problem.
Diagnostic
The methodA structured method for finding the constraint behind an outcome. Diagnostics connect business results to the metrics, capabilities and behaviors underneath them.
GTM Play
Run-it assetA repeatable operating system for solving a specific GTM problem. A Play goes beyond advice by defining how the work should actually be executed, measured and maintained.
Playbook
The frameworkThe deeper operating framework around a GTM problem or capability. A playbook may contain multiple Plays, templates, diagnostics, workbooks, metrics and AI workflows.
Human Skill
Human capabilityA GTM capability where human competence materially affects the outcome. Examples include discovery, negotiation, coaching, positioning and executive selling.
AI Skill
AI capabilityA reusable instruction set that enables an AI system to perform a defined GTM job consistently. An AI Skill should contain enough context, standards and guardrails to produce useful work repeatedly, not just once.
Agent
AI systemAn AI system that can execute multiple steps toward a defined GTM outcome using context, instructions and tools. Agents are most useful after the underlying process has been made explicit.
Routine
AI workflowA repeatable AI workflow that runs on a schedule or trigger. If a GTM task happens every Monday, after every call, when a deal changes stage or when an account shows a signal, it is a candidate for a Routine.
Signal
InformationA piece of information that may change a GTM decision or action. Signals can come from buyers, accounts, customers, markets, competitors, operators or internal performance data.
GTM Signal
Raw intelligenceA relevant observation, tactic, pattern, benchmark or operating lesson collected from the GTM ecosystem. GTMcraft uses GTM signals as raw intelligence, not as recommendations by default.
Signal Engine
The intelligence systemThe GTMcraft intelligence system that collects, structures and connects GTM signals from leading operators and sources. Its purpose is not to create more content. Its purpose is to keep GTMcraft's operating knowledge current.
Operator Judgment
The filterThe contextual reasoning required to decide whether a GTM pattern actually applies to your company. Signal without judgment becomes noise. Judgment turns signal into a decision.
Metric
The measureA measurable indicator used to understand whether a GTM outcome, capability or behavior is improving. Metrics connect Plays and Skills back to business performance.
Operating Cadence
The rhythmThe recurring rhythm that keeps a GTM system running. Examples include weekly deal reviews, monthly channel reviews, coaching sessions and quarterly market reviews.
GTM Operating System
The systemThe connected set of processes, standards, metrics, plays, cadences, human skills and AI workflows that determine how a company executes go-to-market. The objective is repeatability. Not documentation for its own sake.
Founder-Operator
PersonaA founder who still materially owns GTM decisions, selling or revenue execution. The transition challenge is turning founder knowledge into systems the company can run without constant founder intervention.
GTM Operator
PersonaA leader responsible for turning GTM strategy into revenue execution. Examples include CROs, VPs of Sales, Heads of Revenue, Country Managers, RevOps leaders and senior commercial operators.
Human × AI
The modelThe GTMcraft operating model where humans own judgment, systems provide structure, and AI executes repeatable work.
- A signal should become judgment.
- Judgment should become a decision.
- A recurring decision should become a Play.
- A repeatable Play should become a system.
- Repeatable work inside that system should increasingly be executed by AI.