Loading
Because a renewal is not a sale. It has a different shape, a different probability curve and a different owner, and running both through one funnel makes the forecast wrong in a way that is hard to see.
Worse, mixing recurring and one-off value in a single column double-counts new business every quarter it renews.
New business, expansion and renewal run as their own pipelines with their own stages and probabilities. Value and recurring value are separate fields, so you can total new business without the subscription arriving twice.
Renewal dates are records, so a renewal appears in a queue ninety days out with an owner rather than surprising somebody.
It does not meter usage or bill per seat automatically. Books handles the recurring schedule; product usage comes from your own instrumentation through the API.
And it will not predict churn. It shows the signals — support load, payment behaviour, contact changes — on one record, and leaves the judgement to a person.
Desk's ticket history and open escalations are on the same account, and Books shows whether they pay on time. Both are visible before the call rather than after it.
That is usually the difference between a renewal conversation about price and one about the two escalations nobody resolved.
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, they are separate fields, which stops the double-counting that makes most SaaS pipelines wrong.
Yes, their own pipeline entirely.
Yes, on the account timeline, because Desk writes to the same record.
Half an hour on your own numbers is usually enough to say whether Flow is the right place to start.