How to Run a Pilot Forecast Project for a Mid-Market Company

TL;DR

A pilot forecast project is a time-boxed initiative (typically 8 to 12 weeks) that tests a demand forecasting approach on a limited set of SKUs before committing to full deployment. Mid-market companies between $10M and $5B in revenue face unique constraints: smaller teams, tighter budgets, and data spread across systems that rarely talk to each other. This guide defines every term you’ll encounter when scoping, running, and measuring a forecast pilot, organized in the sequence you’ll actually need them, not alphabetically. The goal is to help you avoid pilot purgatory, prove value fast, and build a business case your CFO will approve.

---

Why This Glossary Exists (and Who It’s For)

According to a 2026 Kaufman Rossin report, 73% of mid-sized manufacturers are unable to achieve full operational status with their AI initiatives. They’re stuck testing. Only 7% of mid-market companies are positioned for company-wide AI scaling. That gap between “we ran a pilot” and “we’re actually using this” is where most forecasting projects go to die.

If you’re a supply chain leader, VP of operations, or finance executive at a mid-market company, you’ve probably felt the pressure. The largest businesses employ armies of PhDs to tune their forecasts and build custom tools. Mid-market companies representing a third of US GDP don’t have that luxury. You need a contained, measurable pilot that proves value before anyone signs off on a broader rollout.

This glossary covers every concept you’ll encounter when figuring out how to run a pilot forecast project for a mid-market company. Each term includes a plain-language definition, why it matters during a pilot specifically, and a practical warning or tip. The terms are grouped by pilot phase so you can read them in order or jump to the section you need.

Explore BetterDemand’s forecasting engine to see what a purpose-built mid-market tool looks like.

---

Section 1: Scoping and Readiness Terms

Before you touch a forecasting model, you need to get the foundation right. The first mistake most organizations make is selecting a platform before assessing whether they’re ready to use one. This section covers the terms that define what a pilot is, what it needs, and who owns it.

Pilot Forecast Project

Definition: A time-boxed initiative, typically 8 to 12 weeks, that tests a demand forecasting approach on a limited product scope before committing to full deployment. It runs in parallel with existing methods so you can compare results side by side.

Why it matters: A pilot is not a proof of concept that sits in a slide deck. It’s a live test on real data with real planners using the outputs. The distinction matters because 80% of AI projects fail to deliver promised business value, and most of those failures happen in the gap between “interesting demo” and “production workflow.”

Practical tip: Set a hard end date with a go/no-go decision. Without one, you’ll drift into perpetual evaluation, the most common form of mid-market pilot purgatory.

Data Readiness Assessment

Definition: A structured evaluation of whether your historical data is clean, complete, and accessible enough to support a forecasting model. This covers sales history, inventory records, and any external signals you plan to incorporate.

Why it matters: AI forecasting models need at least 24 to 36 months of granular sales history to capture seasonality and year-over-year patterns. If you only have 12 months of clean data, you’re building a forecast that can’t see a full seasonal cycle. Practitioners on Reddit’s r/SupplyChainLogistics consistently report that data cleanliness, not algorithm sophistication, is the primary bottleneck in forecasting projects.

Practical tip: If your data isn’t ready, spend 4 to 8 weeks on data quality improvement before model development. Clean data with simple algorithms outperforms messy data with sophisticated ones every time. Your data probably lives in NetSuite, SAP Business One, or a mix of spreadsheets and ERP exports. The first project is getting those sources to reconcile, not picking a model.

For a deeper look at what clean data actually means in practice, see this guide on using sales and inventory data to improve demand forecasts.

SKU Scope (Pilot SKU Set)

Definition: The specific subset of products selected for the pilot. Typically one product family, one distribution center, or one supplier segment.

Why it matters: Scope determines whether your pilot produces meaningful results or just noise. Practitioners recommend picking a product family with meaningful demand variability, not your most predictable items. You want the pilot to face real forecasting challenges so the results translate to the broader business.

Practical tip: Make a shortlist of 3 use cases, score them by impact versus data availability, and pick one. Resist the temptation to include “just a few more SKUs” once the pilot starts. Scope creep kills timelines and makes it impossible to attribute results clearly.

Baseline Forecast

