The problem
A media and events group had more than 100,000 contacts in its CRM, collected over years of events, reports and newsletters. Almost none of them had a usable job level or role recorded. Sales could not tell a chief executive from a student without opening each record.
This is in-house work, built by Rob Dale, who runs Above Threshold, in his employed role. The employer is not named because this is an internal system.
What was built
- Filling the gaps. Rules read each contact's job title and worked out seniority and role. Seniority went from under 2,000 contacts to more than 35,000, and role from under 2,000 to more than 22,000. Titles the rules were not sure about were held back, not guessed.
- A score for every contact. Each contact gets a score from 0 to 100: half for how well they fit, half for what they have done lately. Press, students and the general public are kept out of the sales list.
- A weekly re-score. Every week the scores are worked out again, and only the contacts that changed are updated. One recent run checked every contact and changed about 1,500.
- A morning list for sales. Each weekday the sales lead gets a short email listing the contacts that are ready for a call.
How it is kept safe
Every change to the live CRM follows the same three steps. First a dry run writes the proposed changes to a file. Then a snapshot of the current values is saved, so any change can be undone. Only then is the change applied. Nothing in this system emails a customer.
What it proves
Most small firms have the same problem at a smaller size: a contact list nobody trusts. The fix is the same too. Fill in what can be worked out, score what is there, and send one useful list to the person who makes the calls.