What part of a sales ops team's workflow does Roster replace?

The core problem that we're solving is around lack of internal visibility into who is doing what, when they're doing it, and what behaviors actually move the needle. If you don't do that properly, there are pretty profound consequences - lost revenue and efficiency. You can't improve what you can’t see in the first place. Our product, at its core, is data aggregation. We're pulling event logs across a pretty disparate  sales tech stack, like Salesforce, Gong, and Salesloft.

Event logs means event streams of user actions and behavior. Behaviors can include a Sales Manager frequently listening to their reps’ calls in Gong, or reps sending post-call recap emails in a timely manner. Tying these timestamped behaviors to a business process can be a path. For instance, a deal advancement path can include having a demo, engaging a Sales Engineer, updating the opportunity notes, launching this email sequence and making some personalized changes to the email before sending it off. We want to contextualize users’ workflows across fragmented  tools, and piece it together so that it's apples-to-apples.

At the very core, what we're building is data aggregation. It’s a really gnarly data modeling problem. We're mapping events with business processes, and then tying that to outcomes. Creating a universal event log is a really tough mapping categorization problem to crack.