Kepion Planning

Well-suited: Migrating from planning in Excel, scenarios when multiple users are involved in the planning process, scenarios where there is a commitment to improve the planning process and accuracy.

Less appropriate: Where users are looking for a lower-overhead, more visual, less-connected solution.

• Customizable platform: Enables its users to handle just about any kind of budgeting scenarios tailored to each customer needs, whether based on drivers, allocations integrations with other systems (such as S&OP processes).
• Easy integration with other systems: As data is stored within an MS SQL database it is very easy to integrate other applications with it for reporting, such as Tableau or PowerBI or from other downline systems such as S&OP.
• Real-time: Enables the possibility to calculate bottom line results for all applications immediately allowing the possibility to calculate easily what-if scenarios.
• Not stuck: within a single way of budgeting. as part of the beyond budgeting movement, companies have been creating a more driver-based high-level forecasting which is often a problem with specific budgeting systems that are locked within the P&L statement. Here you can make it as simple or as complicated as needed.

• Interface: The interface is built in Silverlight, so is a little clunky and inflexible. Kepion are, however, planning to launch a HTML5 version in March 2018, which will greatly enhance the product.
• Visualisation: We usually use Kepion for data entry and deep analysis, and then leverage tools like Power BI or Tableau to visualise data or create aggregated management reports.

We are a Microsoft gold analytics partner. As such, we were looking for a Microsoft friendly solution which would fit into our analytics stack with Tableau on top. Kepion is a lightweight easy to use solution which integrates perfectly with the Microsoft framework. It is much easier to use and intuitive than the heavy Cognos and SAP/BO systems. However, if my existing infrastructure is Cognos, SAP or Oracle I would consider using that technology. For Microsoft SQL companies this is a great choice.