Foresight Creation
Detect and structure emerging change, weak signals, regulation, technology and market developments.
Output: validated foresight / signalSales Motion / Cognitive Model Architecture
An architecture for controlling how understanding progresses across the Sales Motion — from foresight and company evidence to buying insight, customer narrative and formal response — through modular, evidence-gated pipelines.
Cognitive Model: defines what must be understood next, using what evidence, and under what reasoning boundaries.
Evidence-Gated Pipelines: govern how each cognitive step is executed, validated and converted into an approved artifact.
Execution Components: models, agents, APIs, databases, search and humans perform the work inside the architecture — they do not define it.
00 / Why This Matters
The point is not better orchestration.
The point is better business outcomes.
Sales Motion is designed to move the organisation upstream: from reacting to already-defined demand toward identifying, validating and shaping evidence-supported customer needs earlier — while improving the speed and quality of the response once demand becomes explicit.
The architecture should be judged through measurable operating and business outcomes — not by how sophisticated the orchestration looks.
01 / Opening Thesis
The distinctive idea of Sales Motion is not the existence of modules, databases, pipelines or even agents. Those are implementation components. The architecture is really about controlling how cognition progresses from one state of understanding to the next.
Starts from agents, models, tools, APIs and orchestration. The central question becomes: who acts next?
Starts from the required progression of understanding. The central question becomes: what must become known next, from what evidence, and under what conditions may the system proceed?
02 / Core Architectural Principle
The architecture should first define the sequence of cognitive states, evidence requirements, reasoning boundaries, validation gates and artifact contracts. Only then should it decide which model, agent, API, deterministic service, database query or human performs each operation.
03 / System Flow
The Sales Motion is not one monolithic workflow and not a chain of agents. It is a sequence of cognitive states implemented through modular pipelines. Each module can operate independently, while governed artifacts connect the modules horizontally when the evidence is sufficient and the next cognitive step is justified.
Detect and structure emerging change, weak signals, regulation, technology and market developments.
Output: validated foresight / signalBuild an evidence-backed current-state baseline of the company, stakeholders, strategy and relevant developments.
Output: governed company contextConnect the company to market, competitive, industry, regulatory and structural pressures.
Output: market pressure analysisCombine foresight, company reality and market pressure into a testable customer-specific hypothesis.
Output: buying insightTurn analytical findings into a coherent executive story and a customer decision conversation.
Output: buying narrativeMap formal requirements to capabilities, approved evidence, gaps, response structure and human validation.
Output: validated proposal / RFP package04 / Architecture Stack
The architecture separates the cognitive model from pipeline mechanics and execution technology. The Sales Motion therefore remains independent of any single module or tool: The Scanner, RFP Orchestrator, models, agents, databases and other capabilities can evolve without changing the required cognitive progression.
05 / Cognitive Layer
The system advances by changing the state of understanding, not by merely handing work from one agent to another. Each module therefore owns a distinct cognitive question, evidence requirement, reasoning boundary and stopping criterion.
What is changing — and why could it matter?
Detects, classifies and validates emerging signals before they become customer-specific.
What is currently true about this company?
Builds a defensible current-state baseline from company, account and stakeholder evidence.
What external pressures surround this company?
Connects account reality to market, regulation, competition and structural change.
Why could this matter to this customer now?
Separates observed facts from inference, forms a hypothesis and identifies what still requires validation.
What is the coherent story worth discussing?
Turns analysis into a customer-relevant executive narrative without converting hypotheses into facts.
How do we answer the recognized need defensibly?
Maps formal requirements to capabilities, evidence, gaps and approved response components.
06 / Vertical × Horizontal
Vertically, each cognitive step is governed end to end. Horizontally, the system advances only when an approved artifact satisfies the contract for the next step. This makes progression a property of the Cognitive Model Architecture rather than of agent choreography.
07 / Where The Scanner Fits
The broader architecture is the Sales Motion. The Scanner and its modules contribute selected sensing, company-context, market-intelligence and buying-insight capabilities inside that motion. Other components — such as Buying Narrative, Simulator and RFP Orchestrator — continue the cognitive progression.
08 / Shared Data & Knowledge Layer
The Cognitive Model Architecture uses shared governed sources and knowledge services without collapsing all modules into one reasoning process. Common evidence and metadata create consistency; module-specific cognitive logic creates precision.
09 / Buying Narrative
Buying Narrative is a distinct cognitive state between analytical hypothesis and formal response. It does not simply reformat Buying Insight: it reframes validated analysis into a decision-oriented customer conversation while preserving the boundary between evidence, interpretation and open questions.
What could be happening, why could it matter, and what must be validated?
Analytical artifact. Evidence and inference remain explicitly separated.
What is the coherent customer story and leading idea?
Conversation artifact. It frames the situation, evidence, implications, unresolved questions and proposed executive dialogue.
How do we respond once the need is recognized or formalized?
Response artifact. Requirements, capability evidence, claims, gaps and approvals become explicit.
10 / Artifact Contracts
The horizontal architecture becomes reliable when a cognitive state is represented by a governed artifact rather than a loose text handoff. Each artifact therefore carries known fields, evidence state, unresolved uncertainty and rules for downstream consumption.
| Module | Core artifact | Minimum contract idea | Typical consumer |
|---|---|---|---|
| Foresight Creation | Validated Foresight / Signal | Signal, source, date, taxonomy, relevance, confidence, provenance | Market Intelligence, Buying Insight |
| Company Summary | Governed Company Context | Current facts, stakeholders, events, source dates, confidence, unresolved gaps | Buying Insight, Sales |
| Market Intelligence | Market Pressure Analysis | Pressure, evidence, affected capability / business area, direction, strength, uncertainty | Buying Insight |
| Buying Insight | Buying Insight & Hypothesis | Observed evidence, hypothesis, causal logic, uncertainty, validation questions, opportunity direction | Buying Narrative, Sales |
| Buying Narrative | Customer Narrative | Leading idea, evidence-backed story, implications, decision questions, proposed working session | Customer dialogue, Proposal |
| RFP Orchestrator | Validated Response Package | Requirements, mapped evidence, response text, gaps, completeness state, human approvals | Customer / procurement process |
11 / Design Principles