Moving Reporting, Budgeting, and Forecasting Out of Excel with Limelight
Use Cases and Deployment Scope
We use Limelight for reporting, budgeting, and forecasting. We were previously doing much of this in Excel. Limelight has helped reduce user error in entry and in version control. It's also helped us increase the speed at which we can update forecasts, as the consolidation of templates will happen automatically after a user clicks save.
Pros
- Agile reporting
- Collaborative forecasting and budgeting
- Up to date reporting with GL integration
Cons
- Complex template speed
- Customer service response - was good initially, but has become worse recently
- Formatting options in charts
Likelihood to Recommend
Limelight is well suited for reporting, especially if you're GL is integrated with it. I've been able to create many different types of reports for a wide user base. It's easy to copy reports and change them based on different scenarios.
Limelight has been great as a replacement for Excel for forecasting and budgeting. We have many users updating their individual forecasts, which then get consolidated. Previously, we would have to manually consolidated many Excel workbooks. Now this is done automatically by Limelight.
Limelight struggles with processing speed if you create more complex reports/templates. I've asked how to speed up reports and most of the response is to make them less complex or have less people using the templates, neither of which work well for us as a solution.
The help desk response use to be much better in the past. They have struggled in this area recently.
