# Build the AI GTM Agent That Knows the Buyer Before the First Message

Dr. Sajjan Kanukolanu

AI Engineer World's Fair 2026

[Talk page](https://ai.engineer/talks/ltv-L5oMPIs-build-ai-gtm-agent-that-knows-buyer) · [Video](https://www.youtube.com/watch?v=ltv-L5oMPIs)

## Build a GTM Agent That Knows the Buyer Before the First Message

Connect visitor identity, CRM history and social signals to buyer intelligence, then use that context to coordinate chat, sales alerts and outreach without restarting discovery.

Familiarity with CRM records, B2B sales workflows and basic data pipelines will help; no specific agent framework is required.

### The buyer arrives informed

[0:01](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1s)

By the time a B2B buyer contacts a vendor, they may already have researched the market, compared alternatives and assembled a shortlist. The seller enters a conversation that has been underway elsewhere, without knowing what the buyer has learned or which competitors remain in contention. The architectural problem is how to recover enough context to make that first interaction useful.

Dr. Sajjan Kanukolanu approaches this problem from his work at [Position²](https://www.position2.com/), where he introduces himself as VP of Global Operations and Strategy, leading services and the company’s AI transformation through deployment. He brings more than twenty years across product, technology and marketing. In his June 2026 month-to-date update, Kanukolanu reports more than 75 client AI agents, more than 18 vertical knowledge bases and more than 800 runs per month. These describe the implementation practice behind the architecture, rather than a measured improvement in sales outcomes.

### Why adding AI to the existing stack is insufficient

[1:18](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=78s)

Adding an AI interface to an existing go-to-market workflow leaves three connected problems to solve:

| Problem | What remains missing |
| --- | --- |
| Buyer understanding | The buyer’s role, history and intent |
| Integration | A joined view of intent signals, CRM records and newly captured context |
| Architecture | A system that uses that context throughout its decisions and actions |

A model cannot infer a relationship history that the surrounding system never supplies. Connecting a few data sources helps, but if the workflow still treats each interaction as an isolated event, the architecture remains the constraint. **Buyer understanding, integration and architecture have to be solved together.**

![Three cards describe missing buyer understanding, disconnected signal and CRM data, and AI bolted onto an unchanged stack.](https://ai.engineer/api/talk-essay-media/2daf9e492883b17df08724a138369e20258e45ad76c91909a5cd464303fedefd)

Three GTM problems: AI, integration, and architecture.

### Do not restart discovery at the chat window

[3:24](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=204s)

The buyer’s research increasingly happens beyond the seller’s visibility. A generative AI conversation can conceal which content the buyer consumed, which vendors they investigated and whether the seller made the shortlist. Kanukolanu cites a 94% figure for GenAI as a primary research source; the linked [Forrester account](https://www.forrester.com/blogs/b2b_buyers_make_zero_click_buying_number_one/) supports the narrower finding that 94% use AI during the buying process, drawing on its 2025 survey. The distinction matters: adoption does not establish that AI is every respondent’s primary research channel.

Kanukolanu also cites a 67% preference for a rep-free buying experience. That is a preference, not a claim that buyers never want human interaction. He then describes 80% of deals as going to vendors on a pre-contact list; the related 6sense research distinguishes roughly 80% wins for the pre-contact favorite from 95% for vendors on the initial shortlist, so favorite status and shortlist membership should not be treated as the same measure. Finally, he cites 17% of buying time spent talking with potential vendors, without specifying the underlying study population or period. The practical point is that vendor conversations occupy only part of the buyer’s decision process.

Now the informed buyer arrives on the website and opens its AI chat. The system asks, “How can I help you?” It follows with another broad discovery question, asking what the visitor wants to know. The seller has gained a conversational interface but still knows nothing about where to begin. Kanukolanu describes buyers abandoning these exchanges because the questions move them backward. The system needs to establish who the visitor is and what they need, then continue from that point.

### Signals, buyer intelligence and action

[6:04](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=364s)

The architecture begins with a **signals layer**. CRM records contribute deals, contacts, account owners, sales representatives and existing conversations. Enrichment adds information about anonymous website visitors. Its quality is a dependency for everything downstream: incorrect identity or company information produces incorrect context and, eventually, inappropriate communication.

Social activity adds signals that a CRM alone may miss. LinkedIn engagement can reveal interest; job changes can reveal a new account opportunity. Consider an executive sponsor at an existing customer who moves to another company. The relationship already exists, but the target account has changed. Capturing that move systematically lets the team add the destination company to its account list and pursue the existing champion relationship there.

The **buyer intelligence layer** turns those inputs into decisions. Its knowledge base holds product information, buyer definitions, ideal customer profiles (ICPs), personas, titles, playbooks and success criteria. The buyer database also holds identified visitor records. Qualification cannot depend on an undefined impression of a good lead: the system must codify what constitutes fit, what indicates a buying stage and what looks like research. A context builder connects the signals, and routing logic decides who should receive which message, when and through which channel. LinkedIn engagement might lead to LinkedIn outreach, an email or an advertisement; the originating channel does not determine the response by itself.

The **action layer** uses those decisions in several places:

- **Website chat:** Address an identified visitor by name, resume prior activity or offer content selected from intent signals.
- **Sales alerts:** Give representatives enough actionable information without overwhelming them.
- **CRM updates:** Record account context produced by the first two layers, beyond a log of sales conversations.
- **Outreach sequences:** Choose the outreach type, recipient and timing.

These are coordinated outputs of the same intelligence. If chat uses context but CRM updates and outbound sequences do not, the buyer can still encounter a fragmented conversation.

### Connect people, accounts and deals

[11:39](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=699s)

The **context graph** is the connected record behind those decisions. It links a buyer’s persona, account and deal to signals, actions and touchpoints. Person-level activity belongs to an account, and an account can contain several people. Connecting those records makes a buying committee visible instead of leaving its members scattered across unrelated contact entries.

Deal context adds another essential question: has sales or marketing already contacted this person, or other members of the committee? Combined with the activity history, this lets the team prioritize high-intent accounts and select the relevant people within them. The graph’s value is not simply that it stores more facts; it lets an account-level decision take account of multiple people and prior outreach.

![Connected Person, Account, and Deal circles link to pages visited, email history, LinkedIn signals, intent score, CRM record, market signals, buying committee, readiness state, outreach sent, and outcome.](https://ai.engineer/api/talk-essay-media/df8c29cf86e73fceb3a9528021e457a3976f18f09e34a411c710002a08da17f3)

The context graph connects Person, Account, and Deal records.

### From an anonymous visit to an outreach decision

[13:08](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=788s)

Position² implements the layers as connected jobs and agents. The initial visit does not arrive with a known person attached. Recognition is work the system must perform:

1. **Identify the visitor.** The visit triggers an identification job. Multiple sources run together because no single tool catches every visitor.
2. **Consolidate and deduplicate.** Combine the identification outputs before passing them into enrichment.
3. **Enrich the contact.** Add the information needed by the intelligence layer. Individual providers can change without changing this overall architecture.
4. **Apply the ICP filter.** An agent consults knowledge-base criteria for industry, geography, company size and persona. Nonmatching contacts and their information are deleted from this flow; qualifying records enter a clean table of qualified accounts.

This ordering matters: qualification operates on consolidated, enriched records and a defined policy, rather than on whichever identification result arrived first.

The qualification boundary can be expressed as a small TypeScript function. It receives enriched records and the criteria maintained in the knowledge base, then produces the qualified collection. The particular industries, geographies, sizes and personas remain policy data rather than being embedded in the function.

```typescript
type EnrichedContact = {
  personId: string;
  accountId: string;
  industry: string;
  geography: string;
  companySize: number;
  persona: string;
};

type IcpPolicy = {
  industries: ReadonlySet<string>;
  geographies: ReadonlySet<string>;
  minCompanySize: number;
  maxCompanySize: number;
  personas: ReadonlySet<string>;
};

function qualifyContacts(
  contacts: readonly EnrichedContact[],
  policy: IcpPolicy,
): EnrichedContact[] {
  return contacts.filter((contact) =>
    policy.industries.has(contact.industry) &&
    policy.geographies.has(contact.geography) &&
    contact.companySize >= policy.minCompanySize &&
    contact.companySize <= policy.maxCompanySize &&
    policy.personas.has(contact.persona)
  );
}
```

The returned collection excludes nonmatches; it does not itself delete stored records. In the described workflow, deletion and persistence of the clean table are subsequent storage operations.

Next, the **match agent** checks qualified people against CRM history: has the team talked to them, and are they warm or hot? The **action agent** then decides what happens per person, including coordinated decisions across an account’s buying committee. Its outputs can include a Slack alert with context and a draft email for a representative, a decision to send an email directly, or LinkedIn outreach. A draft supplied to a representative and an automatically sent message are different action paths; selecting an action does not make every draft a completed send.

### What the visitor and GTM team see

[16:34](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=994s)

The product demonstration begins with Position²’s system, Intelligence. On arrival, Kanukolanu receives a personalized chat message that refers to an earlier conversation and asks whether he wants to continue it. He explains that accepting produces a link to that specific conversation. The visible experience is a continuation of known activity, replacing the generic opening question with a relevant next step.

The internal interface separates GTM and organic sections. Within GTM, Kanukolanu opens the anonymous-visitor dashboard to show how the identification workflow organizes visitors. The demonstrated dashboard contains approximately 3,000 visitors from approximately 280 accounts, with no reporting window stated. Information technology appears as a leading visiting industry and is also one of Position²’s target verticals.

The dashboard combines an industry breakdown with hot contacts and accounts, using signals that include prior HubSpot conversations. Kanukolanu has changed the displayed names for the demonstration while retaining accurate titles. Contact records expose company, location and industry information; the team can sort by industry, seniority and engagement, or inspect the companies visiting the site. These views turn the underlying records into choices about which accounts and people to pursue.

The LinkedIn intelligence view provides a second route into the same kind of account analysis. For the preceding few days, Kanukolanu reports about 100 people arriving through LinkedIn from 73 companies and engaging with eight recent posts. The view lists people, interaction types and company affiliations. Seniority filters separate C-suite executives, VPs, directors, managers and individual contributors; clicking a record exposes more detail about its overall engagement.

### Where the system breaks

[21:15](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1275s)

**ICP drift** makes a correct filter stale. A team might initially target companies with $20 million in annual recurring revenue in one vertical, then win customers with $50 million or $100 million in another. Those outcomes can change which accounts deserve attention, but only if the knowledge base changes with them. Kanukolanu recommends quarterly retraining of models and agents using closed-won and closed-lost opportunities. He does not specify whether that involves model-weight updates or changes to knowledge and agent configuration; the concrete requirement is that new customer evidence reaches future qualification decisions.

**Alert fatigue** breaks the connection between intelligence and action. When every account is hot, representatives become overwhelmed, stop acting and lose trust in the system. The knowledge base and context graph should therefore restrict alerts to accounts and contacts worth a salesperson’s attention. Alert volume is not evidence that the agent is helping.

**Identity limits** constrain how much personalization the pipeline can support. Kanukolanu estimates roughly 70% or slightly higher company identification accuracy, versus approximately 15–20% for individuals. He describes these as structural limitations of available tools, but provides no evaluation defining whether the percentages measure correctness, coverage or match rate. Those measures are different: identifying a fraction of visitors does not establish that the resulting identities are correct. His operational advice is to test alternative systems against existing results and plan outreach around the identification limits actually observed.

**Human approval friction** can stop an otherwise functioning pipeline. A queue that feels like a chore becomes backlogged and ignored. Drafts should need only minor edits and make sending easy, ideally a single click after review. Position² uses more than 30 seconds of email editing as a warning threshold: Kanukolanu says representatives then prefer writing the message themselves. This is an adoption heuristic, tying the quality of generated drafts to the effort required to use them.

### Make the policy controllable and the feedback continuous

[24:37](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1477s)

Identity is the starting dependency, but it must participate in a feedback loop: visitor information should flow into the knowledge base, and that knowledge should inform subsequent decisions. **Score fit and intent separately.** Fit asks whether this is the kind of buyer the business serves; intent asks what the available signals say about the buyer’s readiness. Combining the two into an undifferentiated judgment can send the wrong message to the wrong person.

An **auditable, adjustable policy engine** gives the GTM team control over those decisions. When an output is wrong, an operator needs to locate the responsible agent or workflow stage and adjust it, rather than depending on a developer for every correction. The qualification criteria, routing choices and action decisions need to remain inspectable parts of the system.

Finally, the workflow must capture what happens after it acts. Sends, replies and closed deals create new evidence; wins, losses and deferred sales should return to the knowledge base so agents can use them in later decisions. That closes the architectural loop: the system does not merely accumulate visitor signals and produce messages. It uses the outcomes of those messages to improve whom it recognizes as relevant, when it engages and what it proposes next.

![Four colored cards read Start With Identity, Score Fit and Intent Separately, Build a Policy Engine, and Let the Flywheel Compound.](https://ai.engineer/api/talk-essay-media/d401b29dfb7f65ef7b0d7ef5468a40a585d031c0598ab437273d7696395f415d)

Four takeaways: identity, separate fit and intent scores, a policy engine, and a compounding flywheel.

## Resources

- [B2B Buyers Make Zero-Click Number One](https://www.forrester.com/blogs/b2b_buyers_make_zero_click_buying_number_one/) — Forrester explains its 2025 survey findings on business buyers' AI adoption and information sources.
- [Visitor Identification Match Rates](https://www.warmly.ai/p/blog/visitor-identification-match-rates) — A vendor's explanation of company versus person matching, traffic-dependent coverage, and the separate need to validate match correctness.

## Slides

### Build the AI GTM Agent That Knows the Buyer Before the First Message

Kanukolanu says buyers research and compare vendors, and may have already shortlisted them before reaching a seller. He introduces an architecture to help GTM teams know buyers better.

[0:00](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=0s) [Title slide naming Sajjan Kanukolanu and the AI Engineer World’s Fair 2026.](https://assets.ai.engineer/sites/aiecode2025/sha256/356e57c6f7252baf706b7a9eaca78c471497ac4a20e84072e5f3c40683c3a4f1.webp)

Build the AI GTM Agent That Knows the Buyer Before the First Message

Sajjan Kanukolanu, PhD
VP, Global Operations and Strategy, Position²

AI Engineer World’s Fair 2026 · San Francisco

p²
© Position², 2026
1

### Dr. Sajjan Kanukolanu

Kanukolanu leads Position²’s services team and AI-native transformation. He reports 75+ AI agents for clients, 18 vertical knowledge bases powering agents, and 800+ automated runs per month, as of June 2026 month to date.

[0:34](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=34s) [Speaker introduction with a portrait, experience summary, and figures for AI agents, knowledge bases, and automated runs.](https://assets.ai.engineer/sites/aiecode2025/sha256/32d3896a74190f6295c659a8d56b6a1e03eea69b771220cf4c192e643d71de39.webp)

Dr. Sajjan Kanukolanu

20+ years across product, technology, and marketing.

At Position², I lead the services team and our AI-Native transformation — vision → positioning → deployment.

75+ AI Agents for Clients

18 Vertical Knowledge Bases Powering Agents

800+ Automated Runs/Month

© Position², 2026
2

### Three Problems Connecting AI to the GTM Stack

Kanukolanu argues that buyer context, integration, and architecture must be solved together: a standalone model lacks buyer context, while AI bolted onto an unchanged stack will not scale.

[1:48](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=108s) [Three cards describe AI’s lack of buyer context, disconnected integration, and AI bolted onto an unchanged architecture.](https://assets.ai.engineer/sites/aiecode2025/sha256/527e9f3bdeb4f567c6e90d6c26c8b5984cf784e45f360780d80f32dfb3a710b7.webp)

Connecting AI To The Stack That Runs Your GTM Is Not One, But Three Problems

01
AI
The model doesn’t know your buyer—their role, their history, their intent.

02
Integration
The stack isn’t connected to signal data, CRM context, or identity resolution.

03
Architecture
AI bolted onto an unchanged stack.

Most GTM deployments do not solve for all three problems simultaneously– and they fail.

© Position², 2026
3

### The Buyer Is Late-Stage When They Engage

The slide cites 6Sense: 80% of deals go to the buyer’s pre-contact favorite (2025); Gartner: 17% of total buying time is spent talking to potential vendors. The speaker warns that basic chat questions can drive buyers away.

[3:23](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=203s) [Four reported statistics describe buyer research, preference for rep-free experiences, pre-contact favorites, and time spent with vendors.](https://assets.ai.engineer/sites/aiecode2025/sha256/c96e0e3c592d54821c91b1544d305125a99e00e4c29d4b933f7902ee792ca462.webp)

The Buyer Is Not Early-Stage When They Engage You. They’re Late-Stage. Build For That.

94%
buyers use GenAI as primary research
Forrester 2026

67%
of B2B buyers prefer a rep-free experience
Gartner, 2026

80%
of deals go to the buyer’s pre-contact favorite
6Sense 2025

17%
of total buying time is spent talking to potential vendors.
Gartner B2B Buying Journey

By the time they open your chat window, the research is done. The question is whether your system knows it.

© Position², 2026
4

### What It Takes to Build a System That Knows the Buyer

The speaker turns to how a system can recognize a buyer and their needs when they arrive on a site.

[6:15](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=375s) [Section title introducing a system that knows the buyer.](https://assets.ai.engineer/sites/aiecode2025/sha256/459f433b6bb9150b58ec88c53a89251eb899c0f656811afce2a5a749b10acda0.webp)

What It Takes To Build A System
That Knows The Buyer

p²
© Position², 2026
5

### The 3-Layer Architecture Behind Intelligent GTM

CRM, enrichment, and LinkedIn signals feed buyer intelligence, which builds context and routes messages. That context supports personalized chat, rep alerts, CRM updates, and outreach sequences.

[6:18](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=378s) [Three columns describe signals, buyer intelligence, and resulting actions.](https://assets.ai.engineer/sites/aiecode2025/sha256/c40c51d279108c81a3d8be67a53344c79575f850e1335a0ad54dec731be9f611.webp)

The 3-Layer Architecture Behind Intelligent GTM

Signals
CRM
Contact, deal stage, owner

Enrichment
Role, company, tech stack

LinkedIn Signals
Engagement, job changes, intent

Buyer Intelligence
Knowledge Base
Product context, playbooks, ICP criteria

Visitor Identity
Deanonymize-match to contact/acct.

ICP Scoring
Score fit, tier, buying stage

Context Builder
Assemble buyer context graph

Routing Logic
Segment → message track → rep assignment

Action
Chat Greeting
Personalized first message, pre-loaded context

Rep Alert
Slack / email — buyer context + recommended next step

CRM Update
Contact scored, tagged, routed in HubSpot

Sequence Trigger
Outreach sequence auto-enrolled

Without these, you're running a generic GTM on an expensive model.

© Position², 2026
6

### The Context Graph — One Connected Record Per Buyer

The graph links person signals and account context to a deal, including outreach and outcomes, so teams can prioritize high-intent accounts and contacts.

[11:36](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=696s) [A graph connects person, account, and deal records to signals and outcomes.](https://assets.ai.engineer/sites/aiecode2025/sha256/a18b6a43707961281cbc17599c90ba4cd326766c568073dcc70ce54bed371ea2.webp)

The Context Graph — One Connected Record Per Buyer
Every signal, action, and outcome — unified across Person, Account, and Deal

PERSON
name · title · linkedin

PAGES VISITED
pricing · case studies · blog

EMAIL HISTORY
opens · clicks · replies

LINKEDIN SIGNALS
likes · comments · reactions

INTENT SCORE
hot · warm · cold

ACCOUNT
company · ICP tier · tech stack

CRM RECORD
hubspot · deal stage · owner

MARKET SIGNALS
funding · hiring · M&A

BUYING COMMITTEE
champion · DM · approver

READINESS STATE
state machine position

DEAL
stage · owner · history

OUTREACH SENT
Slack · email · crm

OUTCOME
reply · meeting · pipeline

Legend: Person signals · Account signals · Deal / Outcomes · Intelligence layer
© Position², 2026
7
p²

### Visitor identification and enrichment workflow

Apollo and Clay run together to identify site visitors. Their results are consolidated and deduplicated before enrichment; the speaker says no single tool catches every visitor.

[13:33](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=813s) [A workflow connects visitor identification sources to enrichment and a knowledge base.](https://assets.ai.engineer/sites/aiecode2025/sha256/42b8d069a899df8ec03aad8fd8af2669ac87b0e87fc7601bff3ecc5829f3e148.webp)

Apollo — Visitor ID
Operation: Search People
Apollo API Key: [redacted]
Keywords: <sitevisitor>
Error

Clay — Visitor ID Orchest...
Webhook URL: https://api.clay.com...
Data (JSON Or Plain Text): <start>
Auth Token: -
Error

Enrichment & Consolidati...
Messages: You enrich and consolid...
Model: claude-opus-4-8
Files: -
Thinking Level: high
Tools: -
Skills: -
Memory: sliding window (tokens)
Conversation ID: -
Max Tokens: -
Max Output Tokens: -
Response Format: -
Error

Knowledge Base
Operation: List Documents
Search: <start>
Status Filter: All
Limit: 1000
Offset: -
Error

ICP Filter Ag...
Messages: You are...
Model
Files
Tools
Skills
Memory
Conversation ID
Response Format
Error

Interface text:
agent.thearena.ai/workspace/5349c0c4-6c72-492b-9330-1e1f42e65f40/w/1d8fd502-c254-42d8-93e9-cab113e8bd8a
Work
Chat
Toolbar
Editor
Triggers
Start
Schedule
Webhook
Airtable
Ashby
Attio
Azure DevOps
Cal.com
Calendly
Circleback
Confluence
Email Bison
Fathom
Fireflies
GitHub
GitLab
Gmail
Gong
Google Calendar
Logs
No logs yet

### ICP filtering and CRM matching workflow

The ICP filter checks enriched contacts against knowledge-base criteria. Qualifying accounts move to a table, then the CRM match agent checks prior contact and warmth.

[14:28](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=868s) [A workflow connects a knowledge base and ICP filter agent to qualified accounts.](https://assets.ai.engineer/sites/aiecode2025/sha256/c3569a5d4912dc45d0f14b15f4be693d236a538d9f442a0db72793f3169fc209.webp)

Knowledge Base
Operation: List Documents
Search: <start>
Status Filter: All
Limit: 1000
Offset: -
Error

ICP Filter Agent
Messages: You are an ICP (Ideal Cu...
Model: claude-opus-4-8
Files: -
Tools: -
Skills: -
Memory: conversation
Conversation ID: -
Response Format: name, schema +1
Error

Qualified Accounts
Operation: Query Rows
Table: -
Input Mode: Builder
Filter Conditions: -
Sort Order: -
Limit: 100
Offset: 0
Error

Interface text:
agent.thearena.ai/workspace/5349c0c4-6c72-492b-9330-1e1f42e65f40/w/1d8fd502-c254-42d8-93e9-cab113e8bd8a
Work
Chat
Toolbar
Editor
Toolbar
Triggers
Start
Schedule
Webhook
Airtable
Ashby
Attio
Azure DevOps
Cal.com
Calendly
Circleback
Confluence
Email Bison
Fathom
Fireflies
GitHub
GitLab
Gmail
Gong
Google Calendar
Logs
No logs yet

[15:20](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=920s) [Workflow connecting qualified accounts and CRM data to a matching agent.](https://assets.ai.engineer/sites/aiecode2025/sha256/8d5532f810b3fb34656093f2ff1f35315e1ed8f0991c50db330c1e7beebd313d.webp)

[illegible]er Agent
[illegible] You are an ICP (Ideal Cu...
[illegible] claude-opus-4-8
[illegible] -
[illegible] -
[illegible] -
[illegible] conversation
[illegible] -
[illegible] name, schema +1
[illegible]

HubSpot CRM
Operation: Get Contacts
HubSpot Account: -
Contact ID Or Email: <start>
ID Property: <start>
Error

Qualified Accounts
Operation: Query Rows
Table: -
Input Mode: Builder
Filter Conditions: -
Sort Order: -
Limit: 100
Offset: 0
Error

CRM Match Agent
Messages: You are a matching engi...
Model: claude-opus-4-8
Files: -
Tools: -
Skills: -
Memory: conversation
Conversation ID: -
Response Format: name, schema +1
Error

Action Q[illegible]
Operation
Table
Input Mode
Filter Condition[illegible]
Sort Order
Limit
Offset
Error

Interface text:
agent.thearena.ai/workspace/5349c0c4-6c72-492b-9330-1e1f42e65f40/w/1d8fd502-c254-42d8-93e9-cab113e8bd8a
Work
Chat
Toolbar
Editor
Toolbar
Triggers
Start
Schedule
Webhook
Airtable
Ashby
Attio
Azure DevOps
Cal.com
Calendly
Circleback
Confluence
Email Bison
Fathom
Fireflies
GitHub
GitLab
Gmail
Gong
Google Calendar
Logs
No logs yet

### Action decision workflow

The CRM Match Agent feeds an Action Queue and an Action Decision Agent, which the speaker says chooses next steps for an individual or an account’s buying committee.

[15:40](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=940s) [Workflow connecting a CRM matching agent to an action queue and decision agent.](https://assets.ai.engineer/sites/aiecode2025/sha256/d6bae7482c0638edfc3305137f9d13ab66ff0a439f1280e3fdc1358d4062c6c7.webp)

CRM Match Agent
[illegible]essages  You are a matching engi...
[illegible]odel  claude-opus-4-8
[illegible]les  -
[illegible]ools  -
[illegible]kills  -
[illegible]emory  conversation
[illegible]onversation ID  -
[illegible]esponse Format  name, schema +1
[illegible]rror

Action Queue
Operation  Query Rows
Table  -
Input Mode  Builder
Filter Conditions  -
Sort Order  -
Limit  100
Offset  0
Error

Action Decision Agent
Messages  You are a sales-ops pla...
Model  gpt-5.5
Files  -
Tools  -
Skills  -
Memory  conversation
Conversation ID  -
Response Format  name, schema +1
Error

Interface text:
agent.thearena.ai/workspace/5349c0c4-6c72-492b-9330-1e1f42e65f40/w/1d8fd502-c254-42d8-93e9-cab113e8bd8a
Work
Chat  Toolbar  Editor
Toolbar
Triggers
Start
Schedule
Webhook
Airtable
Ashby
Attio
Azure DevOps
Cal.com
Calendly
Circleback
Confluence
Email Bison
Fathom
Fireflies
GitHub
GitLab
Gmail
Gong
Google Calendar
Google [illegible]
Logs
No logs yet

### Slack action

The action decision agent feeds a Slack message step. The speaker says it chooses alerts for sales reps with context and a possible email draft.

[15:58](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=958s) [An action decision agent connects to a Slack message step.](https://assets.ai.engineer/sites/aiecode2025/sha256/418b7f6d14ec8f16041e0a51ecf3df1b998c771f50651e81d4be61a77a919b07.webp)

Action Queue
Operation: Query Rows
Table: -
Input Mode: Builder
Filter Conditions: -
Sort Order: -
Limit: 100
Offset: 0
Error

Action Decision Agent
Messages: You are a sales-ops pla...
Model: gpt-5.5
Files: -
Tools: -
Skills: -
Memory: conversation
Conversation ID: -
Response Format: name, schema +1
Error

Slack
Operation: Send Messag[illegible]
Authentication Method: Sim Bot (b[illegible]
Destination: Channe[illegible]
Slack Account: Sajjan Kanukolanu’...
Channel ID
Message Format: Plain Tex[illegible]
Message: <actiondecisionagent.ac...
Thread Timestamp
Attachments
Error

Interface text:
agent.thearena.ai/workspace/5349c0c4-6c72-492b-9330-1e1f42e65f40/w/1d8fd502-c254-42d8-93e9-cab113e8bd8a
Work
Chat
Toolbar
Editor
Triggers
Start
Schedule
Webhook
Airtable
Ashby
Attio
Azure DevOps
Cal.com
Calendly
Circleback
Confluence
Email Bison
Fathom
Fireflies
GitHub
GitLab
Gmail
Gong
Google Calendar
Logs
No logs yet

### Personalized welcome

On landing, Sajjan sees a personalized chat prompt asking whether he wants to continue an earlier conversation.

[16:53](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1013s) [A website displays a prompt to continue an earlier interaction.](https://assets.ai.engineer/sites/aiecode2025/sha256/ea559d65969c5416a6cc2c31bc73303771bb253092336b222be6790a8f03adc5.webp)

Hi Sajjan 👋
Want to continue where you left off?

Interface text:
SOUND
keep on growing
position²

### Contextual chat prompt

Vimi recalls Sajjan’s visit to the Website Visitors page and asks whether he wants to continue from the Acme Corp view. The demo shows him typing “yes.”

[17:12](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1032s) [An expanded chat offers to resume a previous website visit.](https://assets.ai.engineer/sites/aiecode2025/sha256/292ad2848929f920750c77a2a561d208f1dbf357644219c5ef131e1ba0b40f82.webp)

Vimi
online

Hi Sajjan 👋 you visited the Website Visitors page and were checking out Acme Corp on 23rd June. Want to continue from there?

yes

Interface text:
SOUND
keep on growing
position²

### Personalized chat

Vimi recalls Sajjan checking out Acme Corp on the Website Visitors page on 23 June. After he replies “yes,” it offers a link back to that view. The presenter connects the personalized prompt to collected user signals.

[17:22](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1042s) [The chat responds to the visitor and offers a link to the previous view.](https://assets.ai.engineer/sites/aiecode2025/sha256/5b55e9aee4dbfb89bff527fb64d109b008fec6f9de7166678caa9573c5a240b5.webp)

Vimi
online

Hi Sajjan 👋 you visited the Website Visitors page and were checking out Acme Corp on 23rd June. Want to continue from there?

yes

Perfect — here's exactly where you left off:

Open Website Visitors → Acme Corp

You'll sign in once, then land right on that view.

Interface text:
Type a reply...
SOUND
keep on growing
position²

[17:25](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1045s) [A chat assistant offers a link to resume an earlier dashboard visit.](https://assets.ai.engineer/sites/aiecode2025/sha256/333acd318558dc62763580204ee58dbf1b4ee60a529e0b5a47997195176bfdad.webp)

Vimi
online

Hi Sajjan 👋 you visited the Website Visitors page and were checking out Acme Corp on 23rd June. Want to continue from there?

yes

Perfect — here's exactly where you left off:

Open Website Visitors → Acme Corp

You'll sign in once, then land right on that view.

Interface text:
Type a reply...
ENABLE SOUND
keep on growing
position²

### GTM and SEO dashboard choices

The intelligence hub separates go-to-market and organic growth dashboards. The speaker chooses the GTM dashboard for the walkthrough.

[18:09](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1089s) [Two cards offer GTM and SEO dashboards, with descriptions and dashboard counts.](https://assets.ai.engineer/sites/aiecode2025/sha256/8f1628a564311db6cd97dc5c0a657ebf175d1f1fcc6bbcce9b0474be522fbbca.webp)

TWO DISCIPLINES · ONE INTELLIGENCE LAYER

GO-TO-MARKET
GTM
Active
Buyer signals, ad intelligence, anonymous visitor de-anonymisation, job-change alerts, and LinkedIn scraping — your full go-to-market intelligence layer.
5 dashboards   4 live   Open →

ORGANIC GROWTH
SEO
Active
SEO & GEO audits, content research, article briefs, keyword research, agent readiness, image alt audits, knowledge base, and team insights.
10 dashboards   10 live   Open →

Interface text:
Intelligence
Context Graph
Sajjan
https://intelligence.position2.com/gtm
keep on growing
position²

### GTM dashboard menu

The GTM menu shows five dashboards: four are live, while Job Change Alert is coming soon. The speaker opens Anonymous Visitors and plans to cover LinkedIn Intelligence.

[18:21](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1101s) [Five GTM dashboard cards include anonymous visitors and LinkedIn intelligence.](https://assets.ai.engineer/sites/aiecode2025/sha256/a97d056823d71f568720120f0a033e2622e17da3484a5d119cab76842ecb700f.webp)

Target Accounts
LIVE
Real-time signals across 1,500+ companies — funding rounds, C-suite changes, M&A, IPO alerts, and news mentions.
Healthcare · CSG

Ad Intelligence
LIVE
Monitor competitor ad creatives, messaging, and estimated spend across Google, Meta, and LinkedIn.
Google Ads · Meta · LinkedIn

Anonymous Visitors
LIVE
De-anonymize website visitors — identify companies and surface high-intent accounts before they fill out a form.
Position2 · Apollo

LinkedIn Intelligence
LIVE
Post & People Intelligence — track who engaged with your posts, surface decision-makers, and build ABM target lists.
Leads · Enrichment

Job Change Alert
COMING SOON
Get notified when key decision-makers at target accounts change roles — the best time to reach out is within days of a job change.
[illegible]

Interface text:
Intelligence · Hub · GTM · Sajjan
https://intelligence.position2.com/gtm/anonymous-visitors
keep on growing
position2

### Anonymous Visitors Dashboard

The dashboard identifies 2,924 visitors across 281 companies, with information technology and services as the top industry. It also shows an industry breakdown and a list of hot signals.

[18:30](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1110s) [Dashboard showing visitor and company counts, an industry breakdown, and hot signals.](https://assets.ai.engineer/sites/aiecode2025/sha256/62f7b42e557deeaf4a1aa3dbdabbab7d122dd6e0c8cb61f7febeb95d7bde8f5d.webp)

GTM · INTENT INTELLIGENCE
Anonymous Visitors
De-anonymized visitors enriched with job title, company, and industry data. Click any row, card, or bar for details.

People visiting position2.com — identified and enriched automatically.
Position2  Apollo

PEOPLE IDENTIFIED
2924

UNIQUE COMPANIES
281

TOP INDUSTRY
information technology & services

Industry Breakdown
click a bar to explore
information technology & s...  81
hospital & health care  17
marketing & advertising  16
financial services  14
construction  10
management consulting  10
health, wellness & fitness  8
machinery  8

Hot Signals
In your HubSpot list
click to engage
Michael Brennan — Chief Marketing Officer — C-Suite — 2026-06-24
Sarah Whitfield — VP of Demand Generation — VP — 2026-06-24
David Caldwell — Director of Growth Marketing — Director — 2026-06-24
Jennifer Hollis — Senior Director, Digital Strategy — Director — 2026-06-24
Robert Sanders — Founder & CEO — C-Suite — 2026-06-24

People (2924)  Companies (281)
Search name, company, title, location, industry...
From  mm/dd/yyyy  To  mm/dd/yyyy  Clear
All Industries  All Seniority  All Engagement  All Locations  All Company Sizes

Interface text:
Platform  Hub  GTM  Anonymous Visitors
Sajjan
Refresh
keep on growing
position²

### Companies Tab

The selected Companies tab shows 281 unique companies, with filters for industry, seniority, engagement, location and company size. The dashboard also highlights HubSpot matches.

[20:02](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1202s) [Anonymous visitors dashboard with the companies tab selected and a count of 281 companies.](https://assets.ai.engineer/sites/aiecode2025/sha256/d2601808e9061eeb598c8572e8b5bab0a1ba7254d46e97bba7c39d43f577f4c8.webp)

GTM · INTENT INTELLIGENCE
Anonymous Visitors
De-anonymized visitors enriched with job title, company, and industry data. Click any row, card, or bar for details.
Refresh

People visiting position2.com — identified and enriched automatically.
Position2  Apollo

PEOPLE IDENTIFIED
2924
UNIQUE COMPANIES
281
TOP INDUSTRY
information technology & services

Industry Breakdown
click a bar to explore
information technology & s...  81
hospital & health care  17
marketing & advertising  16
financial services  14
construction  10
management consulting  10
health, wellness & fitness  8
machinery  8

Hot Signals
In your HubSpot list
click to engage
Michael Brennan — Chief Marketing Officer — C-Suite — 2026-06-24
Sarah Whitfield — VP of Demand Generation — VP — 2026-06-24
David Caldwell — Director of Growth Marketing — Director — 2026-06-24
Jennifer Hollis — Senior Director, Digital Strategy — Director — 2026-06-24
Robert Sanders — Founder & CEO — C-Suite — 2026-06-24

People (2924)  Companies (281)
Search name, company, title, location, industry...
From  mm/dd/yyyy  To  mm/dd/yyyy  Clear
All Industries  All Seniority  All Engagement  All Locations  All Company Sizes
281 of 281

Interface text:
Platform  Hub  GTM  Anonymous Visitors
Sajjan
https://intelligence.position2.com/gtm
keep on growing
position²

### LinkedIn Intelligence: People

The people view groups LinkedIn engagement by person and seniority. The speaker says about 100 people visited the site through LinkedIn in the last few days, from 73 companies, and engaged with eight recent posts.

[20:12](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1212s) [People dashboard with engagement totals, filters, profile cards, and a company leaderboard.](https://assets.ai.engineer/sites/aiecode2025/sha256/1d9157d44337b882dbde6f784c3eadc43307aa1e4a0769e936b08a0a318de795.webp)

LinkedIn Intelligence
Signal tracking: people, companies & post engagement

PEOPLE 99
COMPANIES 73
POSTS 8
HOT LEADS
Matched from HubSpot

SENIORITY
All
C-Suite
VP/Dir
Manager
IC
Search name, title, compe[illegible]
99 people

All countries
All locations
All degrees
Any activity
mm/dd/yyyy → mm/dd/yyyy
Decision Makers
Hide Position²
Reset

C-Suite / Founders
25 people

Rajiv Parikh
Growth Marketing CEO
C-Level · 3rd
GTM Community Builder
LinkedIn
2 posts

Ankur Srivastava
CEO and Founder
C-Level · 3rd
Flywl
LinkedIn
2 posts

Fella A.
Co-Founder & COO
C-Level · 3rd · FR
We Better Ai
London Area, United Kingdom
9
LinkedIn
1 post

Mary Voss
Vice President, Human Resources
C-Level · 3rd · US
Trivium Corporate Solutions
San Francisco Bay Area
92
LinkedIn
1 post

Jeevathman Paulraj
Founder
C-Level · 3rd · US
DemandVibes
Chennai, Tamil Nadu, India
9
LinkedIn
1 post

Sallee Poinsette-Nash
CEO
C-Level · 3rd
LinkedIn
1 post

Francis Dimayuga
Proven Vice President: Digital/Paid Media
C-Level · 3rd
LinkedIn
1 post

Lama Mansour
Co-Founder
C-Level · 3rd
CMO, Soteri Skin Inc.
LinkedIn

Pavan Deshapande
David Roebuck
Verdi Israelyan
Frank DESVIGNES

COMPANY LEADERBOARD
1 Position² 10
2 Fuel AI 1
3 GTM Commu... 1
4 Flywl 1
5 Enterprise B... 1
6 We Better Ai 1
7 Trivium Corp... 1
8 DemandVibes 1
9 Application D... 1
10 Amazon Web ... 1
11 The Patel Mo... 1
12 Agentic AI 1
13 B2B SaaS, Fi... 1
14 Real-Time 3D... 1
15 Position² Mar... [illegible]

### Where It Breaks – Things That Go Wrong

Stale ICP data and excessive hot alerts can misdirect or overwhelm reps. Identification has a ceiling, while cumbersome approvals stall outreach. The speaker recommends quarterly retraining and making drafts quick to send.

[21:04](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1264s) [Four failure points: ICP drift, alert fatigue, identity ceiling, and human bottleneck.](https://assets.ai.engineer/sites/aiecode2025/sha256/70f8a9d6f1f1dc8a7829d2410e8c442a084b2f40022e6073482b668c17800458.webp)

Where It Breaks – Things That Go Wrong

ICP Drift
Your ICP evolves. Your system does not — unless you force it to. Quarterly retrain on last 90 days of closed-won. Non-negotiable.

Alert Fatigue
Too many HOT signals → reps stop acting → system ignored. Use the Knowledge Base and the Context Graph to reduce noise and focus on key accounts and outreach channels.

Identity Ceiling
70%+ of companies, 15%-20% of individuals. Structural limit. Build warm path for known, cold path for rest.

Human Bottleneck
The approval queue becomes a chore. Shrink the friction. Draft + one-click send. Optimize time to send.

© Position², 2026
8

## Full transcript

[0:01](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1s) Hello. We know that the modern B2B selling has evolved significantly. The uncomfortable truth is that by the time the buyer reaches you, the decision is mostly made. They've researched, compared, and probably shortlisted vendors or partners that they want to work with.

[0:20](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=20s) That may include you or your competitors. This talk is about the architecture that lets GTM teams know the buyer more than they today.

[0:32](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=32s) My name is Sajjan Kanukolanu. I have twenty-plus years' experience across product, technology, and marketing. At Position² as the VP of Global Operations and Strategy, I lead the services teams and our AI native transformation from vision to positionings to deployment, where I work closely with our technology team.

[0:54](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=54s) We have launched seventy-five-plus AI agents specifically for our clients, eighteen-plus vertical knowledge bases that power these agents, and we've had eight hundred-plus runs per month, and this is data as of month to date June twenty twenty-six.

[1:11](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=71s) By the time we get to the end of the year, I expect these numbers to increase significantly.

[1:18](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=78s) The interesting thing about GTM and AI is that many GTM teams try to bolt AI onto their existing stack or existing processes and workflows, and therein lies the problem.

[1:33](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=93s) That approach itself is hindrance to scale. The interesting thing, though, is there are three different problems that GTM leaders and GTM teams have to solve in order to be successful in this AI era.

[1:50](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=110s) And these three are, number one, AI. By just bolting AI onto your existing systems, AI doesn't really and cannot really find out

[2:01](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=121s) who your buyer is. It doesn't understand their role. It doesn't understand their history. It doesn't understand their intent standalone.

[2:10](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=130s) That's number one. Number two is the integration itself. The old GTM stacks may not necessarily be best positioned to capture all the intent signals and the data, the CRM context, context that the AI captures on its own and bring that all together.

[2:27](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=147s) So the systems today, as they stand, may be broken. By putting AI on top of it is not gonna help solve a problem. The third is the architecture.

[2:38](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=158s) The underlying architecture has to evolve with AI at the core, and I'll talk about what I mean by that in a little bit. But the fundamental concept here is that with AI bolted on to your existing GTM systems, processes, and workflows, you will not be able to scale.

[3:00](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=180s) And most GTM deployments do not solve for all these three problems simultaneously. You could accomplish one and two, but if three is not accomplished or you don't solve for number three, then you still have a problem.

[3:14](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=194s) So it is important that all these three problems are solved together, and I will show you an architecture diagram in just a bit that's gonna walk you through how we do it at Position².

[3:24](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=204s) Another problem that we face is that with the buyer. The buyers are constantly evolving,

[3:32](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=212s) and what I mean by that is by the time the buyer reaches out to you in today's world, they are not early stage. They're actually late stage.

[3:42](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=222s) Here are some stats to prove that point. Ninety-four percent of buyers use GenAI as a primary research,

[3:49](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=229s) and these platforms are almost like a black box where we don't know what they consumed, what they read about, who they have investigated, if your organization is on top of that list or not.

[4:02](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=242s) And that is information that is from the Forrester twenty twenty-six research. The second stat is about sixty-seven percent of B2B buyers prefer a rep-free experience. They don't want to talk to people as they make their decision.

[4:18](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=258s) Eighty percent of deals, very interesting statistic. Eighty percent of deals go to the vendors who are part of the pre-contact list, so essentially buyers have already made up their mind.

[4:31](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=271s) And the fourth and very vital stat here is only seventeen percent, only seventeen percent of the total buying time is spent talking with potential vendors. What all these numbers tell us is the buyers do their research thoroughly.

[4:46](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=286s) They use various tools, including the GenAI platforms, and by the time they come talk with you or come to your website, they have made up their mind.

[4:55](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=295s) Now imagine a situation where the buyer does that research, comes to your website, and you have a chat window for them to engage with so they can converse with your very intelligent AI system that is now responsible for telling them about what you have to offer and how they can buy your services or product.

[5:15](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=315s) But many GTM systems that are bolted with AI would essentially start off with a conversation that would be something like this: "How can I help you?

[5:27](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=327s) What is it that you would like to... What is it that you would like to know today?"

[5:32](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=332s) But these are questions that actually move you backwards. They don't move you forward as an organization. The buyer has done their research, and when some basic questions are asked to them, they're actually walking out of the system.

[5:46](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=346s) They're not continuing their conversation. So it is very important that as a seller, you know what the buyer's needs are, you know who the buyer is, you know who the buyer is, who-- what their buying needs are, and you're able to cater to those as they engage on your site.

[6:04](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=364s) So what does this really mean when it comes to implementing an architecture? How does one accomplish an architecture or a system where the buyer information is known as soon as they come to your site?

[6:19](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=379s) There are essentially three architectural layers behind an intelligent system and running an intelligent GTM. The first is signals. This includes all the communication and information coming from your CRM systems, which includes your information about the deals, your contacts, who the owner or the sales rep is for that, who are you conversing with.

[6:43](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=403s) It also includes an enrichment system where you have the right information pulled out of these anonymous visitors that are hitting your site.

[6:53](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=413s) This system is going to work as long as that information is accurate. If you're off on the enrichment, your data is off and so is your communication.

[7:04](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=424s) And one of the things that we find really helpful and really useful, very important, is signals coming out of social media platforms, especially LinkedIn. What we find is the engagement, the job changes are huge signals for you to capture as an organization, which we do as ourselves, and I'll show you what, what I mean by that.

[7:25](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=445s) And these, these signals really help identify how and who you should target and when. So, for example, if you have an exec sponsor at your current account and that individual is leaving the organization and moving into another account, and that company is not part of your list, given that you have this exec sponsor currently as your contact,

[7:50](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=470s) you ought to make sure that the company that they're moving to next is part of your account list, and they become your new exec sponsor, your champion in that organization.

[8:00](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=480s) That's the power of social signals, and it's very important that these are captured, and not many companies leverage this in a automated, systematic way, and I'll talk about how to, how to do that in just a second.

[8:12](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=492s) The second layer is that of buyer intelligence.

[8:15](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=495s) This is about making sure you have the right information about the buyer. It all starts with, for us, at least at Position² and we believe, uh, this is how it should be for a lot of organizations,

[8:28](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=508s) is through a knowledge base. A knowledge base is a repository of context that you have about your product, your buyers, the ICPs, the personas, the different titles, different playbooks, different criterias of success.

[8:46](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=526s) Everything that makes you successful sits in a knowledge base. It also has visitor identity information, de-anonymized information sitting in your buyer intelligence database. The ICP scoring. What defines a score?

[9:01](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=541s) Uh, uh, what score defines a fit, and w-what score defines a buying stage versus someone who's a research mode? All these are things you have to codify within your buyer intelligence system.

[9:13](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=553s) Then you have a context builder. All the signals that you have need to form a context graph that I'll talk about next.

[9:22](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=562s) And then you need to have a routing logic. This is where you would define what message goes to who when. So if someone were to e-engage with you on LinkedIn, do they get a LinkedIn outreach or do they get a email or should they be shown a ad?

[9:41](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=581s) Um, these are the insights or inputs that actually go as part of your routing logic.

[9:47](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=587s) The third layer is that of action. Once you have the signals and the information and the intelligence from the first two layers, now it's time for action, which basically means now you have...

[9:58](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=598s) when user lands on your, uh, page or your website, the chat window that popped up earlier that I talked about shouldn't ask generic questions like, "What can I help you with?

[10:09](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=609s) What are you looking for? What's your name?" That's not the communication at this point. The communication is personalized, and I'll show you an example of what I mean by that.

[10:16](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=616s) It needs to identify the user, address them by name,

[10:21](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=621s) and talk about where they potentially left off last time they were on your site. Or based on the intent signals, the chat needs to offer them specific content.

[10:31](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=631s) The action also based on these signals should be about sending the right alerts and information to the rep. Too many, you lose the, the rep, the sales rep, and too few, you're not helping them hit their, hit their numbers, um, and, and get revenue for the organization.

[10:52](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=652s) The third piece here is that of updating the CRM. The CRM system cannot just be an update about the contacts that the sales had. It needs to be about the context on-- A-about the account that the first two layers drive for you.

[11:09](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=669s) And finally, the sequence trigger. The actions need to determine what type of outreach sequence need to be sent out at what time. What outreach is triggered when to who.

[11:22](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=682s) Without all these three layers running in tandem,

[11:27](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=687s) the GTM model is still obsolete, is old school, and it's not set for the AI era that we are talking about.

[11:39](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=699s) And here's an example of context graph. All the signals we just talked about roll into this connected record, which is per buyer. The persona, account, and deal, these are all signals and actions that are logged for every touch point across the account for every single person.

[12:03](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=723s) A person's signals link to their account The accounts have multiple people in them, so the buying committee information surfaces for the account based on the signals coming by person and for each account.

[12:21](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=741s) Then you have deal-level information here, which is very specific to sales and marketing activities. So has sales and has marketing already reached out to this individual or people, the buying committee at this account?

[12:38](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=758s) And all these together, with all those signals and data points and touch points, become a context graph.

[12:46](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=766s) The reason why a context graph is important is because without it, you don't know which account is a priority and which one is not. And therefore, when you have this information, you're able to prioritize the high-intent accounts and contacts within those accounts for your sales team and marketing to pursue.

[13:08](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=788s) Now, having covered the architecture and the importance of a con-- a context graph, I want to walk you through

[13:17](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=797s) how we implement this architecture and what that flow looks like, followed by a quick demo of what our system shows us when it comes to all the details that I just talked about, and how our system helps us identify key accounts and key stakeholders that we need to reach out to.

[13:34](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=814s) This is how the three-layered architecture I just talked about looks like as connected agents. When a user lands on our site, at that moment, we don't know who they are.

[13:45](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=825s) They're anonymous. And that is when that visit kicks off the first job, which is the identification job.

[13:54](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=834s) And as you'll notice, I'm using more than one source here running together, and that's because no single tool catches every visitor.

[14:02](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=842s) We pull the information provided by these tools, consolidate them, and dedupe them, and send it over to the next layer, which is the enrichment phase.

[14:14](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=854s) These tools change all the time for us, but not necessarily the architecture as such.

[14:20](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=860s) Once these contacts are enriched, the next layer, which is the intelligence layer, kicks in.

[14:32](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=872s) Here you'll notice that our ICP filter agent kicks in, which is referencing information from the knowledge base. What this does at this stage is it's looking back at the knowledge base and making sure that the contacts that come in are part of the criteria we've defined in our knowledge base.

[14:54](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=894s) Anything that doesn't fit, such as wrong industry or wrong geo, wrong size, wrong persona, are weeded out.

[15:04](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=904s) Those contacts and information are, are deleted. What fits our criteria and what's relevant

[15:12](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=912s) moves into a clean table of qualified accounts.

[15:17](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=917s) After this, the match agent kicks in. It checks for people against our CRM. Have we talked to them? Are they warm? Are they hot? That's the evaluation that happens at this stage.

[15:32](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=932s) Finally, the action agent kicks in. This agent decides what happens next per person.

[15:42](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=942s) And this could include one person from an account, or if there's a buying committee, the actions are decided for the entire buying committee per account.

[15:56](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=956s) Here, the action agent decides different alerts that the sales reps have to get on Slack with the right context and a draft of an email that they can possibly send.

[16:10](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=970s) This agent also decides if an email has to be fired up and sent over to the contacts we have. It also decides if we need to use LinkedIn for an outreach.

[16:21](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=981s) And this is how the workflow works, from the three-layered architecture to how we implement GTM agents today at Position².

[16:34](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=994s) Now let me walk you through how the system actually looks in the back end. So we saw the three-layered architecture. We saw the agents working together. Now what does the output look like is what I'll show next.

[16:50](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1010s) Here's a view of our system at Position², which is called Intelligence.

[16:57](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1017s) What you see here is as soon as I land, the system is able to understand who I am, and I see a personalized message

[17:06](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1026s) coming up here as part of our chat interface.

[17:09](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1029s) Instead of just asking me generic questions, it's actually pointing me to one of the conversations that I had with it earlier and prompting me or asking me if I want to continue there.

[17:17](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1037s) And if I were to say yes, it pulls up a link or gives me a link here, which I can click on and go to the specific conversation that I was, uh, part of earlier.

[17:26](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1046s) What you see here is a culmination of all the signals, information, and all the data that we collected as part of the user that is reflected here in a chat.

[17:38](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1058s) So as opposed to having a generic greeting for me, this is more personalized.

[17:44](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1064s) Let me now take you to our internal dashboard

[17:49](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1069s) and show you how this data actually is projected to us when we look at the accounts that we

[17:58](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1078s) are pursuing. Here's a view of the interface that gets us into a dashboard. What you have here is two key sections that we have built. One is for GTM, the other is organic.

[18:09](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1089s) For our conversation today, I'll be walking you through what happens when we go to our GTM dashboard.

[18:16](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1096s) Once you enter the dashboard, what you see are multiple cards. And for the conversation today, I will be focusing on the anonymous visitors and the LinkedIn intelligence sections. What you see here is when I click on the anonymous visitors, it takes us to a dashboard where

[18:32](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1112s) the flow of agents and the architecture that I showed you earlier is de-anonymizing the users. It's identifying the users that come onto our website, and it's categorizing them into multiple sections.

[18:42](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1122s) What you see here is we have-- Our system has identified about three thousand odd people or visitors coming in from about two hundred and eighty different accounts. And the system tells us that information technology is one of the key verticals or key industries that's visiting our site.

[19:01](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1141s) And this is, in fact, one of the verticals that we focus on. What you also see is the industry breakdown as well as hot signals, and this is information of people

[19:10](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1150s) from different companies that are being categorized as hot contacts or hot accounts at this point. This is a combination of different signals, including the conversations that have happened within HubSpot.

[19:22](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1162s) For the sake of the conversation here, I have changed the names, although the titles are accurate. If I were to scroll down, I have more information about these users, about the contacts, the companies they belong to, the location, as well as the industry type.

[19:43](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1183s) All this information is, uh, or, or can be sorted. All this information can be sorted

[19:53](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1193s) based on industry, seniority, different types of engagements they've had with us,

[19:59](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1199s) and we can also look at the companies that visit our site.

[20:05](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1205s) The second part to this is if I were to go to the LinkedIn intelligence, and this is a part that many GTM teams miss. LinkedIn has a wealth of information that is very useful.

[20:17](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1217s) What you see here is over the last few days, about a hundred people visited our site through LinkedIn from seventy-three different companies, and they've engaged with eight different posts that we put out recently.

[20:30](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1230s) It has a list of all the folks that have engaged and the type of engagement they've had with us. We can actually sort them out by C-suite, VPs, directors, managers, and individual contributors.

[20:41](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1241s) Those are the categories that we use, and you have a list of companies where they belong to. By clicking on each of these, we can actually go into very specific details about their overall engagement with us.

[20:56](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1256s) This level of detail really helps us bring in the right level of intelligence into our system. Now that we have looked at the architecture, let me walk you through what does tend to break when it comes to building these types of systems, and I want to focus on four key areas.

[21:15](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1275s) The first is the ICP drift, and this is real. Your ICPs evolve over time. For example, today you focus on a twenty million dollar ARR organization from a sort of vertical, and if you were to close a fifty million dollar or a hundred million dollar ARR firm from a different vertical, then you might realize that that is

[21:31](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1291s) a new area for you to focus on and for you to pursue. And that information is critical to enter into your knowledge base. Without that, your agents are working off of the old information, always giving you wrong in- wrong data that you might not want.

[21:45](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1305s) What this means is you need to retrain your models, to retrain your agents every quarter

[21:53](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1313s) with your closed won or closed lost opportunities, and this is critical. Without this, your agents are looking at wrong information, pointing you to the wrong accounts and the wrong people.

[22:07](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1327s) The second point is alert fatigue. If everything is flagged as hot to a sales rep, they would stop acting because it's, it just gets overwhelming for them.

[22:21](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1341s) And at that moment, they stop trusting the system, and the system's dead.

[22:26](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1346s) So it's important to use the knowledge base and the context graph to cut through the noise and focus on the alerts.

[22:33](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1353s) Focus on alerts from the accounts and contacts that do actually matter for the salespeople to act upon.

[22:43](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1363s) The third item is identity ceiling, and this is a limit that exists with tools today. A lot of these platforms, when it comes to identifying the anonymous visitors, they're almost seventy percent, a little more than seventy percent accurate when it comes to company identification.

[23:01](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1381s) They're only about fifteen to twenty percent accurate when it comes to individual identification, and this is a structural limit and a structural issue with these systems. The only way to truly maximize this is to keep testing different systems till you hit on one that gives you a much better numbers than what you already have.

[23:22](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1402s) But most important thing here is to keep these metrics in mind as you plan your GTM outreach.

[23:30](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1410s) And finally, the human bottleneck. The minute the approval queue feels like a chore, it's going to become backlogged. It's going to be ignored, and the system is not gonna be trusted anymore.

[23:45](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1425s) What this means is you need to make sure that you shrink the friction between,

[23:52](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1432s) let's say, a draft email that's ready to be sent to that being sent. And what I mean is if your draft email is in a spot where it's almost ready to go with very minor edit,

[24:05](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1445s) and you're able to kick it out with just one click, then that's a system that's gonna sustain. But if the time taken to edit an email that the AI writes

[24:16](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1456s) is, let's say, longer than... We look at thirty seconds. If it's longer than thirty seconds- then this is a dead initiative because

[24:27](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1467s) the sales would then rather focus on drafting their own email as opposed to trusting what the system gives them. Finally, I want to leave you with four key takeaways.

[24:37](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1477s) One, you have to start with the identity.

[24:40](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1480s) Not being able to identify visitors who s- who land on your site

[24:45](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1485s) is as good as a dead GTM project. What you need is a system that's put in place, just like what I showed you earlier or something similar to that, that is robust enough to identify the visitors coming to your website

[24:58](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1498s) and has a feedback mechanism where that information is able to go back into your knowledge base and vice versa. The second is the score fit and intent needs to be looked at separately.

[25:09](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1509s) Conflating them is going to send the wrong message to the wrong person.

[25:14](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1514s) The third is you need to have a policy engine that is auditable and adjustable. What it means is you need to have a system where if it doesn't work, you have a way to audit which agent or what part of the workflow, for example, like the one that I just showed you, is broken and you have a

[25:32](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1532s) way to go fix it, as opposed to going after a developer to help you come fix it. So you need to build a system where, as a GTM leader or a GTM team member, you are able to control the system and fix it when needed, because things do break quite frequently when it comes to AI and managing

[25:50](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1550s) the output from AI. Finally, you need to let the flywheel compound. What I mean by that is every send, every reply, and every closed deal should make the model smarter, should make your system smarter.

[26:07](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1567s) What it means is any information about wins, losses, deferred sales, all that needs to go back into your knowledge base, and your agents need to be able to capture that information to make the right decision for the future.

[26:23](https://www.youtube.com/watch?v=ltv-L5oMPIs&t=1583s) That's all I have for you today. Thank you very much for your time
