One post tagged with "data-infrastructure"

I want to tell you about the hardest problem in B2B sales technology. It's not lead generation — we solved that years ago (arguably too well, which is its own problem). It's not personalization — LLMs made that almost trivially easy. It's not even multi-channel orchestration, although that's closer.

The hardest problem is intent signal orchestration: ingesting signals from dozens of sources, prioritizing them in real time, and activating the right response before the buying window closes.

Every serious GTM team talks about being "signal-based." Very few actually are. And the current crop of AI sales agents — the open source repos making the rounds on GitHub and Twitter — reveal exactly why.

What Intent Signal Orchestration Actually Means​

Let me define the term precisely, because it gets thrown around loosely.

Intent signal orchestration is a three-stage process:

Stage 1: Ingestion. Capturing buying signals from every relevant source. This includes:

• Website visitor behavior (page views, time on site, content consumed, pricing page visits)
• CRM engagement history (email opens, link clicks, meeting bookings, deal stage changes)
• Third-party intent data (research topics, content consumption patterns, review site activity)
• Technographic signals (new tool adoptions, contract renewals, tech stack changes)
• Job change signals (champions leaving, new decision-makers hired, team restructuring)
• Social signals (LinkedIn engagement, conference attendance, content sharing)
• Firmographic triggers (funding rounds, acquisitions, office expansions, hiring surges)

Stage 2: Prioritization. Not all signals are equal. A pricing page visit from a company that matches your ICP and has an open opportunity in your CRM is dramatically more valuable than a blog post view from a random domain. Prioritization requires:

• Signal scoring based on historical conversion data
• Account-level aggregation (combining multiple weak signals into a strong composite signal)
• Temporal weighting (recent signals matter more than old ones)
• Deduplication and noise filtering (bot traffic, internal visits, competitor research)
• ICP matching and enrichment
• Cross-referencing against existing pipeline to identify acceleration vs. net-new opportunities

Stage 3: Activation. Converting a prioritized signal into an action within the buying window. This means:

• Routing the signal to the right rep or sequence based on territory, account ownership, or round-robin rules
• Triggering the appropriate response (email, call, LinkedIn touch, content share) based on signal type and strength
• Personalizing the outreach based on the specific signal and account context
• Executing through deliverability-safe channels with proper throttling
• Logging the action and creating a feedback loop for future signal scoring

This three-stage pipeline — ingest, prioritize, activate — is intent signal orchestration. Every stage is hard. Doing all three in real time, reliably, at scale? That's where almost everyone fails.

The Prompt-Based Orchestration Fallacy​

Here's where the current AI agent movement runs into a wall.

I recently examined a popular GTM agent repo — 92 agents, 67 Claude Code plugins, covering the full GTM spectrum. It includes an agent called something like "intent-signal-orchestration." Sounds perfect, right?

Open it up. It's a prompt. A well-written prompt, but a prompt. It instructs an LLM to "analyze intent signals and prioritize accounts for outreach based on buying stage and signal strength."

Think about what's missing:

There's no actual signal data. The prompt assumes signals will be provided as input. But where do the signals come from? The agent doesn't have a JavaScript pixel on anyone's website. It doesn't have access to Bombora or G2 buyer intent feeds. It doesn't know who visited your pricing page at 2 AM. It doesn't track job changes on LinkedIn.

The prompt is an analytical engine with no fuel.

There's no real-time data pipeline. Intent signals are perishable. A pricing page visit from 3 hours ago is an urgent buying signal. The same visit from 3 weeks ago is a data point. Orchestration requires real-time (or near-real-time) data ingestion — webhooks, streaming APIs, event-driven architectures. A prompt that runs when a human triggers it isn't real-time orchestration. It's batch analysis with extra steps.

There's no historical scoring model. Effective signal prioritization requires training on your own conversion data. Which signals in your business actually correlate with closed-won deals? A prompt can apply generic heuristics ("pricing page visits are high intent"), but it can't learn from your specific win/loss patterns unless it has access to your historical CRM data — enriched with signal attribution.

There's no activation infrastructure. Even if the prompt perfectly prioritizes accounts, what happens next? Someone has to copy the output, switch to their sequencing tool, find the contacts, build a sequence, and hit send. The gap between "AI recommends" and "rep executes" is where urgency goes to die.

This is the prompt-based orchestration fallacy: the belief that intelligence alone can solve an infrastructure problem. It can't. Intelligence without data is guessing. Intelligence without infrastructure is advising. Neither is orchestrating.

Why Infrastructure Beats Intelligence (For Now)​

I realize this is a counterintuitive claim in the age of AI, so let me be specific.

Consider two hypothetical sales teams:

Team A has a brilliant AI agent that can analyze intent signals with PhD-level sophistication. But it only gets data when a rep manually exports their CRM and pastes it into a prompt. The agent has no access to website visitor data, no third-party intent feeds, and no way to execute outreach.

Team B has a relatively simple rules-based system (if pricing page visit + ICP match, trigger high-priority sequence). But it has real-time website visitor identification, direct CRM integration, automated sequence execution through deliverability-safe email infrastructure, and an integrated dialer.

Team B will outperform Team A every time. Not because their intelligence is better — it's objectively worse. But because they can see the signal, act on the signal, and execute the response within the buying window.

Infrastructure creates the floor. Intelligence raises the ceiling. But you need the floor first.

The Three Types of Intent Signals (and Why Most Teams Only Capture One)​

There's a hierarchy of intent signals that most sales teams don't think about clearly:

First-Party Signals (Highest Value, Hardest to Capture)​