Definition: The “before” snapshot of your current forecasting performance. This captures accuracy, bias, and inventory outcomes using your existing method (whether that’s a planner’s spreadsheet, ERP native forecasting, or gut instinct) before the pilot launches.

Why it matters: Without a baseline, you can’t measure improvement. This sounds obvious, but a surprising number of companies skip this step and then find themselves three months into a pilot unable to answer the question “is this better?” Capture accuracy metrics, service levels, and inventory positions at the SKU level before you change anything.

Practical tip: Document the baseline formally and get stakeholders to sign off on the numbers. If you let people retroactively argue about what performance “used to be,” the pilot results become political instead of factual. The hidden cost of gut-instinct planning is often larger than teams expect.

Parallel Run

Definition: Operating the new forecasting approach alongside the existing method for a defined period, typically 90 to 120 days, and comparing outputs without yet using the new forecast to drive decisions.

Why it matters: Parallel runs protect you from catastrophic errors while giving you clean comparative data. The new forecast generates recommendations, but purchasing and replenishment decisions still follow the existing process. You’re building confidence and evidence simultaneously.

Practical tip: Don’t extend the parallel run indefinitely. Industry practitioners converge on 90 to 120 days as the window. Beyond that, you’re not gathering new information; you’re just avoiding a decision.

Executive Sponsor

Definition: A single senior leader who owns the pilot end to end and has the authority to remove obstacles, allocate resources, and make the go/no-go decision.

Why it matters: Assign a single owner for the deployment end to end. No owner, no production. This is the consistent message from organizations that have escaped pilot purgatory. Mid-market companies are disproportionately affected by stalled pilots because they run fewer initiatives in parallel, so each failure consumes a larger share of available budget and executive attention.

Practical tip: The executive sponsor should not be the person building the model. They should be the person who cares most about the business outcome (typically a VP of Operations or Supply Chain Director) and who can hold the organization accountable for actually using the output.

---

Section 2: Forecasting Method Terms

Once you’ve scoped the pilot and confirmed data readiness, you need to understand the forecasting approaches you’re testing. This section defines the methods and concepts your team will encounter during the pilot itself.

Demand Forecast

Definition: A quantitative estimate of future customer demand for specific products over specific time periods. It combines historical patterns, known events, and external signals to project what customers will buy.

Why it matters during a pilot: The pilot forecast needs to be actionable, meaning it produces numbers at the SKU/location/week level that a planner can actually compare against the baseline and eventually use to drive purchasing. A forecast that only works at the category level or monthly rollup won’t prove value for operational decisions.

Multi-Horizon Forecast

Definition: A forecasting approach that generates predictions across multiple time frames simultaneously: short-term (weeks, for operational execution), mid-term (months, for S&OP and tactical planning), and long-term (quarters to years, for strategic planning).

Why it matters during a pilot: Most mid-market companies start by fixing the short-term forecast because that’s where the pain is most visible (expedited freight, stockouts, frantic purchasing). But a good pilot should also generate a mid-term signal so you can demonstrate value to the S&OP process and show the CFO an inventory reduction trajectory.

For a detailed walkthrough of building this kind of forecast at a mid-market company, see the guide on multi-horizon demand forecasting.

Time-Series Forecasting

Definition: Statistical methods that predict future values based on patterns in historical data. Common techniques include moving averages, exponential smoothing, and ARIMA (AutoRegressive Integrated Moving Average).

Why it matters during a pilot: Time-series methods are the backbone of most forecasting pilots because they’re interpretable and relatively fast to implement. Your team doesn’t need a PhD to understand “this method weights recent data more heavily.” That interpretability matters for adoption.

Practical tip: Don’t obsess over which specific algorithm to use at the pilot stage. The model selection matters far less than data quality and process discipline. A simple exponential smoothing model on clean data will outperform a neural network trained on garbage.

Demand Drivers

Definition: External and internal factors that influence demand beyond historical patterns. These include promotions, price changes, seasonality, weather, competitor actions, economic indicators, and marketing spend.

Why it matters during a pilot: Incorporating demand drivers is what separates a statistical extrapolation from a real forecast. During the pilot, identify which drivers have the biggest impact on your pilot SKU set. You don’t need to model everything, just the two or three factors that explain the largest demand swings.

Demand Sensing

