The GTM Decision System is Databook's operating system for revenue execution. This article explains what it does, how the parts fit together, and where your teams use it. If you want to understand the intelligence underneath it, read Customer Context Graph.
What the GTM Decision System is
The GTM Decision System guides your entire go-to-market organization, from CRO to BDR, on how to grow revenue efficiently. It helps your teams:
Prioritize the accounts that matter, based on what is happening in your customer's business rather than on internal records alone
Build a point of view on an account that stands up in an executive conversation
Progress opportunities with guidance that arrives at the moment of the decision
Identify the risks that stop deals closing, early enough to act on them
A decision system is different from the tools that sit alongside it. Revenue intelligence tells you what already happened. Sales enablement delivers content. Agent platforms automate individual tasks. A decision system determines what should happen next, and makes sure it happens consistently across your organization.
What changes for your organization
Most AI in the revenue stack helps one person do one task faster. Individual gains like that do not add up to an organization that performs better: three thousand sellers with a faster assistant is not a faster sales organization. The Decision System is built for the level above the individual, which changes four things:
Consistency The same reasoning is applied the same way for every seller, every account, every time, instead of varying with individual skill or effort.
Proactivity Risks and opportunities surface on their own. Nobody has to think to ask the question first.
Learning The system improves from what happens across your whole organization, not from one user's history.
Flexible deployment The same system reaches your teams in the surfaces they already work in, so adoption does not depend on people coming to a new application.
Two shifts sit behind those benefits. Context and reasoning move from a single user's session to a shared foundation your whole organization works from. And the system moves from surfacing an insight and stopping to taking action within the guardrails you set.
How it fits together
The Decision System has four layers. The Customer Context Graph is the foundation, and everything above it is modular, so you can start with the workflows that address your most urgent problem and add more later on the same foundation.
Layer | What it does |
Intelligence foundation | Establishes what is true about your customer and where you stand with them |
Agentic network | Turns that context into judgment and guided action |
Deployment | Carries intelligence and guidance into the surfaces your teams already use |
Governance | Lets your leaders govern, measure and evolve what is running |
Intelligence foundation
The Customer Context Graph: a continuously updated model of accounts, buyers, industries and priorities, organized around the account rather than the individual deal. It combines licensed and analyst-curated third-party intelligence with your own first-party context, so context is established before execution begins and holds across every handoff.
See Customer Context Graph for what goes into it.
Agentic network
This is where context becomes guided action:
Coaches are interactive and user-facing. Base coaches cover common workflows out of the box, and custom coaches can be configured to your own motion, assets and methodology.
Agents run in the background with no user input, continuously enriching context, detecting change and surfacing risk.
Assets are generated outputs in your own branding, as PowerPoint, Google Slides or Word, which you can refine conversationally.
Inline guidance is produced inside a workflow when a downloadable asset is not what you need.
Your own team extends this layer in GTM AI Studio, using Coach Studio, Prompt Studio and SmartTemplate Studio. These are open to every user rather than administrators only, so the people who own the number can configure and evolve the workflows they depend on.
Deployment
You choose the surface. The intelligence and the reasoning stay the same wherever it appears.
Your CRM, Slack and Teams, for in-workflow guidance and proactive notifications
Your own GTM Command Center, for deep work
API, in batch, conversational, insights and deep reasoning modes, for your own applications, embedded intelligence or a front end you build yourself
MCP, for AI-native surfaces where a language model is the interface, with no custom build required
Reasoning inside your own agent platform, using Databook as the domain-specific inference layer
The goal is to let your teams work in fewer places, by bringing the system to the surfaces they have already consolidated on.
Governance
The GTM Control Center is where your leaders govern and measure what is running.
Analytics Dashboards covering high-urgency accounts, whitespace analysis, usage and execution patterns, adoption trends, conversation analytics and revenue attribution
Administration Membership, roles and access, team publishing and integration controls
Branding and personalization A custom domain, deep links into your CRM and internal tools, branded avatar and naming, and a configurable platform voice
Leaders use it to see where sellers are executing well and where they are struggling, spot pipeline opportunity and whitespace across accounts, identify where enablement or process change is needed, and measure whether the change in behavior is improving outcomes against an agreed baseline.
Example use cases
The workflows below are examples of what the Decision System supports, grouped by the team that usually sponsors them. Which workflows are available to your organization, and how each one is configured to your motion, is set up with your account team. Some are designed collaboratively with you rather than switched on as-is.
Marketing
Dynamic account prioritization Rank your target list using an ICP gate plus intent scoring
Demand generation Contact strategy and outbound sequences built from scored accounts
Lead scoring Inbound lead qualification, briefing and routing
Account based marketing Microsites and landing pages per target account
Executive briefings Account briefings ready for an executive conversation
Campaigns Campaign build-out and orchestration
Sales operations
Sales forecasting Deal-level forecast intelligence and roll-ups
Account planning Signal sweeps, account dossiers and plans
Territory planning Territory design and coverage modelling
Sales plays Plays triggered off account and deal signals
Sales enablement Rep enablement and coaching workflows
Sales content and playbooks Content and playbook generation
Value engineering
Deal support and value enablement In-deal intelligence, risks and next steps
Post-sales value realization Consumption pre-analysis and value realization strategy
Executive presentation and storytelling Executive narratives and presentation build
Discovery and diagnosis Structured discovery and diagnostic framing
Business case and ROI modeling Business cases and ROI models
Customer enablement
Post-sale value realization Adoption pathways and proof of value after the sale
Expansions and renewals Renewal and expansion pathways from your consumption strategy
Consumption analysis and strategy Consumption pacing, objectives and milestone plans
Whitespace Priority whitespace use cases by GTM team
Quarterly business reviews QBR preparation and outputs
Getting started
Every workflow runs on the same foundation, so you do not need to have everything in place before you start. Speak to your account team about which workflows fit your priorities, which surfaces you want them delivered into, and what first-party context you can connect.