Lead Scores Worth Routing Work On

What it is for

A readiness check for predictive scores in a CRM: what the model is trained on, whether there is enough closed history, which fields leak the outcome, and a shadow period before anything is routed on it. Use it when someone proposes prioritising work by a score. It prevents a model that has quietly learned your process instead of your customers.

The skill Copy

Before a prediction score decides who gets called first, prove it is built
on something real.

1. Find the field the prediction is trained on and read a hundred records of
   it by hand. If reps fill it late, skip it, or use it to mean two different
   things, the model is learning your team's habits, not your customers.
2. Check how much finished history you have, with both outcomes present. A
   young pipeline, or one where almost nothing is ever marked lost, cannot
   produce a useful score - it will simply predict the majority and look
   accurate doing it.
3. Remove the fields that leak the answer. Anything only filled in after a
   deal closes will make the model look brilliant in testing and useless on
   open deals.
4. Look at which fields the prediction leans on hardest. If the top signal is
   operational - record owner, a lead source spelled three ways, a dead
   campaign name - fix the data before you trust the ranking.
5. Hold the score at arm's length for one full sales cycle. Log it, do not
   act on it, then compare what scored high against what actually closed.
6. Only then wire it to something reversible: a sort order, a view, a
   reminder. Never to something that cannot be undone - deleting a lead,
   closing a case, hiding a record from a queue.
7. Re-check it every quarter. A model trained before a price change, a new
   market or a new team is describing a company that no longer exists.

The failure this prevents: a confident-looking score that is really ranking
leads by which rep owns them, quietly starving everyone else of follow-up.

How to install it Copy

1. Open the tool and start a new conversation, project or template.
2. Paste the text below wherever the tool keeps standing instructions
   — usually called system prompt, instructions, or persona.
3. Save it so it applies to every run rather than a single message.

Did it work for you?

Where it came from