Your sales pipeline is not next month’s revenue forecast

The sales meeting sounds encouraging. There is plenty in the pipeline, several proposals are “almost there”, and the team expects a strong month. Finance asks how much revenue to plan for. The answer depends on which spreadsheet, salesperson or date field you use.

For an SME or mid-market business, that uncertainty affects practical decisions: purchasing stock, allocating delivery capacity and deciding which gaps need management attention.

A pipeline shows potential business. A useful forecast explains what the company reasonably expects in a defined period, why it expects it and what could change. Getting there requires shared judgement and reliable records.

Agree what you are forecasting

Start the meeting with the measure. Are you forecasting orders won, revenue, invoices raised or money collected? These events can happen in different periods.

An order signed next month may be delivered later. A project may run across several months. A raised invoice does not tell you when the customer will pay. Ask finance to agree the revenue basis and keep a separate cash view where needed.

Record the period, the scope and the treatment of existing orders. If your revenue forecast combines order-book delivery with new opportunities, show those components separately and check that a deal does not remain in both after it is won.

The first improvement may simply be replacing an ambiguous “Forecast” heading with a specific measure and date range.

Separate possibility from commitment

A proposal sent is evidence of activity. It is not evidence that a customer will buy this month.

Agree a small set of confidence categories that people can explain consistently. For example, distinguish credible potential from deals the team expects to win in the period, and show additional upside separately. These are planning judgements, not guarantees.

For each significant opportunity, ask: what has the customer confirmed, what remains unresolved, and what is the next dated action? Budget approval, procurement, technical acceptance and an agreed delivery plan may each matter more than a salesperson’s percentage.

In an illustrative equipment supplier, a £60,000 opportunity could look attractive while the buyer has not approved funding. Keeping it visible as upside is more informative than allowing it to inflate the main planning assumption.

Make the dates believable

Review deals whose expected close dates have passed, whose dates repeatedly move to month-end, or whose delivery timing has not been confirmed.

Ask what changed in the customer’s buying process. Updating a date without an explanation can make an old opportunity look fresh while leaving its uncertainty intact.

Then connect sales timing with operational timing. If a deal is expected to close near the end of the month, can stock, capacity and acceptance requirements support the revenue assumed for that same month?

Microsoft’s Dynamics 365 Sales guidance shows that forecast rollups depend on selected amount and date fields.^[1] That makes field selection a business decision: a close-date view should not quietly be presented as a delivery-based revenue forecast.

Check which records are included

Before debating the total, inspect a few representative deals behind it. Confirm the value, currency, owner, category, date and whether the opportunity is still genuinely active.

Look for duplicate records, superseded proposals and closed opportunities left in an open category. Check whether renewals, recurring business and existing orders are handled consistently with the forecast’s stated scope.

Microsoft’s forecast configuration guidance separates the source records, their filters, the hierarchy used to group them and the forecast periods.^[2] If an entire team or seller appears to be missing, investigate those relationships and filters before concluding that the business has no pipeline.

Give corrections named owners and make them in the agreed source where possible. Repeatedly repairing an exported spreadsheet creates another version of the truth to maintain.

Review movement, not just the latest total

A forecast can remain unchanged even when the deals supporting it have changed completely.

Keep a dated snapshot of the agreed view. At the next review, explain the movement: new opportunities, won or lost business, value changes, confidence changes and deals pushed into later periods.

Make any management adjustment visible, with an owner and reason. There may be a valid judgement that is not yet reflected in a CRM field, but colleagues should be able to distinguish it from the underlying records.

After the period ends, compare the forecast with the actual result on the same basis. Investigate whether differences came from conversion, timing, scope or data quality. Use that learning to improve the next review rather than treating every miss as a sales-performance issue.

Build one forecast people can explain

Start with one team and one period. Agree the measure, inclusion rules, confidence definitions and owners before adding more charts or automated predictions.

A concise review should show the main planning assumption, the upside, the gap to target, the important dependencies and the actions assigned to resolve them.

The test is straightforward: can sales, operations and finance trace the number back to the same records and explain what needs to happen for it to materialise?

When they can, a CRM and reporting layer can make the review easier to repeat. The technology supports a shared commercial process; the team still owns the decisions.

Discuss your forecasting challenge

If your sales forecast still depends on disconnected spreadsheets and unexplained adjustments, discuss your sales reporting and forecasting challenge with Qubit. Start with the number you need to trust and the decisions it should support.