Your FP&A Team Has Opinions About the Sales Forecast and They Are All Skeptical

This is satire, although the forecast will be presented with enough confidence to qualify as policy. At 9:04 a.m., Sales submits a revenue plan showing a 47,000% increase in pipeline conversion, driven primarily by “momentum,” three unnamed enterprise prospects, and an account executive who has recently changed their LinkedIn banner to a photo of a mountain. FP&A thanks the team for the update, opens the file, and begins the ancient corporate ritual of being told it is negative.

The forecast arrives in its natural habitat: a slide

The Sales forecast is not a model. It is a statement of aspiration formatted in dark blue, with an arrow that becomes steeper after Q2 because “the market will know who we are by then.” The slide contains a single annual number, a quarterly breakout that does not equal the annual number, and a footnote reading: “Assumes normal deal velocity.”

No one can define normal deal velocity because the company has sold its product for fourteen months, changed pricing five times, reorganized territories twice, and spent the last quarter deciding whether its customers are mid-market, enterprise, strategic enterprise, or “enterprise-adjacent.” This is not a problem. It is a source of flexibility.

FP&A’s first task is to translate this commercial vision into the tiresome language of cash, headcount, gross margin, commission expense, implementation capacity, and dates. This is received as an act of hostility. A forecast that must reconcile to anything is widely understood to have lost its entrepreneurial spirit.

The questions FP&A is encouraged not to ask

• “Which opportunities are expected to close this quarter, and what has changed since last week?” This implies that last week’s forecast may have contained information.
• “What is the historical conversion rate by stage, segment, and deal size?” This introduces precedent, a known enemy of possibility.
• “Does the sales capacity plan support this bookings target?” This is particularly inflammatory if the company plans to hire the missing account executives after they deliver the missing bookings.
• “When does revenue begin, given implementation, procurement, security review, and the customer’s stated desire to revisit this in the next fiscal year?” This question is considered overly accounting-oriented, even when asked by the person responsible for explaining revenue timing to the board.
• “Why is the upside case now the base case?” This is a philosophical question and should be directed to a specialist in corporate optimism.

How the meeting proceeds

The VP of Sales begins: “We need Finance to be a partner.” Everyone agrees, because partnership is central to the process. In this context, partnership means taking the submitted forecast, retaining every number, adding no reserves, identifying enough operating expense to fund it, and explaining the resulting cash position without using words such as “shortfall,” “runway,” or “mathematically.”

The Head of FP&A asks whether the largest deal in the quarter has a signed order form. The room grows quiet. The sales leader explains that the customer is deeply engaged. The customer attended a webinar, accepted a calendar invitation for a discovery session, and has not formally rejected the latest follow-up email. The deal is therefore categorized as Commit, subject only to legal, procurement, budget approval, information security, executive sponsorship, product fit, timing, price, and the customer selecting the vendor.

The CEO enters halfway through and says, “Let’s not sandbag ourselves.” This is a valuable intervention. It establishes that the company’s planning process has only two permissible settings: sandbagging and believing.

A framework for productive skepticism

FP&A professionals who want to preserve both their credibility and access to lunch should avoid saying, “I don’t believe this.” Instead, use the company-approved formulations below. They communicate the identical message while allowing everyone to leave with a calendar hold for a follow-up.

1. “Can we align on the bridge from current pipeline to recognized revenue?” Translation: the annual target has appeared without parents.
2. “What would need to be true for this conversion assumption to hold?” Translation: several laws of probability may require revision.
3. “Should we distinguish management ambition from the operating case?” Translation: please stop making payroll contingent on vibes.
4. “Could we put the expansion cohort in a separately visible scenario?” Translation: these accounts have not agreed to expand.
5. “Let’s identify the leading indicators we will review weekly.” Translation: if this falls apart, we would like advance notice.

The forecast review becomes an interview process

Eventually, the dispute shifts from the forecast to FP&A itself. The team is asked whether it is “commercial enough.” This is a familiar hiring criterion for finance roles, especially at companies where commercial means agreeing that every late-stage deal is unique, every renewal is assured, and every variance can be corrected by adding a column called Upside.

Candidates for FP&A manager and director roles may recognize the pattern. During interviews, they are given a case study in which revenue is missing plan by a large amount and are asked how they would partner with Sales. The correct answer is not to recite a forecasting methodology. It is to show that you can separate four things without publicly insulting anyone: the target, the latest forecast, the deal-level evidence, and the actions management can actually take.

At a smaller company, this may mean building a simple weekly bookings-and-capacity view because the CRM is mostly memorial architecture. At a larger company, it may mean challenging definitions, inspecting stage movement, and keeping the board package from quietly treating pipeline as revenue. The title may be analyst, senior manager, director, or VP; the job is often the same: make uncertainty legible before it becomes a surprise.

The final compromise

After ninety minutes, the company reaches consensus. Sales will keep its original forecast. FP&A will publish a base case, an upside case, a downside case, a downside-downside case, and a “not for external circulation” case. Leadership will use the highest number in the board deck, the middle number for hiring, and the lowest number when discussing discretionary spend. Everyone will call this a single plan.

The skeptical FP&A team has not killed the forecast. It has done something less glamorous and more useful: made clear which assumptions are carrying it. That is the real work. A plan does not become pessimistic because Finance asks what has to happen for it to work; it becomes usable.