The Spine

Seven horizontal layers. Causality flows downward. Constraints flow upward. This is not a marketing stack — it is a control architecture.

The Seven Layers

Revenue Thermostat

Not a flowchart. A control system. The set point is economics. The sensor is attribution. The actuator is governance. Feedback loops close the system.

The Control System Model

A thermostat has three components: a set point (desired temperature), a sensor (actual temperature), and an actuator (heating/cooling). Revenue works the same way.

SET POINT    // Economic constraints — what the business demands
  Business Plan → P&L → Protected Margin → Coverage Ratio

ACTUATOR     // Translation layer — how constraints become action
  Budgets → GTM Model → Allocations → ICP Spend → Stage Defs

SENSOR       // Operations — what actually happens
  Execution → Forecasting → Attribution → Optimization

FEEDBACK ↑   // The loop that makes it a thermostat
  Forecasting →↑ Budgets    // most critical correction
  Attribution →↑ Stage Defs  // informs governance, not just reporting
  CAC Breach  →↑ P&L Agent   // constraint enforcement

Why Feedback Flows Upward

In most GTM organizations, forecasting is a downstream output — something that happens after execution. That's observation, not governance.

In the governed model, forecasting is an input to budgets. The forecast corrects the budget. The budget corrects the allocation. The allocation corrects the execution. This is a closed loop.

Without upward feedback, budgets are set once and never corrected. Attribution becomes just reporting. The system is open-loop — a thermostat with no thermometer.

Agent Enforcement Rails

Five vertical agents span the three bands, monitoring thresholds and enforcing constraints at every intersection. They are not process steps — they are enforcement mechanisms.

When a CAC breach is detected at the execution layer, the P&L Agent doesn't just flag it — it constrains. The constraint flows upward through budget correction. The system self-regulates.

Agent Specifications

Five vertical enforcement agents span the spine layers. They are not process steps. They are governance rails — monitoring thresholds, enforcing constraints, and closing feedback loops.

Agent Design Principles

Agents don't execute. They govern. An agent never sends an email or creates a campaign. It monitors thresholds, enforces constraints, and triggers corrections.

Agents span layers. That's what makes them different from process automation. Each agent has jurisdiction across multiple spine layers, which is what enables closed-loop control.

Agents conflict. This is by design. The tension between a P&L Agent constraining spend and a Coverage Agent demanding more pipeline is the system working correctly. The Orchestration Agent resolves these tensions.

Sovereignty Map

Build vs buy vs integrate — for every layer of the stack. Not a vendor comparison. A decision framework for where you need sovereignty and where you can rent.

The Framework

Every component in the GTM stack sits on a spectrum from full sovereignty (you own and control it entirely) to full dependency (you rent it as a service). The map helps you decide where to be for each layer.

Layer-by-Layer Decisions

Economic Model: Always own. Your P&L constraints and governance logic are core IP.

ICP Governance: Own the logic, build on enrichment platforms for data.

Pipeline Architecture: Own the model (OpptyCon), configure execution tools.

Stage Definitions: Own in CRM, enforce via agents.

Agents: Build custom. These are the governance mechanism — don't rent your control plane.

Execution Systems: Configure SaaS. Signal surfaces, orchestration, CRM — these are commodity at the execution layer.

Attribution: Build on commercial platforms, own the feedback loop logic.

Motion Map

Seven acquisition modes. Every motion governed by the spine. Every channel traced to economics. No orphan campaigns.

The Seven Modes

Governance Connection

Every motion connects upward to the Pipeline Architecture layer (Layer 03) where budget allocation rules determine how much investment each mode receives. The Coverage Agent monitors whether the combined output of all seven modes meets the pipeline coverage target.

No mode operates independently. Each reports attribution data back through the feedback layer, which informs the next budget cycle. This is what makes it governed — not just planned.

Identity Graph

Contact and account resolution across the entire GTM surface area. Who is this person, which account do they belong to, and how do they connect to every touchpoint.

The Problem

Most B2B companies have the same person represented 3–5 times across their stack — once in the CRM, once in the MAP, once in the enrichment tool, once in the intent platform, once in the ad platform. Each representation is partial. None is authoritative.

Without a resolved identity graph, attribution is fiction, stage definitions are unreliable, and ICP governance is unenforceable. The identity graph is the prerequisite for every other governance function.

Resolution Layers

Contact Resolution: Deduplication, email normalization, role/title standardization, engagement history unification across all touchpoint systems.

Account Resolution: Company matching, hierarchy mapping, subsidiary-to-parent linkage, firmographic enrichment, account scoring consolidation.

