Loading
Because it only feeds a report. Updating a stage benefits somebody else's Monday meeting, so it happens on Friday afternoon in a batch, from memory, and the forecast is built on it anyway.
The rep is not lazy. They are correctly observing that the CRM takes from them and gives nothing back.
The record a rep updates is the one delivery, support and finance read. Winning a deal opens the project; the invoice bills what was quoted; support sees what was promised.
So the stage change is not admin — it is how the handover happens, which is the only durable reason anyone maintains a CRM.
It will not make people update a record that does nothing for them, and no CRM does. What it does is make the update useful to the person making it.
It also will not forecast for you. It shows what the pipeline says; the judgement about which deals are real stays with the manager.
The forecast becomes defensible because it shows its arithmetic: weighted beside unweighted, with the hygiene rules that flag the deals nobody has touched in three weeks.
Handover stops being a document. Delivery starts from the contracted lines rather than a reading of the proposal.
They use it where the update triggers something they want — the handover, the invoice, the entitlement.
Yes, with their own stages and entry criteria.
It shows the same arithmetic, with the deals behind each number.
Half an hour on your own numbers is usually enough to say whether Flow is the right place to start.