Definition: The use of near-real-time data signals (point-of-sale data, web traffic, order pipeline) to detect demand shifts in the very short term, typically days to weeks ahead.

Why it matters during a pilot: Demand sensing is distinct from traditional forecasting. It’s about catching sudden shifts that historical models miss. For a pilot, it’s usually a Phase 2 addition rather than a starting point. Get the baseline statistical forecast working first.

Statistical Forecast vs. Judgmental Forecast

Definition: A statistical forecast is generated by algorithms using historical data and mathematical models. A judgmental forecast incorporates human knowledge, market intelligence, and planner intuition.

Why it matters during a pilot: The pilot should test both and measure which adds value. This is where Forecast Value Add (covered in Section 3) becomes critical. In many mid-market companies, the existing forecast is 100% judgmental (a planner’s spreadsheet). The pilot needs to show whether the statistical forecast alone is better, or whether the combination of statistical plus human override is the winning approach.

Practical tip: Track every human override during the pilot. If planner adjustments consistently make the forecast worse, that’s a powerful data point for the business case. If they consistently improve it, you know you need a collaborative model.

---

Section 3: Measurement and KPI Terms

You can’t build a business case without hard numbers. This section defines the metrics you’ll use to evaluate whether the pilot worked, and it highlights the gotchas that can make good performance look bad (or bad performance look good).

MAPE (Mean Absolute Percentage Error)

Definition: The average of the absolute percentage differences between forecasted and actual demand across all items and periods. It’s calculated by dividing each individual error by the actual demand, then averaging.

Why it matters during a pilot: MAPE is the most widely recognized forecast accuracy metric, which means your CFO and board will understand it. However, it has a well-known flaw: it divides each error individually by demand, so it’s heavily skewed by low-volume SKUs. A slow-moving item that sells 2 units when you forecasted 4 registers as a 100% error, even though the absolute miss is trivial.

Practical tip: Don’t use MAPE as your headline pilot KPI if you sell slow-moving SKUs. It’ll make your forecast look terrible even when it’s good. Use WMAPE instead (next entry) and keep MAPE as a secondary reference for high-volume items.

WMAPE (Weighted Mean Absolute Percentage Error)

Definition: A variant of MAPE that weights each item’s error by its volume or revenue contribution. This ensures that accuracy on your highest-impact products carries the most weight in the overall score.

Why it matters during a pilot: WMAPE solves MAPE’s main weakness. It focuses attention on the products that have the biggest impact on the business. For a mid-market company where 20% of SKUs typically drive 80% of revenue, WMAPE gives you a much more honest picture of forecast quality.

Practical tip: Define the weighting basis (units, revenue, or margin) before the pilot starts. Revenue weighting is usually best for the business case because it directly connects accuracy to financial outcomes. Be aware that bias can hide at the aggregate level, so look at WMAPE by product family, not just the overall number.

Forecast Bias

Definition: A measure of the systematic tendency to consistently over-forecast or under-forecast demand. Unlike accuracy metrics that measure the size of errors, bias measures their direction.

Why it matters during a pilot: Bias is arguably more important than accuracy during a pilot because it reveals whether the forecast is structurally broken. A forecast with 30% MAPE but zero bias will average out over time. A forecast with 20% MAPE and consistent positive bias will steadily build excess inventory.

Practical tip: Measure bias separately for the statistical model and for human overrides. In many organizations, the statistical model is unbiased but planners systematically inflate forecasts “just in case.” The pilot should expose this pattern.

Tracking Signal

Definition: A cumulative measure of whether forecasts are trending consistently too high or too low over multiple periods. It acts as an early warning system against developing bias. When the tracking signal strays consistently from zero, it means the model needs recalibration.

Why it matters during a pilot: Check the tracking signal weekly during the pilot. If it starts drifting after week 4, you catch the problem early enough to adjust. If you only check accuracy at the end of 12 weeks, you’ve wasted time running a forecast that went off the rails in month one.

Forecast Value Add (FVA)

Definition: The measurement of whether each step in the forecasting process (statistical model, planner adjustment, sales input, management override) actually improves the forecast or makes it worse. It’s calculated by comparing accuracy at each stage.

