We’re here today to discuss a story, one that may cause confusion, chaos and disruption to the RevOps world. Doug’s a bit hesitant to share this story with us because while using client stories as examples, because it’s real life experience, he does try to keep it completely anonymous (which he is going to continue to do). The movement to RevOps has created hype and as he looks at everyone talking about revenue operations, one of the things more often than not that’s the question to answer is, what is RevOps NOT responsible for?
Today's episode will answer questions on a client that shouldn't have a focus of RevOps...at least not yet. You'll get to learn answers to:
- When is revenue operations the wrong focus?
- If their problem is not a RevOps problem, what is it?
- What is a lack of force problem?
- What are the things you need to do for the problem to be RevOps?
- What should this company do?
If you're liking the show, please make sure to subscribe and share it with your friends and/or coworkers. Follow us on Twitter: @dougdavidoff, @JessDCardenas & @demandcreator to receive updates on when new episodes publish or to get other great insights. You can also watch the video version of the show on our page. Thanks for watching and remember you can't solve your upstream problems, downstream.