Oivalo Planning
Oivalo Planning
Oivalo Planning is a enterprise level cloud‑based planning tool designed for budgeting, forecasting or any kind of data harvest.
With fully customizable logic it combines operational data and finance data into the same model, allowing organizations to see the financial impact of business decisions immediately.
Typical use cases include:
- Annual Budgeting and Forecast
- Multiple versions, Rolling forecasts, Actual + Budget planning
- Distributed driver based planning across large organizations
- Multi‑currency and multi‑language environments
Oivalo Planning is for you if…
The current budgeting process is heavy
If your budgeting model still lives in Spreadsheets, you’ve probably hit the point where it’s no longer flexible enough. Handling different budget versions, updating actuals, comparing forecasts and consolidating numbers from multiple files quickly turns into a manual and frustrating process.
And even if budgeting is already in a system, it can still feel like the same problem in a different form: difficult integrations, expensive and complex licensing, slow performance, or a tool that’s hard to modify without outside help.
Oivalo Planning is designed with these key concepts:
- Enterprise level features for needs of big, constantly changing, international organizations.
- Intuitive and fast as possible setup phase.
- Steer and control for admin users:
- Easy daily admin tasks and processes.
- Keep tracking what is the status of each planning process and administrate when hundreds of users are participating.
- Easy integrations (in and out) with existing Data/BI/reporting systems.
- Fool proof end user experience.
You want to improve your business planning and analytics
Oivalo Planning is also for you if you want planning to be more than just a P&L budget exercise. It helps you collect and consolidate drivers and planning details from multiple units quickly and easily, and it supports complex planning drivers when your business logic isn’t simple. You can build Profit and Loss budgeting alongside more detailed operative planning, combining sales drivers and P&L into one model instead of trying to connect them afterward. On top of that, budgeting and forecasting numbers can be used as reference data alongside actuals, so planning becomes part of your analytics instead of living separately.
Get it done quickly. Adjust it yourself.
Finally, Oivalo Planning is for you if you want an enterprise-level planning tool that still gives you real flexibility. It’s built for teams who don’t want to spend months just to try out a tool – or burn huge project hours with consultants before anything useful is delivered.
In the best scenario:
- you already have reference data available
- in SQL a data warehouse, reporting system
- you have an idea of what the logic of planning model should look like.
Most importantly, it’s a good fit if you want to stay in control and adjust the model yourself, instead of being dependent on constant outsourced consulting.
Absolute value
P&L accounts, amount of customers, business days…
Driver based
Multiply amount of customers with avarage spend, Plan salaries using hours and hourly salary or FTE, Use reference value like number of weekend days in a month multiplied with sales per day.
Percentage planning models
Personel side costs with pre defined percentage, product category sales margin as a percent from planned sales, set a cost based on sales etc
Summary and info
Statistical summaries and documentation can be delivered in the planning model to give the user information how for example Gross Margin % will set, what is the total sales of certain sub set of planning.
AI Assistant
Prompt over planning model, modify values or ask anything.
Use your selected AI API
Monthly or annual input
Plan on annual/total level and distribute values to months using pre-defined multipliers, reference value actuals, saved input values…
Day level planning is also supported
One input type (account) – multiple cost centers
Set values of one account over multiple cost centers at once. For example set rents account across the organization part.
Graphical input
See numbers in graphs and edit values from graph with reference line.
Dimensional planning
Split one account into several named or unnamed entries like customers, dimensions, sales products, employer category etc
Realtime
All values are updated realtime and user will see the end result all the time! Planning has simple reporting for consolidation and “Controlling use cases” to give easy answers and compare – even with your own reporting models when Data Manager is in use.
Fast to implement & transparent pricing
Oivalo Planning is designed to be set up quickly and adjusted independently.
Implementation project to get started typically takes 2–12 consulting days depending on model and organization complexity.
Pricing is transparent and predictable
- Monthly fee usually starts around 750 € and scales with scope
- No restrictive user licensing
- No forced consulting dependency
Customers for Planning
Daily reporting – A Planning extension
Daily reporting module makes day level data collection easy and integrates with advanced Planning organization and user access handling.
There is a lot of information that cannot be fetched from any system. Daily report comes to help getting that kind of data aligned. It delivers customizable form where wanted information from current day activities can be inserted.
Daily reporting can follow Planning day level figures and show how current day actuals are compared with planning numbers. So it is possible to set for example production amount target and then gather the production amounts – on daily level.
Daily reporting supports number and text inputs, forcing of content and many other process enablers needed to get quality data instead of adding rows to some spreadsheet on network drive or filling a generic feedback form on company intranet. It also supports simple reporting and calculations to generate for example month to date values or sales divided by working hours.
Data can also be combined from systems with API, so data points A and B are inserted by user and data set C comes from ERP
Possible use cases
- Daily sales and efficiency followup with comments
- Factory production amount followup
- Daily visitor number collection
- Employee NPS