HockeyStack raises $50M to expand its enterprise “Revenue Agents” platform
HockeyStack raised $50M to expand enterprise Revenue Agents, pushing revenue intelligence toward AI-driven execution across prospecting and expansion.
HockeyStack has raised $50 million and launched its “Revenue Agents for the Enterprise,” positioning the product as an AI agent layer for prospecting, new business, and account expansion. The company says the funding brings total capital raised to over $50 million, and it has scaled to over 300 customers in less than two years.
For enterprise marketing and revenue leaders, this announcement is less about yet another AI feature and more about a specific bet: shifting from dashboards and attribution reports to systems that take action inside revenue workflows.
Short on time?
Here’s a quick look at what’s inside:
- What HockeyStack is building with Revenue Agents
- Why event-based data architecture matters for revenue teams
- How HockeyStack compares with Dreamdata, 6sense, Clari and Demandbase
- What enterprise marketers should pressure-test before adopting agents
What HockeyStack is building with Revenue Agents
HockeyStack started as a B2B revenue intelligence and attribution platform, aggregating data from CRM, marketing, sales, and product systems to map the buyer journey. The new layer is “Revenue Agents,” which are intended to operate continuously against deals and accounts.
The company describes a few key building blocks:
- Blueprints, proprietary machine learning models that extract “institutional knowledge” from structured and unstructured enterprise data, tailored to a specific revenue motion, segment, or business unit.
- Deal- and account-assigned agents that make decisions, execute actions, and engage sales reps at relevant moments.
- Manager views for coaching and pipeline forecasting.
This moves the product from “tell me what happened” (analytics) to “help me do what to do next” (execution). For marketers, the natural intersection is account-based motion: how intent, engagement, and pipeline signals translate into next-best actions across SDRs, AEs, and lifecycle campaigns.
ContentGrip
Why event-based data architecture matters for revenue teams
HockeyStack frames its differentiation around replacing traditional CRM “object-and-field” models with an event-based data architecture. The underlying idea is that modern go-to-market teams generate signals everywhere (product usage, website activity, email, ads, calls, trials), and rigid CRM schemas often lag behind reality.
If an event layer is implemented well, it can improve:
- Attribution fidelity (more granular touchpoints and sequences),
- Time-to-insight (less custom reporting for every new motion),
- and agent effectiveness (agents need clean, timely event streams to act safely).
The trade-off is operational complexity. Event-based systems can create governance questions quickly: who owns event definitions, how identity resolution is handled, and how to prevent “automation drift” when data quality degrades.
How HockeyStack compares with Dreamdata, 6sense, Clari and Demandbase
HockeyStack operates in a competitive B2B revenue intelligence and attribution landscape, alongside platforms like Dreamdata, 6sense, Clari, and Demandbase.
Where it appears to compete or differentiate:
- Versus attribution-first platforms (e.g., Dreamdata): HockeyStack is pushing beyond reporting into agentic execution tied to accounts and deals.
- Versus ABM and intent platforms (e.g., 6sense, Demandbase): those systems often center on targeting and account selection, while HockeyStack is positioning around end-to-end revenue workflow and the system that learns from closed deals.
- Versus forecasting and pipeline governance tools (e.g., Clari): HockeyStack’s agent framing implies more automation at the edge of execution, not just inspection and forecasting.
The category remains crowded, and enterprise buyers will likely judge HockeyStack on how quickly it can integrate with existing systems, plus whether its “Blueprint” models can be audited and tailored without requiring heavy services work.
What enterprise marketers should pressure-test before adopting agents
If you are considering Revenue Agents-style platforms, a few practical checks can reduce adoption risk:
- Start with one bounded use case (e.g., expansion plays for a single segment) and define success metrics that reflect revenue outcomes, not activity volume.
- Ask how the system learns from wins and losses: what inputs update the model, and how frequently are changes reviewed?
- Clarify human control points: which actions can the agent execute automatically vs. recommend, and what approvals are required?
- Validate data dependencies: identity resolution, CRM hygiene, stage definitions, and campaign taxonomy can determine whether the agent is helpful or noisy.
HockeyStack cites adoption signals including over 300 customers and use by Fortune 100 revenue teams, and it lists customers such as Firstup, DataRobot, Airbyte, Yext, and 8x8. Those logos can indicate category fit, but your team’s readiness will still come down to data quality and process clarity.
