Demand Forecasting Agent: Every RFQ Lane Defined by Verified Demand Not Assumptions
Analyzes historical shipment data to build lane-level volume forecasts. Ensures RFQ scope reflects actual network demand, gives carriers the right volume signals for competitive bids.


















RFQs Go Out with Stale Demand Data. Bids Come Back Wrong.
RFQ demand baselines built from prior-year actuals with uniform growth assumptions miss lanes that shifted. Carriers bid on the wrong picture.
Demand Data Lives Across Disconnected Systems
Historical shipment data sits in TMS, ERP, WMS, and carrier portals not designed to produce a unified lane-level demand picture. Building a baseline requires pulling from multiple systems.
Volume Forecasts Are Based on Last Year's Actuals
Most enterprises use prior-year volumes as the RFQ baseline adjusted by uniform growth. Lanes that grew, contracted, or shifted mode carry the wrong demand signal.
Lane Bundling Is Done Without Optimization Logic
Freight demand is not uniform across the year. Lanes with Q4 peaks or manufacturing seasonality are presented to carriers with annual averages that don't reflect when volume moves.
Seasonal and Cyclical Demand Patterns Are Ignored
When order patterns drive volume from planned TL to LTL or from ocean to air, the mode mix cost increase is absorbed as a freight increase without identifying the demand behavior causing it.
New Lanes Have No Baseline
When a distribution center opens or a new channel is added, the associated lanes have no historical demand data. Carriers cannot bid accurately without a volume signal.
Mid-Year Demand Changes Are Not Reflected in Active Contracts
The connection between ordering behavior and freight cost is never made because no single system holds both. Demand-side cost drivers remain invisible to rate analysis.
Pull the Shipment Data. Build the Forecast. Package the RFQ Scope.
Analyzes historical shipment data across all modes, lanes, and geographies to build lane-level volume forecasts. Identifies seasonal patterns and bundling opportunities before the RFQ.
Historical Shipment Data Consolidation
Shipment data pulled from TMS, ERP, WMS, and carrier EDI feeds and consolidated into a unified lane-level demand picture. No manual extraction before the sourcing cycle.
Lane-Level Volume Forecasting
New lane demand modeled from network characteristics and analogous lane profiles. Carriers receive a credible volume signal from day one without historical data.
Seasonal and Cyclical Pattern Detection
Carrier coverage gaps, outlier pricing patterns, and format inconsistencies identified in each RFQ cycle improve accuracy of future RFQ construction and carrier shortlisting.
Lane Bundling Optimization
Carrier shortlists built from verified coverage and capability records against actual lane demand. Coverage gaps surfaced before distribution, not after bids arrive.
New Lane Demand Modeling
For lanes without historical data, demand modeled from network characteristics and analogous lane profiles. Carriers receive a credible volume signal even for new lanes.
Continuous Demand Monitoring
Actual shipment volumes monitored against contracted forecasts throughout the contract term. Significant demand deviations surfaced to procurement before they affect carrier relationships or trigger minimum commitment penalties.
Where This Agent Sits in the Pipeline
Analyzes historical shipment data across TMS, ERP, and WMS to produce lane-level demand forecasts with seasonal patterns, new lane estimates, and cost driver context.
Receives from
Spend Intelligence Agent
- Delivers freight spend data by lane and mode for demand analysis.
- Provides cost intelligence used to build volume forecasts for RFQ preparation.
Demand Analysis Agent
- Delivers demand pattern findings and cost driver context for incorporation into lane-level volume forecasts and bundling opportunity identification.
This Agent
Demand Forecasting Agent
- Consolidates historical shipment data, builds lane-level volume forecasts, identifies seasonal patterns and bundling opportunities, models new lane demand, and packages demand intelligence for RFQ design.
Triggers
RFQ Builder Agent
- Receives lane demand packages and volume forecasts.
- RFQ scope built from actual volume signals rather than historical averages.
RFP Builder Agent
- Receives demand forecasts for logistics RFP scope definition.
- Volume projections ensure RFP requirements reflect current lane demand, not historical averages.
Scenario Optimization Agent
- Receives lane-level demand forecasts and seasonal demand patterns for award scenario modeling.
- Volume commitments and minimum guarantee thresholds in award scenarios reflect projected demand, not assumed averages.
What Changes When RFQs Start with Accurate Demand Data
The freight network does not change. The accuracy of the demand picture you take into the market does.
Results from Live Deployments
Outcomes from enterprises running the Demand Forecasting Agent as the foundation of their freight sourcing cycles.
Every forecast is grounded in verified shipment history, not assumed growth rates. Seasonal patterns detected from multi-year actual data.
The Context Graph learns from every sourcing cycle. Volume actuals feed back into forecast accuracy. New lane modeling improves as analogous data accumulates.
The Context Graph learns from every sourcing cycle. Volume actuals feed back into forecast accuracy. New lane modeling improves as analogous data accumulates.
Demand intelligence flows into every downstream sourcing agent. RFQ Builder receives lane demand packages. Scenario Optimization receives volume commitment inputs.
Demand monitoring throughout the contract term. Deviations surfaced to procurement before they create carrier strain or trigger commitment disputes.
Scales with lane count and sourcing cycle frequency. No incremental analyst effort as the freight network grows.
Reads Shipment History Where It Lives. Delivers Demand Intelligence to the Sourcing Pipeline.
Reads from TMS, ERP, and WMS shipment data. Delivers lane demand packages to the RFQ Builder and Scenario Optimization agents.
SAP TM · Oracle TMS · MercuryGate · BluJay · project44
Lane-level demand data consolidated automatically from TMS, ERP, WMS, and carrier EDI without manual extraction.
SAP S/4HANA · Oracle Fusion · JD Edwards · NetSuite
Order data, production schedules, and demand plan actuals read from ERP to enrich shipment-based forecasts with upstream demand signals.
Manhattan WMS · Blue Yonder · Oracle WMS
Warehouse throughput, inbound and outbound shipment volumes, and fulfillment activity read for lane-level demand enrichment and new lane modeling.
EDI 214 · EDI 856 · Carrier Tracking APIs
Delivery confirmation, shipment status, and transit event data from carrier EDI ingested for demand actuals and seasonal pattern confirmation.
Freehand Spend Intelligence Agent
Carrier-specific demand forecasts delivered to the RFQ Builder for carrier shortlisting and bid package construction.
DAT · FreightWaves · Xeneta
Demand actuals monitored against contracted forecasts. Significant deviations surfaced to procurement before they affect carrier relationships.
Freehand RFQ Builder Agent
Lane demand packages and seasonal pattern context delivered to the RFQ Builder Agent for carrier bid packages.
Freehand Scenario Optimization Agent
Volume forecast data written for use in award scenario modeling. Demand-backed commitment structures reflect actual projected volumes.
Freehand Carrier Evaluation Agent
Demand forecast data delivered to Scenario Optimization for volume commitment stress testing against award scenarios.
MS Teams / Slack
Demand deviation alerts and seasonal pattern warnings delivered to procurement teams when volumes deviate from contracted forecasts.
Snowflake / Databricks
Demand forecasts, seasonal patterns, and actuals-vs-forecast comparisons written to data lake for multi-period trend analysis.
Freehand Spend Intelligence Agent
Demand intelligence delivered to the Demand Analysis Agent for incorporation into cost driver analysis and structural savings identification.
Accurate Demand Data. Competitive Bids. Better Awards. Every Cycle.
Real outcomes from enterprise deployments across consumer goods, industrial, retail, and logistics categories.
Powered by the Freehand Context Graph
The Context Graph connects lane-level demand data, carrier coverage, market rate benchmarks, and contracted terms. Every lane definition reflects verified demand and current market conditions.
Built on the Freehand Logistics Language Model, trained on freight demand patterns, lane-level volume analysis, and seasonal forecasting. It translates operational shipment history into credible carrier demand signals.
- Every forecast is grounded in verified shipment history, not assumed growth rates. Seasonal patterns detected from multi-year actual data. New lane demand modeled from analogous lanes.
- The Context Graph learns from every sourcing cycle. Volume actuals feed back into forecast accuracy. New lane modeling improves as analogous lane data accumulates.
- Demand intelligence flows into every downstream sourcing agent. RFQ Builder receives lane demand packages. Scenario Optimization receives volume commitment inputs. Carrier Evaluation receives demand-weighted scoring.
Demand Forecasting: Questions Procurement Teams Ask
Straight answers to what freight procurement leaders ask before deploying the Demand Forecasting Agent.
Any freight demand question: lane-level volume by season, mode mix forecast, new lane demand estimate, year-over-year trend. The agent surfaces the answer.
Configured in Freehand Studio. The analyst reviews the demand forecast before it enters the RFQ package. Any adjustment is logged and applied to the lane definition.
Configured in Freehand Studio to flag demand deviations above the configured threshold. Alerts delivered to procurement and logistics via the Alerting Agent when actuals deviate from contracted forecasts.
The Demand Forecasting Agent feeds the RFQ Builder Agent with lane demand packages. Scenario Optimization receives volume commitment inputs. The Demand Analysis Agent receives demand patterns for cost driver analysis.
Receives shipment data from TMS, ERP, and WMS. Delivers lane demand packages to the RFQ Builder Agent, Scenario Optimization Agent, and Demand Analysis Agent.
Deployable in days via pre-built connectors to TMS, ERP, and WMS. Lane demand forecasts available from the first historical data load after go-live.
Start Every Sourcing Cycle with Accurate Demand Data.
Lane-level forecasts from real shipment data. Seasonal patterns identified. Bundling opportunities surfaced. Deployable in days. Connected to your TMS, ERP, and WMS from go-live.
Built on Freehand Studio · freehand.ai