Relationship Mapping: Buying committee identification, champion/detractor tracking, influence network mapping, historical engagement patterns per account.

Infrastructure

The technical stack that implements the governed architecture. Every tool has a role. Every role traces to a spine layer. No orphan subscriptions.

Stack Architecture by Domain

Signal Surface: Apollo, Seamless.AI, UserGems, BuiltWith, GA4 — tools that detect buying signals and feed the top of the funnel. Governed by signal quality thresholds.

Data & Enrichment: Clay, Snowflake, Clearbit — the enrichment pipeline that resolves identity and adds firmographic/technographic context. Governed by data parity requirements.

Orchestration: HubSpot, Customer.io, LeanData — routing, sequencing, and workflow engines. Governed by routing SLAs and handoff compliance.

System of Record: Salesforce, Gong — the authoritative data layer. Stage definitions enforced here. Agent enforcement happens at this layer.

Attribution & Finance: Dreamdata, Anaplan — the measurement and planning layer. Feedback loops originate here and flow upward into budget and stage governance.

Forecasting: Clari, Salesforce Forecasting — the sensor. Critical upward feedback: forecast data becomes budget input, not just board reporting.

OpptyCon — Revenue Physics Engine

Model your entire GTM as physics, not spreadsheets. Pipeline targets, cost structures, funnel conversion, coverage math, and phase-shifted demand across multi-year horizons.

What It Does

OpptyCon is the computational engine behind the governed revenue architecture. It takes your economic constraints (Layer 01) and models the entire cascade through pipeline generation, cost structure, funnel physics, and coverage math.

Unlike a spreadsheet, OpptyCon models time correctly. Q4 marketing spend generates Q1 pipeline. Sales hiring in March produces quota capacity in September. Attrition compounds. These phase shifts are invisible in a flat model.

Core Capabilities

Dual-Axis Cost Model: Separates fixed S&M (headcount, tools, infrastructure) from variable S&M (media spend, event costs, content production). Each behaves differently under scaling scenarios.

Coverage Ratio Enforcement: Pipeline targets are derived from ARR goals using coverage ratios. The engine enforces the math: if you need 3× coverage on a $10M target, you need $30M in qualified pipeline. If your conversion rates don't support that, the model shows it.

Phase-Shifted Funnel: Marketing programs in Q4 generate MQLs in Q1, which become SQLs in Q2, which close in Q3. The engine models this timing explicitly across 24+ month horizons so you can see the carry-over effects.

Attrition Modeling: Sales rep ramp time, quota decay, and turnover are modeled as continuous variables, not static assumptions. This shows the true cost of attrition on pipeline capacity.

Monthly Weight Distributions: Demand isn't flat. The engine allows custom monthly weighting for seasonal patterns, budget flush periods, and renewal timing.

How It Connects to the Spine

OpptyCon operationalizes Layer 01 (Economic Model) and Layer 03 (Pipeline Architecture). The outputs feed directly into budget allocation decisions and coverage ratio monitoring. When the Coverage Agent detects a gap, OpptyCon models the correction scenarios.

Lexicon

Terminology used throughout the governed revenue architecture. Precise language prevents ambiguity. Ambiguity prevents governance.

Core Terms

Provenance

Data lineage and decision audit trail. Every number in the system traces back to its source. Every governance decision traces to a constraint. Trust requires traceability.

Why Provenance Matters

In most GTM orgs, when a board member asks "why did we spend $400K on paid social last quarter?" the answer is a chain of Slack messages, half-remembered meeting decisions, and a spreadsheet someone built in 2023.

In the governed model, the answer is a provenance chain: $400K paid social ← Budget allocation rule ← Pipeline coverage gap ← Coverage Agent threshold ← Economic model constraint ← Board-approved business plan.

Every dollar traces back to a constraint. Every constraint traces back to economics. That's provenance.

Data Lineage

Every metric in the system carries metadata about its source, transformation chain, freshness, and confidence level. When the Coverage Agent reports a pipeline gap, the provenance layer shows exactly which source data fed that calculation and when it was last updated.

Library

The complete governed revenue architecture — every screen, tool, framework, and reference. Open by design. The competitive advantage is not the blueprint. It is the engineering to build and govern it.

Architecture Screens

Nine architecture screens define the governed revenue system. Each screen is a standalone reference — a layer of the control plane you can study, share, and build from.

Tools

Interactive engines that operationalize the architecture. Model scenarios, simulate constraints, and test governance responses before committing resources.

Frameworks

Repeatable decision frameworks extracted from the architecture. Each framework is a structured approach to a specific GTM governance problem.

Reference

Supporting materials, definitions, and background context for the governed revenue architecture.