Loading
Because it is a number with no workings. It arrives weighted, adjusted by a sales director's judgement, and reconciled against finance in a spreadsheet nobody keeps.
When it misses, the post-mortem cannot separate optimistic deals from a genuine market change, so the same conversation happens next quarter.
Weighted and unweighted side by side, with the stage weights visible and the deals behind every figure one click away.
Because won deals open projects and projects bill in Books, the pipeline is traceable through to invoiced revenue rather than stopping at close.
It will not tell you whether a deal is real. Stage weights are averages, and the rep's judgement about a specific customer is usually better.
It also will not replace the conversation about pipeline quality. It gives it evidence.
The variance conversation becomes specific: these four deals slipped, for these reasons, and here is what delivery capacity looks like if they all land in the same quarter.
Revenue quality becomes visible too — which segments actually pay on time, and what each cost to deliver.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
Yes, through to invoiced value in Books.
Yes, via the roadmap in Loop.
Yes, per pipeline, and history is recalculated on the weights that applied.
Half an hour on your own numbers is usually enough to say whether Flow is the right place to start.