Embedded analytics are the future, but you already know that.
So once you decide to embed, the question becomes how deeply you want to embed those analytics.
The decision will affect your precious internal resources. Embed too deeply at the beginning, and your developers might be overtaxed on analytics and incapable of focusing on improving your core product. Don’t embed deep enough and you may not grow your total addressable market or offer enough value to up-charge customers.
Choosing the right level of embedding is a company-specific choice, and there are many factors companies must consider.
- What solutions are my competitors offering?
- What is the market appetite for paying a premium for analytics?
- How many resources do I want to commit internally?
- What capabilities do I really want to offer?
The answers to these questions are found in the embedded analytics maturity model. The model is the foundation on which embedded analytics is devised, and helps establish a baseline of expected capabilities, effort and features at each increasingly complex level of maturity.
So as you begin to embed and consider your existing analytics solutions, I hope you can join me for my BI Inside session at the #Logi16 User Conference. This session will help you develop an appropriate embedding strategy for your business – we’ll discuss each stage of the Embedded Analytics Maturity Model, and demonstrate the actual effort, requirements and output achieved by embedding at each level.
At the conclusion of the session, you’ll understand what is actually required from your team to embed at each level and how that experience will translate to your customers. Hope to see you there!
#Logi16 is taking place October 12-13, 2016 at the Ronald Reagan Building and International Trade Center in Washington, DC.