Issue 07 · Research basis: 2024 contextual retrieval and connected-tool research. Historical sources are interpreted for current GTM decisions.
The decision
Before giving AI another connector, give it the company's decisions. Tool access can retrieve a CRM record. It cannot settle what your team means by qualified pipeline or which claims you have permission to publish.
A company GTM brain should make those decisions available to every lane: paid media, outbound, engineering and AI search. Each lane can have its own plugin while sharing the same approved context.
What the 2024 work explains
Anthropic's September 2024 contextual-retrieval work addresses information lost when document fragments lack surrounding context. Its November 2024 Model Context Protocol announcement describes a standard for connecting AI systems to data and tools.
Our GTM interpretation: access and context solve different parts of the problem. A connection makes information available. Company definitions and decisions make it interpretable for the job at hand. The vendor research does not establish a revenue result for a GTM brain.
Same record, different instruction
Consider this synthetic CRM example: an opportunity exists, an estimated amount is present and a discovery call is booked. One process could call it pipeline because a deal record exists. Another could wait until sales confirms fit and the buying problem.
Both can read the same fields correctly and produce different reports. The missing input is the acceptance rule, not another retrieval tool.
| Brain input | Decision it enables |
|---|---|
| Qualified-pipeline definition | Which CRM events count |
| ICP and exclusions | Which accounts enter a campaign |
| Approved proof and publication permissions | Which claims can appear in copy |
| Owners and escalation rules | Who resolves ambiguity |
| Dated review history | Which decision is current and why |
Separate approved company facts from proposed changes and reference material. A competitor's wording is research, not your positioning. A synthetic example is not a client result.
What to check this fortnight
Choose one recurring output: a pipeline review, outbound cohort or page brief. Ask the system to identify the definition it used, the source behind its claims, the unresolved input and the owner who should decide.
Then change one approved definition in a safe test context and inspect whether the output changes appropriately. If different lanes silently use different versions, repair that shared context before increasing automation.
Keep company brains separate. Reusable skills can describe a method, but one company's commercial data, proof permissions and decisions should not become another company's context.
One workflow
How a GTM brain runs your company's GTM explains the shared system and lane plugins. Start with the company's current tools and decisions. Add a connector when the workflow needs access it does not already have.
Use this next
Write the acceptance rule, exclusion rule, approved evidence and decision owner for one task. Have the team confirm those inputs before using the output in a live campaign or commercial discussion.
The question before adding another tool: which decision will this connection make better, and where is that decision defined?
Publication and source record
Published on GTMhub: . Last reviewed: .