# Henry Schuck

Henry Schuck writes about go-to-market data and AI. Schuck argues that AI agents need connected, accurate company records—including account relationships and business history—and has announced ZoomInfo’s Agent Teams for go-to-market work.

- Profile: https://b2binfluencer.marketing/creators/henry-schuck/
- LinkedIn: https://www.linkedin.com/in/hschuck
- LinkedIn followers: 102,912
- Topics: artificial-intelligence
- Based on 10 dated posts, latest 2026-10-07

## Summary

Henry Schuck is most useful for explaining why AI sales workflows need reliable company records and context.

- Best for: B2B SaaS brands helping sales and marketing teams prepare data for AI agents.
- Not for: Consumer lifestyle brands seeking broad awareness or light entertainment endorsements.
- Check first: Before contacting them, confirm sponsorship terms, audience breakdown and performance evidence.

### Takeaways

- Duplicate Cisco records can make an AI agent confuse companies.
- Missing subsidiary relationships can send a discount for non-customers to existing customers.
- Agent Teams are presented as a way to bring AI workflows to a whole sales team.

## Main ideas

- **AI go-to-market workflows break on the data underneath them; the fixes come in a set order**: Schuck argues that model capability is the wrong place to look when AI sales and marketing workflows disappoint. The requirements they name are entity resolution, so the system knows which of several similarly named records is the real account; hierarchy resolution, so subsidiaries roll up under parents; first- and third-party data — calls, emails, product usage, opportunity history — stitched to the correctly resolved account; and metadata a model can read, described with Palantir's term "ontology." The reasoning is that an agent only acts on records as they are stored, so an unresolved or drifting record produces a confident wrong answer at every step downstream. They contrast this with what they call exhausting acronym churn: MCPs, CLIs, RAG, A2A.
- **GTM context is the layer beneath AI, and owning it is the next vendor battleground**: Schuck picks up the phrase "GTM context" from analyst Adam Schoenfeld, whose argument Schuck credits and quotes (the phrase is Schoenfeld's; the extensions below are Schuck's). Schuck's claim is that the next era is won not by whoever builds the most sophisticated campaign or demand workbook but by whoever builds and owns the connected context that people and agents then run motions on top of. Companies assume that picture already lives in the CRM, and in Schuck's account the CRM is a mess: hierarchies, subsidiaries, employment histories, and rebrands change faster than stored records, and no amount of inference invents those links without a reference dataset. The proposed layer is a "context graph" connecting entities, history, and activity. Schuck then draws an analogy — every function running on AI needs such a layer — and names each function's incumbent before naming go-to-market's.
- **Agentic workflows only count once the whole team can run them, not just the engineer who built them**: Schuck starts from an observation about the impressive Claude-built go-to-market workflows of the past year: dump in CRM notes, call transcripts, emails, and account data, and out comes a near-perfect account plan with who matters, what changed, what to do next, and what to say. The problem, in their words, is that such a workflow has "a user base of one": usually the go-to-market engineer who built it, while everyone else keeps digging through Salesforce and starting from scratch. Their priority is the reliability of a workflow combined with the judgment of a team, delivered to every rep rather than to its author.

## Work to read

- [GTM context is the new vendor battleground](https://www.linkedin.com/posts/hschuck_adam-schoenfeld-recently-called-gtm-context-activity-7513532467547418626-Qaqu)
- [Most AI workflows in GTM produce garbage](https://www.linkedin.com/posts/hschuck_most-ai-workflows-in-gtm-produce-garbage-activity-7510325861267660800-Smeb)
- [Announcing Agent Teams for GTM, built on DoubleO’s agentic technology](https://www.linkedin.com/posts/hschuck_yesterday-zoominfo-announced-the-acquisition-activity-7511425552684109824-qWJT)

## Brand relationships

- **ZoomInfo** (disclosed_partnership)
- **DoubleO AI** (mention)

## Partnerships

Henry Schuck's three posts in scope cover product and company announcements: the launch of ZoomInfo Agent Teams for go-to-market work, GTM data context and entity resolution, and account hierarchy and CRM data quality. They do not describe sponsored placements or disclosed brand collaborations. No official sponsorship policy, rate structure, audience specification, or partnership inquiry route appears in the posts. Buyers should request first-party confirmation of partnership terms before proceeding.

## Alternatives

- Florin Tatulea: Pick Tatulea when the campaign wants the data-readiness argument from someone running ABM programs, not an executive at a data vendor. The posts describe ABM plays scaled past $1.2bn and set out four layers a team needs in one place: a named account list, the named buyers at each account, signals that predict conversion, and the existing context on each account. They also warn that an agent chains steps, so a wrong field at step one becomes the assumption every later step builds on. That practitioner framing suits a hands-on workshop, a diagnostic session, or a peer case discussion for sales and RevOps teams more than a product-led message, and fits the same GTM data-foundation brief.
- Chuck Robbins: Consider Robbins when the need shifts from data hygiene to enterprise AI infrastructure: national-scale AI programs, sovereign security operations, workforce training commitments, and audiences in senior technology, government, and service-provider roles. The posts cover AI infrastructure and partnership work in India and Indonesia, including an AI Center of Excellence with IOH, NVIDIA and the communications ministry, a sovereign security operations platform using Splunk and managed services, a research partnership with the national innovation agency, and a training goal of 500,000 more students by 2030. They also cover meetings with connectivity providers at MWC Barcelona and government discussions in Switzerland and Italy. That suits an awareness or thought-leadership campaign about deploying AI infrastructure at scale with public and institutional partners.
- Maxime Champoux: Choose Champoux when the campaign should show an operator building a GTM data engine from scratch rather than an executive explaining why the problem matters. The posts document the build in specifics: 46 features a month against 7 at the start, a go-to-market engine processing 3.4 million signals and scoring more than 1,600 leads across three tiers, and a context graph that connects the tools a business already uses and deploys agents to capture, enrich, reconcile and act on the data. That fits a founder-to-founder or build-in-public angle about assembling GTM data infrastructure, or a startup finance and operations context around automating invoices, receipts, and financial questions.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/