Key Takeaways (TL;DR)
Most scoring builds start in the wrong place. Score accounts first, then leads. A great contact at a bad-fit account is still a bad-fit lead.
The model depends on field mapping decisions made before any scoring logic exists: which CRM fields sync from Clay, which get overwritten, and which only fill when empty.
Data costs money. Enrich and score your tier-one accounts before spending credits on tier-3 contacts nobody is going to call.
Intent and engagement scoring comes last, not first. It only works once fit data (account and contact) is standardized in your CRM.
A working lead scoring model Clay users can point to: 10,000-plus contacts, a broken 20-stage lifecycle fixed, and a tier system that fed an enterprise demo in its first week.
The GTM Engineering Company can build this exact model inside your own CRM, and then hand over a documented system at the end, so your team can scale outbound on top of it, without depending on our team to run it for you.
Table of Contents
Clay Lead Scoring: at a Glance
What Clay Lead Scoring Really Means?
Why Account Scoring Comes Before Lead Scoring?
Step 1: Mapping CRM Fields to Clay Company Enrichment
Step 2: Building Custom Account Scoring Criteria
Step 3: Tiering Accounts Before You Touch Contacts
Step 4: Mapping CRM Fields to Clay People Enrichment
Step 5: Defining What Makes a Good Contact
Step 6: Building the Scoring Model
Step 7: Adding Intent and Engagement Signals
Templates and Field Mapping Examples
Clay Lead Scoring Criteria for Target Buyers
Real Case Study for Clay Lead Scoring
Everything You Need to Know
Build Your Model with The GTM Engineering Company
FAQs About Clay Lead Scoring
Clay Lead Scoring: at a Glance
Stage | What Happens? | Where the Data Lives First? |
Account field mapping | CRM fields matched to Clay company enrichment fields | Clay table, then CRM |
Account scoring criteria | Custom signals defined: job postings, headcount by department, public data | Clay table |
Account tiering | Accounts sorted into tier 1, tier 2, tier 3 | CRM account object |
Contact field mapping | CRM fields matched to Clay people enrichment fields | Clay table, then CRM |
Contact scoring | Department, seniority, persona, skills, education compared | Clay table |
Intent and engagement | LinkedIn activity, form fills, product usage, job changes | CRM contact object |
What Clay Lead Scoring Really Means?
Clay lead scoring uses Clay to enrich contact and company data, then ranks contacts by fit against your ideal buyer – right before a rep spends any time on them.
Most teams treat this as a single step: pull a list, score it, done. That is not how it works in practice. It runs as 2 connected processes: account scoring first, contact scoring second.
The distinction matters more than most guides admit. A contact scoring model built on top of unscored accounts ranks people, not opportunities. You end up with a "great" VP of Sales at a company with 12 employees and no budget. The title looks right. The account does not fit.
This guide walks through both halves in the order they actually need to happen. Along the way, we’ll also cover: field mappings, scoring criteria, and the Clay automation logic that holds up once the model runs against real volume.
Why Account Scoring Comes Before Lead Scoring?
In most B2B companies, lead scoring gets built before account scoring. That is backwards, and it is the single most common mistake we see in these builds.
Here is the reasoning:
You will always have more contacts than accounts. A 50-person target account might have 30 people who could plausibly show up in your CRM. Data costs money to enrich, whether you are paying for Clay credits, a data provider, or engineering time.
Scoring every contact at every account, before you know which accounts matter, wastes budget on people who were never going to be prioritized anyway.
The fix is a fixed sequence:
Map account fields from your CRM to Clay's company enrichment.
Build custom account scoring criteria.
Tier your accounts.
Map contact fields from your CRM to Clay's people enrichment, scoped to your tier-one and tier-2 accounts first.
Build contact scoring criteria on top of standardized data.
Layer intent and engagement signals last.
Each step depends on the one before it. If you skip account scoring, your contact model has no foundation.
On the contrary, skipping field mapping might lead to the scoring model running on incomplete or duplicated data.
The rest of this guide follows that exact sequence.
Step 1: Mapping CRM Fields to Clay Company Enrichment
Before any scoring logic exists, you need a field mapping exercise between your CRM and Clay's company enrichment sources. Start with your CRM's account object. List every field that matters for scoring: industry, employee count, revenue band, technology stack, funding stage, or even headquarter locations.
For each one, check whether Clay's company enrichment can populate it, and from which provider.
3 key decisions come up for every field:
Overwrite: The Clay-enriched value replaces whatever is in the CRM, every sync. Use this for fields where Clay's data is consistently more current than manual entry, like employee count or funding stage.
Write only if empty: Clay fills the field only if it is currently blank. Use this where reps or marketing may have entered a value manually that you do not want an automation quietly erasing.
Do not write: Clay enriches the field inside its own table for scoring purposes, but the value never syncs to the CRM. Use this for fields that feed other automations downstream, where a sync could break something you are not looking at right now.
Getting this wrong is the most common reason a Clay automation breaks weeks after launch. A field that overwrites when it should have been write-only-if-empty erases a rep's manual notes.
On the contrary, a field that never syncs when it should have leaves a downstream workflow starving for data it assumes exists.
Once the mapping and the overwrite logic are both decided, you transform the data inside Clay and push it into the CRM. This is the moment the account record actually gets richer, not before.
Step 2: Building Custom Account Scoring Criteria
With clean, mapped account data sitting in the CRM, you can define what actually makes an account worth pursuing. This is where most scoring templates stop at generic firmographic filters, which isn't enough.
Custom account scoring criteria worth building in Clay include:
Job posting volume and keywords: How many open roles does the account have, and do the postings mention tools, initiatives or team structures that signal they are building toward something you sell.
Departmental headcount: How many people work in a specific function, like RevOps or Data, since that often predicts both budget and internal champion availability.
Publicly available signals: Press mentions, product launches, leadership changes, or funding announcements that tell you this account is moving, not sitting still.
These criteria are not guesses. Each one should come from your ICP definition, which sets the baseline for what "good fit" means before you ever assign a score.
Scoring without a defined ICP just measures how closely an account resembles your last few closed deals, which is a much noisier signal.
The underlying data for all of this comes from the enrichment layer you set up in Step 1. If that layer is inconsistent, every score built on top of it inherits the same inconsistency.
This is why data enrichment tools matter as much as the scoring logic itself.
A scoring model is only as reliable as the data feeding it.
Step 3: Tiering Accounts Before You Touch Contacts
Once account scoring criteria produce a number or a bucket, group accounts into tiers.
Three tiers is usually enough, and each one gets a different level of enrichment and sales treatment:
Tier 1: Full contact enrichment and scoring first. Reps treat these as already having passed a fit bar.
Tier 2: Enrichment and scoring follow once tier one is stable. Reps treat these as strong but secondary.
Tier 3: Lighter enrichment, or none at all, until an account moves up. Reps treat these as speculative.
This is the point where data cost control actually matters. Enriching every contact at every account regardless of tier burns credits on people connected to accounts that were never going to close.
If you are running this against any real volume, tiering first is how you save Clay credits without cutting corners on the accounts that matter.
Tiering also sets expectations for sales. That context changes how a rep opens a conversation, and it should.
Step 4: Mapping CRM Fields to Clay People Enrichment
With accounts tiered, repeat the field mapping exercise from Step 1, this time for contacts.
Map your CRM's contact fields to Clay's people enrichment sources: job title, department, seniority, LinkedIn URL, email, phone.
The same 3 decisions apply here as they did for the account data:
overwrite
write only if empty, or
do not write
Contact records carry more manual edits than account records, though. Reps update titles and notes directly, so the write-only-if-empty rule shows up more often here than it did at the account level.
Scope this enrichment to your tier-1 and tier-2 accounts first. This is the general contact enrichment pass: get every relevant contact at your prioritized accounts into a standardized, complete state before comparing anyone to anyone else.
Once the mapping is confirmed, push that data into the CRM. Only after every contact at your priority accounts has been enriched can you start comparing them against each other in a meaningful way.
Comparing an enriched contact to a contact still missing half its fields produces a scoring model that is really just measuring data completeness, not fit.
Step 5: Defining What Makes a Good Contact
Once contact data is standardized, you can define what "good" actually means for a person, not just an account.
Common criteria for a scoring model at the contact level:
Department and function: Does this person sit in a team that would actually use or buy what you sell.
Seniority and title: Manager, director, VP, or C-level, mapped against your typical buying committee.
Persona fit: Does the role match a defined buyer persona, not just a generic title keyword match.
Skills, awards, or education: Specific credentials, certifications or academic background that correlate with faster adoption or stronger internal advocacy in your past deals.
This is where a lot of Clay lead scoring criteria for target buyers gets built sloppily. Title keyword matching alone misses people with non-standard titles who function as the actual decision maker.
Combining title, department, and seniority into a single weighted check produces a more accurate signal than any one of those fields alone.
Step 6: Building the Scoring Model
With standardized, organized contact data sitting in your schema, you can build the actual scoring model.
This is the step most competitor guides jump straight to, skipping five steps of groundwork that determine whether the model holds up at scale.
A working Clay workflow finds, enriches and scores target buyers workflow typically runs as:
Pull the tier-1 and tier-2 contact list from the CRM into Clay.
Reference the account tier already assigned in Step 3, since contact scores should be weighted by account tier, not scored in isolation.
Apply the persona and seniority criteria from Step 5 as a weighted formula, not a single yes or no filter.
Output a numeric score or a tier label (A, B, C) back to the contact record.
Sync that score to the CRM using the field mapping rules already established.
The weighting matters. A contact scoring model Clay builders often get wrong treats every criterion equally.
In practice, seniority and department usually deserve more weight than a skill or an award, since seniority correlates more directly with buying authority.
Step 7: Adding Intent and Engagement Signals
Only after fit scoring, both account and contact, is stable should intent and engagement enter the model. This is the step most guides put first. It belongs last.
Intent and engagement signals worth layering into the model include:
LinkedIn engagement with company content or team members.
Webinar or event attendance.
Form fills and content downloads.
Product usage data, for companies running product-led growth motions alongside sales.
Job changes among contacts already in the CRM, since a contact moving into a new role at a new company is a fresh buying window.
Intent data changes fast. Fit data (account and contact) changes slowly.
Building intent scoring on top of unstable fit data means the model reacts to noise. A contact clicking one email does not matter if the account was never a fit. 'Fit first, intent second' is the order that keeps the model from producing false positives. Once the scores update, they need a path back into the CRM where reps actually work.
If you're pushing this data through HubSpot, the field mapping and sync setup follows the same "overwrite" logic from steps 1 and 4. For the specific connection steps, check out our guide on Clay and HubSpot integration.
If a sync that used to work stops updating the scores, that's almost always a broken field mapping or an API limit, not a scoring logic problem.
Troubleshooting steps for that specific failure mode are already covered separately if your Clay and HubSpot integration isn't working.
Templates and Field Mapping Examples
A Clay lead scoring template and integration setup needs 4 building blocks: an account enrichment table, an account scoring formula column, a contact enrichment table, and a contact scoring formula column.
A simple field mapping example for the account side:
CRM Field | Clay Enrichment Source | Sync Rule |
Employee Count | Company enrichment | Overwrite |
Industry | Company enrichment | Write only if empty |
Funding Stage | Company enrichment | Overwrite |
Job Postings (count) | Job posting enrichment | Do not write, score only |
Account Tier | Formula column | Overwrite |
A matching example for the contact side:
CRM Field | Clay Enrichment Source | Sync Rule |
Job Title | People enrichment | Write only if empty |
Department | People enrichment | Overwrite |
Seniority | People enrichment | Overwrite |
LinkedIn URL | People enrichment | Write only if empty |
Contact Score | Formula column | Overwrite |
These Clay lead scoring automation examples field mappings hold up because the overwrite logic protects the data reps already touched, while the fields Clay owns entirely stay current every sync.
Copy the pattern, not the exact fields; your ICP and CRM object structure will change which fields matter most.
Clay Lead Scoring Criteria for Target Buyers
Pulling the guide together, the criteria that show up most often in a working Clay data automation and lead scoring target buyer lists setup:
Account-level criteria:
Employee count and revenue band against your ICP range
Job postings mentioning relevant tools, teams, or initiatives
Headcount in the department most likely to buy or champion
Technology stack overlap or gaps
Funding stage and recency
Contact-level criteria:
Department and function
Seniority and title
Persona match against a defined buyer profile
Relevant skills, certifications, or prior company background
Intent and engagement criteria (layered last):
Job changes among existing contacts
Product usage, for PLG motions
Content engagement and event attendance
Website and pricing page activity
Clay scoring target buyers with signals and enrichment templates that combine all 3 layers, in the right sequence, produce a model that actually tells a rep who to call first, and why.
Real Case Study for Clay Lead Scoring
Fluint, an AI sales enablement company came to us with a hard problem: 10,000-plus contacts, a lifecycle with 20 separate stages, and 53% contact decay.
Over half the database no longer worked at the company associated with their record.
The build followed the account-first, contact-second sequence described above. It included:
Contacts enriched and scored for product-led growth fit, since the company's own product usage data was a strong signal alongside title and seniority.
The 20-stage lifecycle simplified into something a rep could actually use.
A role and seniority classification agent handling the persona matching from Step 5, replacing manual title review.
The job-change signal from Step 7 turned out to matter more than expected.
Instead of treating 53% contact decay as dead data, the model flagged contacts who had changed jobs as a specific outbound trigger. Someone who already knew the product was now sitting in a new seat, with new budget authority.
Within the first week of the new model running, an ABM sequence built on top of it generated a demo with a CCO-level contact at an enterprise account.
That is not a coincidence of good timing. It is what happens when fit and job-change intent are both scored correctly before a sequence goes out.
More Clay use cases for SaaS enrichment scoring case studies like this one, across different stacks and account sizes, are covered in our GTM case studies.
Everything You Need to Know About Clay Lead Scoring
Category | Key Considerations |
What is it? | Using Clay to enrich company and contact data, then rank both by fit, starting with accounts, then contacts, then intent |
Correct Sequence | Account field mapping, account scoring, tiering, contact field mapping, contact scoring, intent and engagement |
Who needs it? | RevOps leads, GTM engineers, and sales leaders managing more contacts than their team can manually prioritize |
Core field mapping decisions | Overwrite, write only if empty, do not write, decided per field before automation runs |
Common mistakes to avoid | Building contact scoring before account scoring, skipping field mapping decisions, layering intent signals before fit data is stable |
Data cost control | Enrich tier-1 and tier-2 accounts and contacts first; hold off on tier 3 until they move up |
Where do scores live? | Clay table first, then synced to the CRM account and contact objects |
Build Your Scoring Model with The GTM Engineering Company
The GTM Engineering Company builds these Clay lead scoring models inside the client's own CRM, not in a separate tool that reps have to check.
The 'account-first, contact second' sequence in this guide is what we also run for client engagements. On a recent build, we scored 10,000-plus contacts for a sales enablement company, replaced a broken 20-stage lifecycle, and turned job-change data into an active outbound trigger, generating a CCO-level demo in the first week the model ran.
If your lead scoring is stuck at the "contact level", with no account tier underneath, or your field mappings are quietly overwriting data the reps rely on, that's the workstream we plug into.
Every workflow by The GTM Engineering Company ships with a Loom walkthrough and written SOP, so your team can plug it in and start using the workflow for your business or use case.
To know more about how we can help, request a 30-day audit with our team. By day 30, you'll get a documented punch list, a working enrichment table and at least one operational scoring signal live in your CRM.
FAQs About Clay Lead Scoring
What is Clay lead scoring?
Clay lead scoring is the process of using Clay to enrich company and contact data, then rank contacts by fit against your ideal buyer profile. It works as 2 connected steps: account scoring first, then contact scoring on top of your tiered accounts. Intent and engagement signals get added last, once fit data is stable.
What should I consider when choosing a Clay lead scoring model for my team?
You should consider your data volume, your CRM's field structure, and whether you have an ICP definition to score against before you build anything. A model built without a clear ICP measures resemblance to past deals, not actual fit. Field mapping decisions need to be settled before any scoring formula runs. Teams with more contacts than accounts should always tier accounts before scoring contacts.
How does The GTM Engineering Company differ from a Clay agency doing one-time list building?
The GTM Engineering Company builds this scoring as living infrastructure inside the client's CRM, not a one-time delivered list. Every field mapping and scoring formula ships with a Loom walkthrough and a written SOP so the client's team can extend it. Work happens in weekly working sessions inside the client's own stack.
How do I get started with a Clay lead scoring build?
Getting started begins with a 30-day audit: a documented punch list of what is broken in your current data and scoring setup. By day 30, you should have a working golden enrichment table and at least one operational scoring signal already live in your CRM. From there, the build follows the account-first sequence: field mapping, account scoring, tiering, then contact scoring.
How long does it take to see results from a Clay lead scoring model?
Most teams see a usable account tier within 2 to 3 weeks of starting field mapping and scoring criteria work. Contact-level scoring typically follows within another 1-2 weeks. One build scored over 10,000 contacts and produced an outbound trigger that generated an enterprise-level demo within the first week the model went live. Full stabilization usually takes 60 to 90 days.
Why does my Clay lead scoring model keep breaking after it works for a few weeks?
These models usually break because a field mapping rule was set wrong, not because the scoring formula failed. A field set to overwrite when it should have been write only if empty erases manual data reps rely on. API limits or a broken CRM sync can also silently stop scores from updating. Check the overwrite logic first.
Can Clay lead scoring work without a defined ICP?
Clay lead scoring can technically run without a defined ICP, but the scores end up measuring resemblance to your existing customer base rather than actual fit. Without an ICP definition setting the baseline, account scoring criteria like job postings or headcount have no reference point for what "good" means. Teams that skip this step usually end up rebuilding their scoring model within a few months.
Isn't lead scoring just a feature inside my CRM already? Why build it in Clay separately?
Native CRM scoring tools work off whatever data already sits in your CRM records, and most records are incomplete or outdated before scoring starts. Clay adds the enrichment layer underneath, pulling in job postings, technographic data, and verified contact details a native CRM feature cannot reach on its own. Teams that skip enrichment end up ranking contacts on fields never filled in correctly.
