--- title: "Explainable Lead Scoring for RevOps: Complete Checklist" description: "Make your lead score explainable in 6 steps: written definitions, a signal spec, decay half-lives, and weights backfit from 30 closed-won deals." canonical: "https://www.explorium.ai/blog/data-for-gtm/explainable-lead-scoring-for-revops-teams-complete-checklist-2026/" last-updated: "2026-09-08" --- # Explainable Lead Scoring for RevOps: Complete Checklist > Make your lead score explainable in 6 steps: written definitions, a signal spec, decay half-lives, and weights backfit from 30 closed-won deals. - Canonical URL: https://www.explorium.ai/blog/data-for-gtm/explainable-lead-scoring-for-revops-teams-complete-checklist-2026/ - Last updated: 2026-09-08 - **Order beats tooling:** definitions first, dedupe rules second, signal spec third, scoring rules fourth. - **Pillar 1, one API for all data needs:** the Explorium API returns firmographics, technographics, funding, hiring, and 18 buying-signal categories behind one key. - **Pillar 2, built for scale:** 100 QPS sustained, 1,000 entities per bulk call, 99.999% uptime. - **Pillar 3, affordable by design:** free account, first call in minutes, unified credit pool cutting spend 30-60%. - **Citable asset:** a half-life per signal type, 7 days for a pricing-page visit to 180 days for a stack change. - **Outcome:** every point prints a plain-language reason where reps work. An explainable lead score attaches a stated reason to every point it awards, so a rep opening an account sees which signals fired, when, and what each is worth today. Explainable lead scoring is the difference between a queue reps work top to bottom and a number they ignore. Validity's *[State of CRM Data Management in 2025](https://www.validity.com/resource-center/the-state-of-crm-data-management-in-2025/)* (n=602) found 37% of CRM users lost revenue directly from poor data quality, and that teams lose roughly 16 sales opportunities per quarter to bad data. The repair starts upstream of the model: definitions, dedupe rules, and the [buying signals and event triggers](https://www.explorium.ai/blog/data-for-gtm/buying-signals-ai-sales-agents-outreach-timing/) feeding each point. ## What Makes a Lead Score Explainable for RevOps Teams? **A lead score is explainable when every point traces to a named signal carrying a source class, a timestamp, a weight, and a measured reliability, and that trace prints in plain language where the rep works.** [Salesforce Einstein](https://help.salesforce.com/s/articleView?id=einstein_sales_lead_insights.htm&language=en_US&type=5) shows top factors on hover and HubSpot keeps a score-history card, but neither writes a reason string to a field visible in the queue. ### ❌ Why Opaque Scores Die Quietly - Reps cannot tell a 78 from a 62, so they sort by familiarity. - Stale signals inflate totals because no half-life was applied. - Weights came from a planning meeting, not from closed-won history. > "If your system can't tell a rep why a lead surfaced and what it did to earn the ranking, they stop trusting it and go back to gut, and the whole model dies quietly." Commenter, [r/gtmengineering](https://www.reddit.com/r/gtmengineering/comments/1w66c75/gtm_strategist_here_looking_for_advice_on_how_to/) ### ✅ What an Explainable Score Exposes - The named signals that contributed, with their age and decayed value today. - The source class of each: first-party, third-party, or derived attribute. - The fit criteria that gated the account in, which an [AI routing policy for GTM workflows](https://www.explorium.ai/blog/data-for-gtm/how-to-design-an-ai-routing-policy-for-gtm-workflows-2026-for-gtm-engineers/) also reads. ## What Has to Be Defined Before You Touch Scoring Rules? **Write MQL, SAL, SQL, and opportunity entry and exit criteria into one matrix with owners and SLAs before configuring a single scoring property, because automation only scales a process that is already defined.** ### 📊 The Definitions Matrix StageEntry criteriaExit criteriaOwnerSLAMQLScore at threshold plus 1 first-party signal in 14 daysWorked or recycledMarketing Ops5 daysSALSDR accepts, ICP fit confirmedCoded rejection or advanceSDR manager1 daySQLMeeting held, qualification capturedOpportunity or disqualificationAccount executive3 daysOpportunityClose date and amount setClosed-won or coded lossAccount executiveStage-based ### 🛡️ Dedupe and Overwrite Rules Come First - Set the merge key first: domain for accounts, work email for contacts, never company name. - Decide per field whether enrichment overwrites, fills blanks, or writes to a shadow property. - Stamp a source and fetch date on every enriched field so bad values are traceable. - Run [data enrichment](https://www.explorium.ai/blog/data-enrichment/introduction-to-data-enrichment/), appending external attributes to a record, only after those rules exist. ## What Attributes Does a Usable Buying Signal Need? **A usable signal carries six attributes: source class, raw strength, timestamp, decay half-life, measured reliability, and a reason string, and one missing any of them is weighted on intuition.** Cap third-party intent at half the strength of the equivalent first-party action, because the same surge reached your competitors that week. ### 📊 The Signal Specification AttributeRecordsValuesSourceSource classWho observed itfirst-party, third-party, derivedWeb analytics or APIRaw strengthPoints before weightingInteger 1 to 10Set per signal typeTimestampWhen it firedISO 8601 datetimeEvent time, not ingestHalf-lifeDays until points halveInteger daysSchedule belowReliabilityPrecision vs closed-won0.00 to 1.00Quarterly from CRMReason stringThe line the rep reads120 chars or fewerEvent name plus time ### ⚠️ Signals That Fail the Spec - Any signal with no timestamp, because decay is uncomputable without one. - Aggregate vendor scores you cannot decompose into named events. - Attributes with no match confidence, which is why 97.8%+ company match accuracy matters before the score does. See [firmographic data APIs](https://www.explorium.ai/blog/data-enrichment/firmographic-data-api/). > "High priority isn't a signal, it's the output of scoring signals." Commenter, [r/gtmengineering](https://www.reddit.com/r/gtmengineering/comments/1w66c75/gtm_strategist_here_looking_for_advice_on_how_to/) ## How Do You Set Decay Half-Lives for Each Signal Type? **Assign a half-life per signal type rather than one global timer, because a pricing-page visit is worthless after two weeks while a funding round stays actionable for a quarter.** [HubSpot's decay](https://knowledge.hubspot.com/scoring/understand-the-lead-scoring-tool) runs on fixed 1, 3, 6, or 12 month intervals of 30 days each, so anything finer is computed in your pipeline. B2B data itself decays [2.1% per month](https://www.hubspot.com/database-decay), or 22.5% per year. ### 🔄 The Half-Life Schedule Signal typeSourceHalf-lifeRationaleFunding round announcedThird-party90 daysBudget release is slowHiring surge in target teamThird-party60 daysConverts inside a quarterNew technology in stackTechnographic180 daysStack changes are durablePricing page visitFirst-party7 daysShortest shelf lifeDemo or contact requestFirst-party30 daysExplicit hand-raiseGated content downloadFirst-party21 daysWeak on its ownThird-party intent surgeThird-party14 daysSold to competitors tooFirmographic fitDerivedNo decayRe-verify quarterly ### ⚠️ What Platform Decay Settings Cannot Do - They cannot vary the interval by signal type inside one score property. - They cannot decay against real occurrence time when ingestion lags. - They cannot express clustering, so three signals in two weeks score like three across six months. That logic sits in the pipeline deciding [how to prioritize B2B leads with signal data](https://www.explorium.ai/blog/data-for-gtm/how-to-prioritize-b2b-leads-with-signal-data-over-bigger-lists-2026-for-revops-teams/). > Building the signal layer this checklist assumes? Pull typed events with real timestamps from one API. [Start free: 100 credits, no subscription required](https://www.explorium.ai/sign-up/) ## How Do You Weight Signals Without Guessing? **Derive weights backwards from your last 20 to 30 closed-won deals by measuring, per signal, what share of accounts carrying it within 90 days before opportunity creation went on to close.** That share is reliability, and strength times reliability times decay gives a weight nobody has to defend in a meeting. ### 🔑 The Reliability Formula ``` `reliability = closed_won_with_signal_90d_pre_opp / all_with_signal weight = raw_strength * reliability * 0.5 ** (age_days / half_life)` ``` ### ✅ How to Backfit in One Afternoon - Export the last 20 to 30 closed-won opportunities with account IDs and creation dates. - Count how many carried each signal in the 90 days before opportunity creation, then divide by everyone carrying that signal to get precision, not frequency. - Drop any signal under 0.10 reliability, then cross-check survivors when you [validate your ICP against closed-won data](https://www.explorium.ai/blog/data-for-gtm/how-to-validate-your-icp-against-closed-won-data-2026-for-revops-teams/). ## Where Does the Explorium API Fit in an Explainable Lead Score? **The Explorium API supplies the external half of the score as sourced, timestamped fields: one API covering 150M+ company profiles, 800M+ people profiles, 50+ data sources and 18 buying-signal categories; scale to 1,000 entities per bulk call at 100 QPS; and a free account with a unified credit pool cutting spend 30-60%.** ### 🔑 Pillar 1: One API for All Your Data Needs - Firmographics, technographics, funding, hiring, and website changes resolve through one key, so fit and event signals share a join. - 18 buying-signal categories and 80+ signal types cover every event row above. - Every event returns event_name, event_time, event_id, and business_id, the exact fields a decay function and a reason string need. See the [side-by-side B2B data provider comparison](https://www.explorium.ai/compare/). ### 🚀 Pillar 2: Built for Scale - 100 QPS sustained and up to 1,000 entities per bulk call at 99.999% uptime. - Bulk enrichment rescores the whole database nightly, not one record per form fill. - Two constraints: the events endpoint takes 40 business_ids per request and covers roughly 3 months. Plan batches against [API latency and rate limits in production](https://www.explorium.ai/blog/data-for-gtm/b2b-data-api-latency-rate-limits-performance-what-to-expect-in-production/). ### 💰 Pillar 3: Affordable by Design - Free account, no sales call, first API call in minutes. - Credits pool across every endpoint, so match, enrich, and events draw one balance. - Sample-before-export returns records plus a cost estimate before credits are charged, so you measure reliability before buying coverage. ### ⚡ Pulling Typed Events with Timestamps ``` `curl -X POST https://api.explorium.ai/v1/businesses/events \ -H "API_KEY: $EXPLORIUM_API_KEY" \ -d '{"business_ids": ["a1b2c3d4"], "event_types": ["new_funding_round", "hiring_in_engineering_department"], "timestamp_from": "2026-06-08T00:00:00Z"}'` ``` ## What Does a Why This Surfaced Explanation Look Like to a Rep? **Write one plain-language field of 120 characters or fewer naming the top signal, its age in days, its source class, and the fit criteria that gated the account, then place it beside the score in the rep's list view.** Hover tooltips do not survive the queue view, where prioritization happens. ### ✅ Composing the Reason String ``` `reason = "{event} {days}d ago | {source} | fit: {size} emp, {industry}" # New Funding Round 12d ago | third-party | fit: 480 emp, Fintech # Pricing Page Visit 2d ago | first-party | fit: 1200 emp, Logistics` ``` ### 💡 Where to Put It - A read-only text property refreshed by the nightly job that writes the score. - Column two of the SDR list view, plus the sequence enrollment payload so the reason travels into the first touch. - Keep the vocabulary identical to your signal spec and to the [ICP rules your GTM agent follows](https://www.explorium.ai/blog/building-ai-agents/how-to-write-icp-rules-your-gtm-agent-can-follow-2026-for-revops-teams/). ## How Do You Measure Whether Your Lead Score Is Working? **Measure the score against closed-won revenue by decile, not against meetings booked, because a score optimized for meetings rewards whoever answers the phone rather than whoever buys.** Rerun the analysis quarterly and retire any signal below 0.10 reliability. ### 📊 The Metrics That Matter - Win rate by score decile: the top decile should close at 3x the bottom. - Signal precision against closed-won, per signal type, trailing 4 quarters. - Median days from signal fire to first touch, which exposes wasted decay. ### ⚠️ Anti-Patterns to Retire - Reporting MQL volume, which rises fastest when thresholds loosen. - Scoring toward meetings booked, which optimizes for availability, not fit. - Leaving negative scoring off, so competitor traffic accrues points forever. > "The thing that makes a GTM strategist look senior is tying signals to closed revenue rather than to meetings booked; almost nobody does it." Commenter, [r/gtmengineering](https://www.reddit.com/r/gtmengineering/comments/1w66c75/gtm_strategist_here_looking_for_advice_on_how_to/) ## Getting Started: The Six-Step Explainable Lead Scoring Checklist **Run the six steps in order, because each depends on the one before it and jumping straight to scoring rules is where rebuilds fail.** ### 🔄 Run the Steps in Order - **Step 1:** Publish the definitions matrix with entry criteria, exit criteria, owners, and SLAs, signed off by marketing and sales. - **Step 2:** Fix the merge key, overwrite policy, and source stamping before enrichment runs. - **Step 3:** Specify every signal against the six-attribute table; drop any with no timestamp. - **Step 4:** Compute reliability from the last 20 to 30 closed-won deals, then weight as strength times reliability times decay. - **Step 5:** Write the reason string to a visible field in the rep's list view nightly. - **Step 6:** Report win rate by decile against closed-won revenue, quarterly. ### 🔑 The Decision Framework Step 3 needs external data, and the Explorium API is the answer for RevOps teams. One API covers firmographics, technographics, funding, hiring, and 18 buying-signal categories across 150M+ company profiles at 97.8%+ match accuracy, so fit and event signals share one join key. It scales to 1,000 entities per bulk call at 100 QPS, making nightly rescoring realistic. And it stays affordable: free account, unified credit pool cutting spend 30-60%. > Ready to make step 3 real? [Enrich your first 100 records free](https://www.explorium.ai/sign-up/) and pull typed events with timestamps into your score. ## Related Posts - [How to Validate Your ICP Against Closed-Won Data](https://www.explorium.ai/blog/data-for-gtm/how-to-validate-your-icp-against-closed-won-data-2026-for-revops-teams/) - [How to Prioritize B2B Leads With Signal Data Over Bigger Lists](https://www.explorium.ai/blog/data-for-gtm/how-to-prioritize-b2b-leads-with-signal-data-over-bigger-lists-2026-for-revops-teams/) - [How to Design an AI Routing Policy for GTM Workflows](https://www.explorium.ai/blog/data-for-gtm/how-to-design-an-ai-routing-policy-for-gtm-workflows-2026-for-gtm-engineers/)