Financial planning · Case study
FedEx: cut costs in step with the revenue forecast
Forecast monthly revenue with a range, and approve the cost actions before a miss reaches the quarter.
By OneShot · Updated
Read the solution ↓What the workflow produces
Revenue forecast and cost plan- Forecast
- Twelve-month revenue per segment with its 80% range.
- Gap
- Forecast against plan, by segment and month.
- Actions
- Cost actions with saving, lead time and owner.
- Decision
- Approved actions and their progress at each close.
The documented problem
On September 15, 2022, FedEx reported preliminary first-quarter results with a revenue shortfall at FedEx Express of approximately $500 million relative to company forecasts, and FedEx Ground revenue approximately $300 million below company forecasts. It withdrew the fiscal year 2023 earnings forecast it had given on June 23, 2022.
FedEx listed the cost actions it was taking, among them parking aircraft, deferring staff hiring and closing over 90 FedEx Office locations. These are FedEx’s own figures. The OneShot workflow below forecasts monthly revenue with a range and has cost actions approved before a miss reaches the quarter.
- FedEx: preliminary first quarter results and outlook updatePrimary source · Checked 2026-10-23
The OneShot solution
Costs cut in step with the revenue forecast
Match costs to the monthly revenue forecast, with cost actions approved before a shortfall reaches the quarter’s results.
What it pays back
Cost cut in the month revenue falls
Counted per month, in days from a forecast below plan to an approved cost action, and the cost that action removes.
- 01
Read revenue and volume
Read three years of monthly revenue by segment and the latest weekly volumes, with the operating plan for the year. Mark one-off months, such as a pricing change, so they do not skew the forecast.
- 02
Forecast each segment
The OneShot agent uses its prediction tool to forecast twelve months of revenue per segment with an 80% range. The point forecast is compared with the plan; the range is what the plan is judged against.
- Predict
- Revenue plan and actuals
- 03
Line up the cost actions
When a segment’s forecast falls below the plan’s range, ask its finance lead by email which costs move with volume, how fast and by how much. Research the published outlook for the segment’s markets where the forecast and the plan disagree.
- Email Inbox
- Deep Research
- Revenue plan and actuals
- 04
Get the actions approved
Give the chief financial officer the forecast, the gap to plan and the cost actions ranked by saving and lead time. Record the approved actions, their owners and the forecast they answer.
- 05
Carry out and re-forecast
Send each owner its approved action and date, and chase it to done. Re-run the forecast at each monthly close; a gap that widens goes back to the chief financial officer with the next actions.
- Email Inbox
- Revenue plan and actuals
What counts as complete
Each segment forecast below its plan has approved cost actions sized to the gap, each done or with an owner and a date.
Decisions and exceptions
- Guidance to investors stays with the chief financial officer and the board.
- Cost actions that affect staff or sites go through the company’s own review.
- A forecast that moves on one week’s data goes to the finance lead before anyone acts on it.
What to measure
- Forecast error by segment and month
- Days from a miss to an approved action
- Cost removed against the revenue gap
- Actions done by their date
Establish the baseline and review period before launch. Compare completed cases, unresolved work and reviewer corrections against the same scope.
The agent’s tool basket
OneShot gives its agents the tools to analyze records, communicate, research and act on authorized business data. The platform carries the workflow from the first action through to the recorded result.
Revenue plan and actuals
Read monthly revenue and weekly volume by segment with the operating plan; record the approved forecast and cost actions.
Workflow pricing
Scope the full workflow around your volume, business systems and required outcome.
Discuss workflow pricing →