I think you're partly right. As you said in your first video, SAP likely want the code that allows WalkMe to create help for 3rd party web-based applications and the analytics that it provides. However, I don't think they will sell 3 separate products especially when you consider that they used to sell Desktop and Web Assistant as separate products with separate developer and end user client licences but simplified it when the cloud solution was introduced to sell just end user licences that allowed by creation and consumption. You also have to remember that the ability to access simulations and book pages from SAP Companion is integral to the solution. If clients want to activate SAP Companion without creating any specific in-app help content (like Guided Tours), they can use the simulations they've created without modification (as long as they've captured the context correctly, of course) as a way to deliver pre-go-live content in a post- go-live scenario. Especially useful in a scenario where time is of the essence. What's more likely is that the recognition provided SAP Companion when creating content may well work like Producer/Instant Producer in using the appropriate technology provided by Application Profiles to determine the best technology available to recognise the target application's UI. SAP web-based app = use XRay. Non-SAP web-based app = use WalkMe recognition. All this would happen in the familiar Companion Editing interface. The ability to create book pages, quizzes, etc in the Manager web editor coupled with the recently-added feature of being able to record web-browser applications with the Browser Application Recorder extension, probably indicates the true direction of Enable Now to make it purely web-based rather than needing the Producer and Instant Producer client components. The other thing to consider is that WalkMe is a cloud-only solution and there are still some Enable Now customers who need the on-premise version so there will also be a decision on how the WalkMe functionality can be integrated in this way to ensure that customer base is not lost.
Very interesting video, thanks. I agree there will probably be separate SKUs offered by SAP to appeal to different use cases. I would be delighted to see SEN be given a robust boost in functionality to rival Storyline. I'm most excited however about the time and cost saving that will be provided by WalkMe's DeepUI once it's fully integrated with SAP Companion as single powerful DAP. Finally, have you given any thought to whether SAP are looking to retain WalkMeX and how that might integrate with Joule?
SAP seems to be going all-in on Joule, so I think that will become the standard, and not WalkMeX. I know they see Joule being used to complete tasks for you instead of you needing to follow Guided Tours, so...
I think you're partly right. As you said in your first video, SAP likely want the code that allows WalkMe to create help for 3rd party web-based applications and the analytics that it provides.
However, I don't think they will sell 3 separate products especially when you consider that they used to sell Desktop and Web Assistant as separate products with separate developer and end user client licences but simplified it when the cloud solution was introduced to sell just end user licences that allowed by creation and consumption. You also have to remember that the ability to access simulations and book pages from SAP Companion is integral to the solution. If clients want to activate SAP Companion without creating any specific in-app help content (like Guided Tours), they can use the simulations they've created without modification (as long as they've captured the context correctly, of course) as a way to deliver pre-go-live content in a post- go-live scenario. Especially useful in a scenario where time is of the essence.
What's more likely is that the recognition provided SAP Companion when creating content may well work like Producer/Instant Producer in using the appropriate technology provided by Application Profiles to determine the best technology available to recognise the target application's UI. SAP web-based app = use XRay. Non-SAP web-based app = use WalkMe recognition. All this would happen in the familiar Companion Editing interface. The ability to create book pages, quizzes, etc in the Manager web editor coupled with the recently-added feature of being able to record web-browser applications with the Browser Application Recorder extension, probably indicates the true direction of Enable Now to make it purely web-based rather than needing the Producer and Instant Producer client components.
The other thing to consider is that WalkMe is a cloud-only solution and there are still some Enable Now customers who need the on-premise version so there will also be a decision on how the WalkMe functionality can be integrated in this way to ensure that customer base is not lost.
Very useful! Thank you for your research on this topic and for sharing it so clearly.
Agree with you about building out Enable Now's courseware component. Maybe we'll finally get the ability to add a dotted line! haha.
Ha! If they add that and the ability to rotate text, I'll consider it a MAJOR upgrade!
Very interesting video, thanks. I agree there will probably be separate SKUs offered by SAP to appeal to different use cases. I would be delighted to see SEN be given a robust boost in functionality to rival Storyline. I'm most excited however about the time and cost saving that will be provided by WalkMe's DeepUI once it's fully integrated with SAP Companion as single powerful DAP. Finally, have you given any thought to whether SAP are looking to retain WalkMeX and how that might integrate with Joule?
SAP seems to be going all-in on Joule, so I think that will become the standard, and not WalkMeX. I know they see Joule being used to complete tasks for you instead of you needing to follow Guided Tours, so...
@@EnableNowExpert Thanks Dirk, that makes total sense. We live in interesting times for sure.