Skip to content

Sales Blueprint

Safety checked

Launch G2 Buyer Intent Campaigns End to End

mchen-gtmJuly 2026

Seven independent AI workflows that turn G2 Buyer Intent signals into campaign-ready assets for prospecting, scoring, nurture, retention, intelligence, and paid media.

Intent-Driven OutboundIntent-Enriched Account ScoringLinkedIn Retargeting & NurtureRetention & Churn ReductionCompetitive IntelligenceGoogle Ads Intent TargetingMulti-Provider High-Intent Targeting

Install Command

Run this command to deploy the blueprint to your environment.

What problem does this solve?

Runs your full motion from intent signal to campaign execution without building integrations. Each workflow pulls live G2 data, composes shared core skills (data retrieval, CRM bridge, enrichment, drafting), and delivers ready-to-use assets ranked and ready for approval. Outputs include prospecting briefings, scored pipelines, audience lists, churn alerts, competitive digests, and paid-media packages. Because every workflow shares the same data layer and CRM bridge, swapping intent sources, CRM platforms, or enrichment providers requires config changes, not skill rewrites.

How does it work?

Set up once: connect G2 as an MCP server, declare your CRM (Salesforce or HubSpot), and configure product slug, ICP, and competitors in config.yaml. Then activate any workflow on its cadence (daily, weekly, or on demand). Each run begins with a preflight check that inventories your connected tools, proceeds or degrades gracefully. Outputs land in Slack, your CRM, and/or CSV files ready for upload to ad platforms. 1. Prospecting teams run intent-driven outbound daily for ranked briefings with drafted outreach. 2. Revenue leadership runs account scoring weekly to tier the pipeline by G2 intent. 3. Demand-gen runs retargeting and paid-media workflows weekly to feed LinkedIn and Google Ads with fresh audiences. 4. CSMs run churn-monitor daily for same-day alerts on at-risk renewals. 5. Product marketing runs the competitive digest weekly for leadership strategy. All workflows share the same signal source and core execution layer, so changes to data handling or CRM fields propagate across the suite.

Included Skill Groups

What's the biggest win?

Signal-to-send in hours instead of days, because intent flows directly to drafts and audiences without manual extraction or reformatting.

What should I know technically?

Each workflow is an orchestration over four shared core skills: g2-intent-data (normalizes G2 MCP queries), crm-bridge (adapts to Salesforce, HubSpot, CSV, or none), contact-enrichment (resolves companies to named contacts), and outreach-drafting (owns message generation and GDPR gating). Workflows are markdown instructions (SKILL.md) for any AI agent that can call MCP tools and read/write files. All workflows respect GDPR regional caps and consent state, drop consumer/ISP domains before anything else, ignore signals older than 14 days, and skip accounts with open opps or recent rep touches. Config.yaml is single source of truth for stack choices and per-use-case parameters (universe, score floor, ICP, competitors, thresholds).

What should I watch out for?

G2 Buyer Intent subscription (with comparison signals for full feature use) is the required data source; workflows stop without it. CRM connection strongly recommended for most workflows to prevent cold-touching existing customers or accounts with open opps. Enrichment providers (ZoomInfo, Apollo, Sales Navigator) are optional but required for contact-level deliverables (email drafts, match lists); without them, assets are flagged 'needs contacts' with suggested searches. Second intent providers for WF7 can be connected as MCP servers or provided as weekly CSV exports; no integration build needed.

Key Features

Seven independent workflows

Each solves one motion: outbound prospecting, pipeline scoring, retargeting, churn detection, competitive intelligence, Google Ads targeting, and multi-source triangulation. Run any, all, or in sequence.

Shared core layer

G2 intent data retrieval, CRM sync, contact enrichment, and message drafting are single implementations used by all workflows. Swap a CRM platform or enrichment tool in config.yaml; all workflows inherit the change.

MCP-native architecture

No custom integrations: declare your tools as MCP servers in your AI agent platform once (Claude.ai, Claude Code, Codex). Workflows discover and adapt to what you've connected.

Preflight and graceful degradation

Each run inventories available tools, proceeds with what's available, skips what's missing (flagged in output), or stops only when the core data source is absent. No silent failures.

Human approval gates

Nothing goes to a prospect, customer, or live campaign without manual approval. Drafts, lists, and plays are assets for human judgment.

Tools in this Blueprint

G2 Buyer Intent MCP
HubSpot Sales Hub logo
HubSpot Sales HubView on G2 ↗
4.4(13,215 reviews)
Slack logo
4.5(37,364 reviews)
GTM Studio - Powered by ZoomInfo logo
GTM Studio - Powered by ZoomInfoView on G2 ↗
4.5(3,395 reviews)

About This Blueprint

Industry
B2B SaaS
Skills
7 workflows, 4 sub-skills, 0 standalone