Why it matters during a pilot: FVA is the single most important concept for building the business case. It answers the question “did the new approach actually add value compared to the baseline?” If your pilot forecast has a WMAPE of 22% and your baseline was 28%, that 6-point improvement is the FVA. For a deeper exploration of why accuracy is never just a model problem, see why forecast accuracy is a process problem.

Practical tip: Measure FVA not just for the model but for every human touchpoint. Some companies discover that their sales team’s input actually degrades accuracy. That finding alone can justify the pilot investment.

Forecast Accuracy

Definition: A general term for how closely the forecast matches actual demand. Typically expressed as (1 minus error percentage). At a 25% MAPE, forecast accuracy is 75%.

Why it matters during a pilot: What counts as “good” accuracy depends entirely on the aggregation level. At the SKU/week level, 65 to 75% accuracy might be excellent for a mid-market company with high variability. At the product family/month level, the same company should expect 85%+. Always specify the level when reporting results, or the numbers become meaningless.

Practical tip: According to UC Berkeley MIDS research, improving forecast accuracy by just 1% can translate to a 2 to 4% improvement in profit. That’s the stat to put in your business case.

See BetterDemand’s pricing tiers to understand what a 90-day pilot with built-in value guarantees actually costs.

---

Section 4: Process and Organizational Terms

Technology is never the reason mid-market pilots fail. Process and people are. This section covers the organizational concepts that determine whether your pilot ever makes it out of the test environment and into daily operations.

S&OP (Sales and Operations Planning)

Definition: A monthly planning cadence that aligns sales, operations, finance, and executive leadership around a single demand and supply plan. The demand forecast is the primary input; S&OP is the process that makes it actionable.

Why it matters during a pilot: If the pilot forecast doesn’t connect to S&OP, it’s just a number on a screen. Even during a pilot, build a lightweight monthly review where stakeholders examine the forecast output, discuss exceptions, and make decisions. This proves the forecast can drive action, not just measure accuracy.

Practical tip: Download the S&OP Playbook for a step-by-step guide to building this cadence from scratch.

Exception Management

Definition: The practice of focusing planner attention only on items where the forecast deviates significantly from expectations or where business rules flag a risk, rather than reviewing every SKU manually.

Why it matters during a pilot: Mid-market teams are small. Your demand planner probably also handles purchasing, vendor management, and inventory analysis. Exception management is what makes the pilot operationally feasible. Without it, the planner drowns in data and abandons the tool.

Practical tip: Define exception thresholds before the pilot starts. Common thresholds include forecast error greater than 30%, demand change exceeding 50% week over week, or stockout risk within lead time. For teams stretched thin, a supply chain agent can handle the exception triage and surface only the decisions that need human judgment.

Consensus Forecast

Definition: A single demand number that sales, operations, and finance all agree to use as the basis for planning. It’s the output of the S&OP process.

Why it matters during a pilot: During the pilot, you may not have full organizational alignment yet. That’s fine. But you should still designate one version of the forecast as the “plan of record” for the pilot SKU set. Multiple competing numbers create confusion and make it impossible to measure results cleanly. For context on why consensus building often goes sideways, see why collaborative forecasting is mostly theater.

Pilot Purgatory

Definition: The state in which an AI or forecasting initiative has completed its proof-of-concept phase but has not advanced to production, often stalling indefinitely due to unresolved governance, data, or organizational readiness gaps.

Why it matters: According to MIT Media Lab research, 95% of enterprise AI pilots never reach production. The reason is rarely the technology. Most AI initiatives are stuck not because the technology fails, but because operations, ownership, and measurement were never properly established.

The mid-market version: The most common mid-market form of pilot purgatory is the “perpetual evaluation,” where the organization keeps testing new tools without committing to deploying any of them. Each failed or inconclusive pilot consumes a larger share of available budget and executive attention than it would at an enterprise with a portfolio of initiatives.

The escape route: Fix data plumbing only for that one workflow. Capture a clean baseline before launch. Assign a single owner. Set a hard deadline with explicit go/no-go criteria. Ship one boring, measurable workflow at a time.

Change Management

Definition: The structured approach to transitioning individuals, teams, and the organization from current planning methods to the new forecasting process.

Why it matters during a pilot: Planners who have relied on spreadsheets and intuition for years will resist a model that tells them something different. That resistance is natural and predictable. The pilot must include explicit time for training, for explaining why the model recommends what it does, and for letting planners override the model (so you can measure whether those overrides help or hurt).

