In mid-market distribution and manufacturing, the demand planning function is frequently understaffed relative to the complexity of the task being asked of it. The gap between what one or two planners are expected to manage and what that volume of work actually requires is one of the most consistent patterns we observe when we work with companies getting started on demand forecasting improvements. The planners are not failing at their jobs. They are succeeding at an impossible scope.
This piece documents what we have learned from working with demand planning teams at manufacturers and distributors with 50-500 employees - how these teams are actually structured, where the capacity constraints hit hardest, and what changes in tooling tend to produce the most relief.
The Typical Structure
At a distributor with 50-150 employees, the demand planning function is often not a distinct function at all. The purchasing manager, the operations manager, or in some cases a senior buyer handles demand forecasting as one part of a broader job that also includes vendor management, purchase order execution, and coordination with the warehouse team. There is no forecasting specialist. There is a person whose job description includes forecasting.
At companies in the 150-300 employee range, the most common structure is a single dedicated planner - sometimes titled Demand Planner or Inventory Planner - who owns the forecast process. They report to either the Director of Operations or the VP of Supply Chain. They work with a set of ERP exports and spreadsheets that have been built up over time, sometimes incorporating tools from previous planners, sometimes rebuilt from scratch when someone new came in.
At 300-500 employees, a two or three person planning team is more common, often with a split between tactical execution (reorder triggers, purchase order management) and strategic planning (forecast development, inventory optimization). But even at this scale, the planning team is managing a catalog that would be considered heavy for a team twice the size at an enterprise company with more sophisticated tools.
Where the Capacity Crunch Hits
The capacity constraint in single-planner or small-team demand planning is almost always in the data assembly and review cycle, not in judgment. When we ask planners where their time goes, the answer is consistently that 40-60% of their weekly planning time is spent extracting data from the ERP, formatting it, and reconciling it with prior-week data - not making decisions about what to order or how to adjust the forecast.
This creates a triage problem. Planners operating at capacity cannot monitor the full catalog with equal attention. They develop informal rules for what to check and what to trust. High-velocity items get reviewed because a mistake on them is immediately visible. Medium-velocity items get reviewed periodically when time allows. Long-tail items often run on autopilot - their reorder points are set and not revisited unless someone notices a stockout or an excess accumulation.
The consequence is that a significant portion of the catalog is effectively unplanned. Reorder points that were set years ago are still in the system. Seasonal adjustments that were once appropriate no longer match current demand patterns. The planner knows this, but does not have time to fix it while managing the day-to-day. The backlog of "things the ERP should be updated on" grows indefinitely.
What Planning Tools Actually Change
When planning teams at mid-market companies adopt forecasting tools, the question most often asked is "what will the system do for me." The most honest answer is that the primary benefit is not that the system makes better decisions - it is that the system eliminates the data assembly overhead that consumes 40-60% of planner time, freeing that time for actual planning decisions.
A planner who previously spent two hours every Monday pulling ERP exports, updating spreadsheet formulas, and reconciling last week's actuals against the forecast now spends 20 minutes reviewing a dashboard that has already done all of that. The reorder recommendations are already calculated. The items that need attention this week are already surfaced and ranked by urgency. The planner's job shifts from data assembly to decision review.
This shift has a secondary effect that is harder to quantify but frequently reported: the planner's attention can now reach the middle and long-tail catalog in a way it could not when the week was consumed by manual data work. Items that were running on autopilot for two years because there was no bandwidth to review them start getting reviewed. Reorder points that were wrong get corrected. Seasonal adjustments that had drifted get updated.
The Handoff Problem
One of the most expensive planning problems in mid-market companies is the handoff when a planner leaves. The spreadsheets, the ERP configuration, the institutional knowledge about which items behave unusually, the informal rules built up over years - most of this exists only in the outgoing planner's head and in a set of files that the incoming planner may not be able to fully interpret.
Companies with well-documented, system-driven planning processes survive planner transitions more gracefully than those where the planning process is inseparable from a specific person's working style. When the forecast lives in a maintained system rather than a spreadsheet, the incoming planner inherits the forecast methodology, not just the data. The transition cost in forecast quality is lower, and the ramp time before the new planner is operating at full effectiveness is shorter.
This is an underappreciated argument for investing in demand planning infrastructure at the mid-market level. It is not just about accuracy improvement or efficiency gain during steady-state operations. It is about reducing the institutional knowledge risk that is inherent in one or two-person planning teams.
What Planners Actually Want
When we ask planners what they wish their systems did that they do not currently do, the answers cluster around three themes. First, they want to know about problems before they become emergencies - a stockout alert that fires six weeks before the event, not on the day the bin empties. Second, they want the system to handle the routine and surface only the exceptions - not a daily report of all 2,000 items, but a prioritized list of the 20 items that actually need attention today. Third, they want the data to always be current - not a Monday export that is stale by Wednesday, but a live inventory position and demand rate updated each day.
These are not technically ambitious requirements. They describe a system that continuously ingests ERP transaction data, maintains an updated forecast, and surfaces exceptions to the planner's attention in priority order. That system does not require a data science team to operate or an enterprise-level software budget to procure. For a mid-market company with one or two planners managing a 2,000-5,000 SKU catalog, it is the single most productive technology investment available in the supply chain function.
