Erol Toker’s Post

View profile for Erol Toker, graphic

Solo Capitalist 🧐 | Building World's Most Efficient SaaS Portfolio | Daily Content

Key takeaway from a great conversation I had with a RevOps leader today: 1) RevOps is a product/engineering function. Many don't feel that way because they 'integrate lots of other products'. Guess what product managers and engineers do :). They use libraries from Github, servers from AWS, payments through stripe, text messages through Twilio, etc. This is no different than trying to figure out how to unify the sales/marketing/success stack. 2) If data is the new oil because it drives better product experiences, customer data hubs (CRM, etc) are now part of the product. Every unit of data that sales gets in the sales process should influence the experience that the user has while onboarding and using the product. Every new insight that an AM gets during a QBR should flow into the marketing and product education that the prospect gets. 3) There is a big talent gap in the RevOps space. Because companies haven't viewed this as being about 'building software', they haven't hired and developed the role definitions, culture, etc of software teams. Because of point #2 above, that now HAS to change. #ceoDoesSales

Nick Bonfiglio

CEO of Syncari, former EVP of Product and Engineering @Marketo, and author

4y

We also see #revops as the stewards for business data across the org. The advantage here is that since data is indeed the new oil, we need refineries, like Syncari, to ensure the proper data octane is achieved to fuel your business. ;)

Like
Reply

To view or add a comment, sign in

Explore topics