Practical tip: Most mid-market wins come from consistency, not heroics: clear inputs, tested outputs, and a regular check-in to keep models aligned with reality. Don’t frame the pilot as “replacing the planner.” Frame it as “giving the planner a better starting point.”

---

Section 5: Outcome and Business Case Terms

The whole point of the pilot is to build a business case for scaling. This section defines the financial and operational outcomes you need to quantify for the go/no-go decision.

Inventory Distortion

Definition: The total financial cost of having the wrong inventory in the wrong place at the wrong time. This includes both overstocks (excess carrying costs, markdowns, obsolescence) and stockouts (lost sales, expedited shipping, damaged customer relationships).

Why it matters during a pilot: The IHL Group estimates that global inventory distortion cost $1.7 trillion in 2024, with out-of-stocks accounting for $1.2 trillion and overstocks totaling $554 billion. For a mid-market company, even a small percentage improvement in inventory distortion translates to meaningful cash. The pilot should measure changes in both overstock and stockout rates for the pilot SKU set.

Service Level (OTIF / Fill Rate)

Definition: OTIF (On Time In Full) measures the percentage of customer orders delivered complete and on schedule. Fill rate measures the percentage of ordered units shipped from available stock. Together, they represent the customer experience the forecast is ultimately trying to protect.

Why it matters during a pilot: Accuracy improvement means nothing if service levels don’t hold or improve. The pilot should track OTIF and fill rate for pilot SKUs alongside forecast accuracy. An improvement in accuracy that doesn’t move service levels suggests the forecast isn’t being used to drive decisions, which is a process failure, not a model failure.

Working Capital Impact

Definition: The change in cash tied up in inventory as a direct result of improved forecasting. Better forecasts reduce the need for excess safety stock and speculative purchasing, freeing cash for other uses.

Why it matters during a pilot: This is the number your CFO cares about most. Translate forecast accuracy gains into inventory dollar reductions. If the pilot demonstrates that you can reduce average inventory for the pilot SKU set by 15% while maintaining service levels, multiply that by the full portfolio to estimate the scaled impact. For a deeper analysis of where cash gets trapped, read about where working capital hides in inventory.

Safety Stock

Definition: The buffer inventory held to protect against forecast error and supply variability. When forecasts improve, the required safety stock decreases because there’s less uncertainty to buffer against.

Why it matters during a pilot: Safety stock reduction is one of the most tangible financial outcomes of a forecast pilot. If your pilot reduces WMAPE by 6 percentage points, your safety stock calculation should reflect that reduced uncertainty. Quantify the inventory dollars freed and include it in the business case.

Practical tip: Many mid-market companies use static safety stock rules (e.g., “keep 2 weeks of supply”) that don’t adjust with forecast quality. If that’s you, your safety stock formula may be lying about what you actually need.

Go/No-Go Decision

Definition: The formal evaluation at the end of the pilot period where the executive sponsor and stakeholders decide whether to scale the forecasting approach to additional products, locations, or channels.

Why it matters: This is the decision the entire pilot is designed to inform. Without explicit go/no-go criteria defined at the start, the decision becomes subjective and political. The criteria should include minimum accuracy improvement (e.g., 5+ percentage points of WMAPE improvement over baseline), demonstrated process adoption (planners actually using the output), and a financial projection of scaled impact.

Practical tip: The portfolio approach to AI investment organizes initiatives into quick wins (30 to 90 day payback), strategic bets (6 to 12 months), and infrastructure investments, sequenced so that each phase funds the next. Position your forecast pilot as the quick win that funds the broader roadmap.

A cautionary tale: Nike experienced major issues with its i2 demand planning software in 2000, resulting in $100 million in lost sales. But the project survived because leadership had defined a clear long-term business case before the pilot stumbled. The lesson for mid-market companies: build the business case before the go/no-go meeting, not during it.

---

Putting It Together: The Pilot Timeline

Understanding the terms is essential. But you also need to know when each concept comes into play. Here’s how to run a pilot forecast project for a mid-market company in three phases, mapped to the glossary above.

Phase 1: Foundation (Months 1 to 3)

