So, Sales has a forecast, Operations has a capacity plan, and Finance has a budget. These plans make sense on their own; the problem is, they don’t “talk to each other”. And when the left hand doesn’t know what the right one is doing, how can the handover be a success? Here’s how to shift your planning from reactive to proactive and end the disconnect between your individual departments.
Most manufacturing (and other) organizations already have the data they need. The problematic part is the process of passing this data across the organization. This is the most common, basic scenario:
Sales updates a forecast → Operations sees it too late → Finance reacts after the impact has already materialized
With a structure like this, cross-department planning is nearly impossible. And we’re not even talking about ideas like using business intelligence for predictions!
No pointing at individuals; it’s the processes and spreadsheets that are often the silent culprit here. They work well for individual planning tasks, but once multiple teams depend on each other, spreadsheets turn planning into a sequence of manual handoffs. Each step introduces delays, assumptions, and loss of context.
(Surely, you’ve experienced that a shared file doesn’t automatically mean a shared understanding.)
Connected planning, fortunately, is not about adding another tool. It starts with creating a continuous flow where one plan becomes the input for the next. A typical connected planning scheme could then look like this:
Sales forecasts and demand signals inform capacity and production planning 👉 Capacity and production plans drive cost and expense planning 👉 Cost plans shape financial outcomes 👉 Financial plans are continuously compared with reality.
When something changes upstream, everyone downstream can immediately see the impact. Teams work within a single, connected planning logic
This is a real use case of what a connected planning flow looks like:
Note: If you’re wondering why we mention mushrooms, it’s because we’ve created an integrated planning option for our customer, Monterey Mushrooms (US). Read the full case study here!
As you can see, the key is not the individual plans themselves, but how changes propagate through the system.
Do you use Qlik for analysis and separate Excel spreadsheets for planning? Then, you are most likely to get caught in a loop of validating numbers rather than improving outcomes. Your planning becomes reactive rather than proactive.
But you can change this dynamic with Inphinity. Inphinity is a Qlik-native extension enabling teams to plan directly where the data already lives. And if the analysis and planning coexist in the same environment, changes are immediately visible across related plans.
It’s not just that plans are connected. Because the same number can play a different role in different plans, it’s also how planning items are mapped across them.
Sales quantity in the sales plan becomes a capacity requirement in operations. A cost driver in the expenses plan. And eventually part of the P&L. In Qlik, these relationships are defined at the data and model level, so all plans share a common structure and logic.
Inphinity then adds the planning layer on top of this model, handling inputs, ownership, and workflows across plans. This is what allows numbers to flow consistently between plans without losing context, and why changes made in one plan are immediately reflected in all the others.
So, using Inphinity in Qlik removes the artificial split between “this is where we analyze” and “this is where we plan.” Instead of exporting data to spreadsheets and re-uploading results, planning becomes a natural extension of analytics.
“Why spreadsheets struggle with cross-functional planning?”
Excel is flexible, pretty fast, and (as we like to emphasize) familiar, too. But that’s why it’s often pushed beyond its limits. Once planning involves multiple teams, it’s hard to maintain spreadsheet version control and preserve context behind changes. You can’t see real-time downstream impact or support-scenario comparison at scale.
Improvements in decision-making lie in the ability to continuously compare planned values with actual results and alternative scenarios.
Planning cross-functionally in Qlik enables your teams to understand not just what changed, but why it changed, and what to adjust next.
An upgraded workflow at Monterey Mushrooms, one of our US customers, is a great example. As their Senior Director of Information Services, Mr. Tom Langell, says, “The team has a single point of reference for the sales budget, resulting in one source of truth. The budget values are then integrated into the various reporting metrics in Qlik, with the understanding that they come from a single source. Long story short, spreadsheets have been eliminated.”
💡 When manufacturing planning is connected, teams spend less time defending their numbers, and planning becomes a shared responsibility across Sales, Operations, and Finance.
In manufacturing environments, especially, a single forecast update can affect production capacity, costs, and margins across the entire organization. That’s why it’s important to avoid reactive planning and use a cross-functional one directly inside Qlik.
Using Inphinity, you can extend analytics with planning capabilities, integrating sales, capacity, financial, and other plans into a single continuous flow. This way, manufacturing teams move from reactive handovers to proactive, coordinated decision-making.
If you’d like more info on your specific use case, you can talk directly with our tech lead, Guilherme.
