A Client Wanted Full Automation, What They Actually Needed Was Partial

The ask was straightforward: "automate our lead qualification so sales reps don't have to manually score every inbound lead." The underlying frustration, once I actually sat with the sales team for a day, was different — reps didn't mind scoring leads, they minded that the scoring criteria kept changing without anyone telling them, so half their time went to re-litigating which leads mattered.

Full automation would have locked in a scoring model trained on historical data that was, by the sales team's own account, already outdated. That's a recipe for confidently automating the wrong decision at scale instead of inconsistently making the wrong decision by hand.

What we built instead

An automated first-pass score using firmographic and behavioral signals, surfaced to the rep with the reasoning attached, plus one human decision point: accept, override, or flag for a criteria review. The override reason got logged and reviewed monthly, which is also how we caught that the scoring weights needed adjusting for a new product line within six weeks of launch — something a fully automated system would have just silently gotten wrong.

Full automation removes the human from the loop. Partial automation removes the tedium and keeps the signal the human was actually providing.

• Automated: initial scoring, routing, and the tedious data lookup across three systems reps used to do manually.
• Kept human: final accept/override decision, with a logged reason.
• Added: a monthly review of override patterns to catch model drift before it compounded.

The client's original request wasn't wrong, exactly — it was aimed at the wrong layer. "Automate this" is often a proxy for "stop making me do the boring part," and the boring part is rarely the whole process. Finding the actual boring 70% took longer than building the automation did, and it's the part of the engagement that mattered most.