Read a sample: 1. The Forecast as a Leadership Practice
The Monday forecast meeting has reached the opportunity everyone wants to discuss. It is large enough to change the quarter, close enough to feel urgent, and uncertain enough that nobody quite wants to say so.
The sales manager asks, “Are we still on track?”
The account executive says, “Yes. They seemed positive last week.”
The manager enters the deal in the forecast. The executive moves on to the next call. A senior leader sees a reassuring number.
What just happened was not necessarily deception or carelessness. The seller may genuinely believe the buyer intends to proceed. The manager may be trying to keep the team focused. Yet an important distinction has disappeared: a positive conversation has been treated as evidence of a decision, and a hoped-for outcome has become part of a prediction.
Forecasting is often presented as a technical exercise involving stages, probabilities, and calculations. Those tools matter, but the quality of the number starts earlier—with what people notice, what they are willing to say, and how leaders respond when the answer is inconvenient.
A sales forecast is therefore a leadership practice. It is a disciplined conversation about what the team currently believes will happen, why it believes that, and what could change the answer.
Sales teams routinely work with targets, pipelines, and forecasts. Each has a legitimate role. Trouble begins when they are treated as interchangeable.
A target states what the organization wants to achieve. It may reflect a growth plan, a budget, a quota, or another business objective. A target can be ambitious and useful even when the current pipeline does not yet support it.
A pipeline is the collection of opportunities the team is pursuing. Its total value describes the potential revenue represented in those records, subject to the quality of the information entered. It does not mean that every opportunity will close, close on time, or retain its stated value.
A forecast is a current assessment of the revenue expected to close in a defined period, based on available information and explicit judgment. It should change when meaningful facts or assumptions change.
Imagine a hypothetical team with a quarterly target of $500,000 and open opportunities totaling $700,000. Neither number tells us the forecast. The team might reasonably expect $400,000, $500,000, or another amount, depending on buyer progress, timing, deal values, and unresolved risks.
If the forecast is below target, leadership has a planning problem to address. It may need to create more opportunities, accelerate work where acceleration is genuinely possible, adjust resources, or communicate a likely gap. Raising the forecast to match the target does none of those things. It makes the gap harder to see.
The opposite problem also occurs. A manager may deliberately keep the forecast low to avoid a public miss. That number can be just as misleading as an inflated one. Leaders need a candid view in both directions: good news that can be supported and bad news early enough to act on.
This does not mean a forecast is a promise. Complex purchases depend on people and events outside the seller’s control. An honest forecast is a reasoned view of the future, not a guarantee about it.
Throughout this book, we will follow a hypothetical business-to-business sales team led by Maya Chen. Maya manages three account executives: Daniel Ortiz, Priya Shah, and Lena Brooks. Their company sells an annual business software subscription, and the figures in their opportunity records represent the expected value of the first year’s agreement.
The team is reviewing opportunities expected to close in the current quarter. Its hypothetical quarterly target is $500,000. At the start of Maya’s first review, five opportunities are visible in the summary she brings to the meeting.
Intentionally incomplete initial snapshot — hypothetical current-quarter opportunities
The table is a starting snapshot, not a dependable inventory or a forecast. It omits next actions, and the stage labels and quarter-level dates have not yet been checked against buyer evidence. It also contains only the five records in Maya’s meeting summary. When the team inventories the underlying system in the next chapter, it finds a sixth record that was not included in this summary; that discovery does not change the five-record total shown here.
Maya could divide $700,000 by the $500,000 target and conclude that the team has enough pipeline to succeed. That calculation would describe the size of the snapshot relative to the target. It would not establish whether the buyers are ready to make decisions this quarter, whether the values remain appropriate, or whether the records represent distinct, active opportunities.
The people behind the records offer a more useful starting point.
Daniel is an experienced seller with strong relationships and a habit of keeping prospects engaged. He believes Acorn Logistics has a compelling need, but his most recent discussion was with an operational contact rather than the person who would approve the purchase. Driftwood Retail has received a proposal, though Daniel is not yet sure how the buyer’s internal review will work.
Priya is meticulous about commercial details. Beacon Health has discussed terms with her, but a discussion of terms is not the same as final approval. At Elm Financial, her contact has expressed enthusiasm while another participant has raised questions about implementation.
Lena joined the team more recently. Cedar Manufacturing is evaluating the software, and her main contact has been responsive. Lena is less certain about who else must be involved before…