This is where you do the Data Readiness Assessment, select the Pilot SKU Set, capture the Baseline Forecast, and identify the Executive Sponsor. Audit data quality across ERP, CRM, and WMS. Establish governance standards. Fix data plumbing only for the pilot workflow.

Key deliverables: Clean data set covering 18+ months of history for pilot SKUs, documented baseline metrics (MAPE, bias, service levels, inventory position), and a signed pilot charter with scope, timeline, and go/no-go criteria.

Phase 2: Pilot (Months 3 to 6)

Deploy the forecasting model on the pilot SKU set. Run a Parallel Run alongside the existing method for 90 to 120 days. Train planners on interpreting model outputs and managing exceptions. Measure WMAPE, Forecast Bias, Tracking Signal, and FVA weekly.

Key deliverables: Weekly accuracy comparison (new vs. baseline), exception management workflow in operation, and S&OP integration for pilot SKUs showing the Consensus Forecast being used in planning decisions.

Phase 3: Scale Decision (Month 6)

Present pilot results at the Go/No-Go Decision meeting. Quantify Working Capital Impact, Service Level changes, and Safety Stock reduction. Project financial impact at full portfolio scale. If the answer is go, expand to additional product families and geographies over months 6 to 12.

Key deliverables: Executive presentation with financial business case, deployment roadmap for scaled rollout, and change management plan for broader organization.

---

Frequently Asked Questions

How long should a pilot forecast project take for a mid-market company?

Plan for 8 to 12 weeks from kickoff to initial results for a focused pilot. Including the foundation phase (data preparation, baseline capture), the full timeline is typically 3 to 6 months. Extending beyond 6 months without a go/no-go decision is a strong signal you’ve entered pilot purgatory.

How many SKUs should we include in the pilot?

Start with one product family or category, typically 50 to 200 SKUs. Choose items with meaningful demand variability, not your most predictable products. The goal is to prove the approach works on real complexity, not to cherry-pick easy wins.

What’s the minimum data history needed?

At least 18 to 24 months of clean historical sales data. If you need the model to capture seasonal patterns reliably, 24 to 36 months is better. If your data isn’t ready, invest 4 to 8 weeks in cleanup before starting the pilot. Skipping this step is the most common reason forecasting pilots fail.

Which accuracy metric should we use as the primary KPI?

WMAPE (Weighted Mean Absolute Percentage Error) is the best primary KPI for most mid-market pilots. It weights accuracy by volume or revenue, so it focuses on the products that matter most. Use standard MAPE only as a secondary metric for high-volume items. Avoid using MAPE alone if you have slow-moving SKUs.

How do we know if the pilot was successful?

Define success criteria before the pilot starts. Common thresholds include: WMAPE improvement of 5+ percentage points over baseline, neutral or positive impact on service levels, demonstrable forecast adoption by planners (measured by exception handling rates), and a projected financial impact that justifies the cost of scaling.

What does a forecast pilot cost for a mid-market company?

Costs vary widely depending on whether you build in-house, buy software, or engage an advisory service. For a mid-market company, expect to invest between $12,000 and $40,000 for a 90-day pilot depending on scope and support level. The relevant comparison isn’t the pilot cost but the cost of the problem: even a 1% improvement in forecast accuracy can drive 2 to 4% profit gains.

What’s the biggest risk in running a forecast pilot?

Not the technology. The biggest risk is running a pilot that never reaches production. Set a hard end date, assign a single executive owner, and define go/no-go criteria in writing before you start. Every week the pilot drifts without a decision costs credibility and budget.

Can we run a forecast pilot without a data science team?

Yes. Most mid-market companies don’t have dedicated data scientists, and that’s fine. The pilot needs clean data and a structured process more than it needs PhD-level modeling. Purpose-built forecasting tools and advisory services exist specifically for companies in this position.

---

What Comes Next

If this glossary maps to problems you’re actively working through, the terms on this page aren’t theoretical for you. They’re decisions you’ll face in the next quarter.

See how BetterDemand runs 90-day forecast pilots with built-in value guarantees, dedicated senior supply chain expert hours, and forecasts built on your actual data, not generic templates. Every subscription tier is designed for mid-market companies between $10M and $5B in revenue, with transparent pricing and measurable outcomes commitments.