Lead Scoring and Anomaly Flagging From Your History
Lead scoring ranks enquiries from your record of deals won and lost. Anomaly detection flags transactions that do not fit your normal pattern, and a person reviews every result.
Scoring needs lost deals too
Scoring needs both outcomes. A CRM full of won deals teaches nothing, because the model has to learn what a poor enquiry looks like as well. Lost enquiries are often the ones nobody updated. Before scoring can start, your team closes them with a rough reason, such as not interested or went elsewhere.
What anomaly detection catches
- A discount well outside what that executive usually gives
- A vendor bill at a rate that has not applied since last year
- Stock movement at an hour when the warehouse is normally shut
- A customer whose ordering pattern changes sharply in one week
- A duplicate payment entered against the same invoice reference
A flag is not an accusation
Each of these examples can have an innocent explanation. A flagged entry goes to a reviewer with the reason it stood out, and the reviewer decides. Automatic blocking on a flag loses the team’s trust quickly, since one wrong block is remembered longer than many correct flags.
Frequently asked questions
Does lead scoring replace a salesperson’s judgement?
No. It orders the list. Your executive still decides who to call and what to say, and can mark a score as wrong. Those corrections feed the next round of training.
How much history do these models need?
It depends on the model. Scoring needs a few hundred closed enquiries, won and lost, as a workable start. Anomaly detection needs a year or so of normal transactions to learn what normal looks like.
Will this work with our CRM and ERP?
Where both allow a read, yes. The score is written back as a field, so your team sees it in the system they already use and not on a separate screen.
Can anomaly detection stop fraud?
No. It can surface patterns worth checking, which is a different thing. Deliberate fraud is designed to look normal, so the output is a prompt for internal audit and not a control.
Tell us what you need.
Share your requirements and one of our engineers will come back to you within one business day.
What happens after you share your requirements
- A senior engineer reads your answers. Nobody phones first.
- Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
- If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
- No call is booked and nothing is paid until you have read the note. Your details stay with us.
Start with your requirements
Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.
Share your requirements