Company Relationship as Data Unit
Bob Moore, CEO and co-founder of Crossbeam, on ecosystem-led growth
The key insight is that Crossbeam worked because it chose the company relationship as the core data unit, not the individual contact. Earlier lookalikes often tried to be a smarter LinkedIn for warm intros, which ran into LinkedIn’s existing network, weak repeatability, and the fact that a rep cannot force another company to share data. Crossbeam instead built around account overlap data that partner teams already control, then expanded that data into sales workflows.
-
The failed pattern was selling a relationship graph straight to sales. That sounds attractive because sales has budget, but the actual permissions and partner connections sit with business development and partnerships teams. Crossbeam spent its first years winning that persona first, which solved the cold start problem for the network.
-
The product is much closer to controlled account mapping than to a lead database. Companies connect CRM or warehouse data, compare customer and prospect lists with a partner, and choose whether to reveal only counts, account names, or richer fields by segment, geography, or use case. That makes the workflow operational and privacy manageable.
-
This category only became durable once the network got dense enough. By 2024, Crossbeam and Reveal together said more than 25,000 companies had adopted one of the two platforms for account mapping and partner data sharing, and the merger was explicitly about unifying a fragmented network into one larger graph.
The next phase is less about proving that partner teams need a tool, and more about making ecosystem data a standard input for sales and revenue software. As the unified Crossbeam network absorbs Reveal and pushes partner data into deal, forecasting, and AI workflows, the category moves from niche partner ops software toward core go-to-market infrastructure.