Every sales organization forecasts. The only question is whether the forecast lives in the system where the deals live, or in a spreadsheet that was accurate the moment it was exported and fiction ever since. Dynamics 365 Sales ships a forecasting module that reads the pipeline directly — same opportunities, same amounts, same owners — and turns the monthly number ritual into a live grid.
The forecast grid
Each row is a seller (rolling up a hierarchy if you have one); the columns are the categories that matter in any forecast conversation: Quota, the committed target; Won, what is already in the bank this period; Committed and Best case, the seller’s judgment about open deals; Pipeline, everything else still breathing; and the computed truth-tellers — Gap to quota and Pipeline coverage ratio. That last pair is where forecast reviews should start: a gap with a coverage ratio under 2–3× is a problem no amount of optimism fixes, and the grid does that math for you every time it recalculates.
Where do Committed and Best case come from? From the opportunities themselves — each deal carries a forecast category, so a seller manages their forecast by managing their deals. The small pencil icons in the grid allow manual adjustments on top, and adjusted values are marked so a manager always knows judgment from arithmetic.
Drill down to the story
A number you cannot decompose is a number you cannot trust. Expand any row and drill down — by account here — and the summary splits into its parts: which customers carry the quarter, which are all pipeline and no commitment. Clicking further shows the underlying opportunities themselves, so the review conversation moves from “why is your number low” to “let’s look at the three deals that make or break it” without anyone opening a different tool.
Configured, not built
Forecasts are defined by an administrator in App Settings: choose the hierarchy (territory or manager rollup), the fiscal calendar, and which opportunity fields feed which columns. The period selector then walks quarter by quarter, and Recalculate data pulls the latest pipeline on demand — the grid also refreshes itself on a schedule, which is why the header admits when it last updated. Snapshots preserve history, so “what did we forecast three weeks ago versus what closed” becomes an answerable question — the one that actually improves forecast discipline over time.
The quiet win of in-system forecasting is behavioral: when the forecast is computed from the pipeline, the only way to fix the forecast is to fix the pipeline — update close dates, move dead deals out, categorize honestly. The spreadsheet let people negotiate with the number. The grid makes them negotiate with the deals.
