Loading
Deal scoring gives every open deal a score from 0 to 100, calculated from rules your team writes — for example “a budget holder is named” or “no activity for 14 days”. Each rule carries a weight, and the deal shows exactly which rules fired, so reps and managers can see why a deal scored low and what would raise it. It is transparent, rule-based scoring, not a machine-learning model.
Because a score nobody can explain is a score nobody acts on. Reps discount it the first time it disagrees with them, and once discounted it never recovers.
Deal scoring applies rules you write to open deals — stage age, activity recency, whether a budget holder is named — and shows the score with the rules that produced it.
Each rule is a readable condition with a weight. The deal shows its total and the individual rules that fired, so a rep can see that the score is low because there has been no contact for 21 days.
A rule set flagging deals with no activity for 14 days and no scheduled next step surfaced 23 deals worth £180,000 that were technically in Proposal and practically inactive.
It scores what is recorded. A deal progressing through conversations nobody logs will score badly, which is a data problem the score makes visible rather than one it solves.
Pipeline reports can group by score band, assignment queues can prioritise by it, and Pulse can raise the ones that fall sharply between one week and the next.
| Gut feel & spreadsheets | Black-box predictive scores | Treepie Flow | |
|---|---|---|---|
| How the score is made | A rep’s judgement, updated when someone remembers | A model trained on history nobody can inspect | Rules you write, each with a weight you set |
| Explaining a score | Depends who you ask | Rarely possible | Every rule that fired is shown on the deal |
| Per pipeline | One sheet for everything | Usually one global model | A rule set for each pipeline |
| When it updates | Weekly, by hand | On the vendor’s schedule | On every change to the deal |
| What happens next | Nothing, until review day | An alert with no reason | Queues and reports reorder by score |
No. They are rules you write, weight and can read. That is the point of them.
Yes. Rule sets are defined per pipeline, because a renewal and a new logo stall for different reasons.
No. It surfaces the deal; what happens next is a person's decision.
Each rule is a condition on the deal with a weight. The score is the weight of the rules that are met, divided by the total weight of all rules, shown as 0–100.
Any field on the deal, its contacts or its activity: stage age, days since the last email or call, whether a next step is booked, deal value, whether a quote has been sent, or whether a contact with a given role is attached.
Whenever something the rules read changes — a logged call, a stage move, a new contact — plus a nightly pass for time-based rules such as stage age.
Yes. The score and the rules behind it sit on the deal, visible to anyone who can see the deal.
Ranges you name, such as Healthy (70+), Watch (45–69) and At risk (under 45). Reports and queues group deals by band.
Yes. Change weights in the sandbox and compare the new scores with the current ones on the same deals before switching.
Lead scoring ranks new leads by fit and behaviour before they have an owner. Deal scoring tracks the health of open opportunities that are already being worked.
No. It is part of Flow; the pricing page lists which plan each feature sits in.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.