These come from your own properties: website visits, product usage, email engagement, chatbot conversations, content downloads, webinar attendance.

First-party signals are the most valuable because they represent direct engagement with your brand. When someone visits your pricing page, they're not doing generic research — they're evaluating you specifically.

But capturing first-party signals requires infrastructure:

• Website visitor identification technology that de-anonymizes traffic
• Event tracking across your web properties
• CRM integration that connects web behavior to account and contact records
• Real-time processing that surfaces signals while they're still actionable

This is where platforms like MarketBetter differentiate — they provide the actual visitor identification and behavioral data capture infrastructure that turns anonymous website traffic into actionable signals. No prompt can replicate this. It requires JavaScript pixels, IP resolution, cookie management, and data processing pipelines.

Second-Party Signals (High Value, Available via Partners)​

These come from platforms where your prospects engage: review sites (G2, TrustRadius), publisher networks, event platforms, communities. A prospect comparing you to a competitor on G2 is an extremely high-intent signal.

Second-party signals require data partnerships and API integrations. They're available as commercial products (Bombora, G2 Buyer Intent, TrustRadius Intent), but they're not free and they're not accessible to open source agents.

Third-Party Signals (Lower Value, Widely Available)​

These come from broader market data: hiring trends, funding announcements, technology adoptions, news mentions, social media activity. They indicate general market interest or company change, but don't necessarily signal intent to buy your product.

Third-party signals are the easiest to access — many are available through public APIs. This is why most AI agent frameworks focus here. They can scrape LinkedIn for job changes and Crunchbase for funding rounds. But third-party signals alone are noisy. Without first-party signals to anchor them, you're guessing about intent rather than observing it.

The teams that win at signal-based selling capture all three layers and weight them appropriately. First-party signals trigger immediate action. Second-party signals accelerate existing pipeline. Third-party signals inform targeting and timing for net-new outbound.

Building a Real Signal Orchestration Stack​

If you're building (or buying) a signal orchestration capability, here's the architecture that actually works:

Layer 1: Signal Capture​

You need persistent, always-on infrastructure that captures signals without human intervention:

• Website pixel that identifies companies and (where possible) individuals visiting your site
• CRM webhooks that fire on deal stage changes, email engagement, and activity updates
• Intent data feeds that deliver third-party signals via API or file transfer
• Job change monitoring that tracks your champion network across companies
• Enrichment on ingestion that appends firmographic, technographic, and contact data to every signal

Layer 2: Signal Processing​

Raw signals need to be cleaned, scored, and aggregated:

• Deduplication to prevent the same signal from triggering multiple actions
• Scoring based on signal type, source, recency, and historical conversion correlation
• Account-level aggregation that combines multiple signals into a composite account score
• ICP matching that filters out signals from companies that don't match your target profile
• Pipeline awareness that distinguishes "new opportunity" signals from "existing deal acceleration" signals

This is where AI adds genuine value. An LLM can synthesize multiple weak signals into a nuanced account assessment that a rules-based system would miss. The key is that the AI needs structured, clean signal data as input — not raw noise.

Layer 3: Signal Activation​

The scored, prioritized signals need to reach a human (or an automated workflow) fast enough to act:

• Real-time routing to account owners or round-robin queues
• Playbook generation that recommends specific actions based on signal type and strength
• Sequence triggering that automatically enrolls high-priority signals into appropriate outreach sequences
• Multi-channel execution that coordinates email, phone, and social touches
• Feedback capture that records outcomes (reply, meeting booked, closed-won) and feeds back into the scoring model

Layer 4: Learning Loop​

The system gets smarter over time:

• Attribution tracking that connects signals to pipeline and revenue outcomes
• Scoring model updates based on which signals actually correlate with conversion
• Sequence optimization based on which messaging and channel combinations work for each signal type
• Threshold adjustment that tunes the sensitivity of signal detection based on false positive rates

Why This Matters Now​

The timing of the GTM agent movement is significant. It's emerging at exactly the moment when:

1. LLMs are good enough to handle the analytical layer of signal orchestration — scoring, synthesis, personalization, recommendation.
2. Intent data is more available than ever — the number of signal sources and the richness of the data have exploded.
3. Email deliverability is getting harder — making signal-based targeting (reaching the right people at the right time) more important than ever.
4. Buyer behavior has shifted — prospects do 70%+ of their research before engaging sales, which means the signals they leave during that research phase are the most valuable asset in B2B selling.

The convergence creates both an enormous opportunity and a dangerous trap. The opportunity: teams that nail signal orchestration will have a structural advantage in pipeline generation and conversion. The trap: teams that confuse "AI agent that talks about signals" with "infrastructure that captures and activates signals" will waste time building on a foundation that doesn't exist.

The Uncomfortable Question​

Here's the question every revenue leader should be asking right now:

When a high-intent prospect visits your website at 10 PM on a Tuesday, what happens?

If the answer is "nothing, until a rep notices tomorrow" — you don't have signal orchestration. You have data collection with a 12-hour delay that kills half the buying windows you capture.

If the answer is "they're automatically identified, scored, enriched, and queued in a rep's morning playbook with personalized outreach recommendations" — you're in the game.

If the answer is "we're going to build that with an open source AI agent" — I'd love to know how you plan to identify the visitor.

Because that's the part no prompt can solve.

---

MarketBetter captures first-party intent signals — real website visitors, real behavioral data — and turns them into prioritized, actionable pipeline through an integrated daily playbook. See how signal orchestration actually works at marketbetter.ai.