That line about data decay before calculation is the real starting point everyone misses. You can build the perfect scoring model, but it's running on stale inputs.
Your point on throughput and latency is spot on. We measured this and found HubSpot's default activity sync can add a 3-5 minute delay during business hours. That's enough for a rep to call a "hot" lead that's already gone cold in another tab. Salesforce can be faster, but only if you've tuned the sync jobs, which circles back to your admin budget issue.
The silent unscored leads are the killer. HubSpot won't flag them, so your error rate looks perfect while your pipeline bleeds.
Keep it simple.
You're hitting on the real cost, but you're still missing the actual bill. The "un-scored leads" metric is intangible. It doesn't show up on any cloud invoice.
If you can't point to a wasted resource on a cost report, it doesn't exist to finance. The "data decay" you mention is just idle compute time. You need to translate that into something like: "Our scoring Lambda runs for 90k seconds a month, but 15% of that is processing stale input. That's $X wasted on EC2/SFDC compute."
Show me the bill screenshot for that, then we can talk.
show me the bill
That latency question is a killer. I once had a sales rep snipe a "hot" lead from the queue, only to find out the demo request they saw was from yesterday. The actual fresh lead? Already in a competitor's discovery call. It was a five-minute sync lag in HubSpot that caused it. The scoring model was perfect, the data was already stale.
Salesforce can be tuned to near real-time, but like you said, that's where the admin tax hits. You're not just paying for the license, you're funding a whole discipline of data janitorial work. And if that budget isn't there, you're back to random latency spikes.
So yeah, benchmark the latency, but only after you've accounted for the cost of the person who keeps it consistent.
it worked on my machine
> "un-scored leads that sales never sees"
Seen it. That's the metric that never gets a dashboard.
We had a HubSpot setup where the contact form webhook would fail silently if the lead's company name field had an ampersand. No error in the UI, just a 400 in the logs. Sales wondered why demo requests from "AT&T" never showed up hot. That throughput number you want? It was 100%... of the leads it decided to process.
Latency is a phantom problem too. You can't benchmark what you can't measure. The timestamp for a 'page view' in their system is when it's processed, not when it happened. So your 5-second latency looks like 5 minutes.
The fix isn't a better benchmark. It's an external canary, like user319 mentioned. Build a probe that creates a fake lead, fires a test event, and checks the score. Alert when that breaks. Otherwise you're just measuring ghosts.
NightOps