MeshLine
Which Lead Score Should You Build First? Object, Type, and Downstream Use
Scoring contacts and companies at once is how lead scoring projects stall. See how the decision you need to make points to the right first score.
Most teams that start lead scoring stall because they try to score everything at once.
They sketch a contact score, a company score, and a deal score, then argue about weighting until the project loses momentum.
The faster path is to pick one score, build it well, and let its downstream use tell you what to build next.
This article gives you a decision order: which object to score first, which score type to start with, and how your planned use should shape that choice.
The facts about what each object and score type supports come from HubSpot's documented lead scoring tool, so you can plan against what your subscription actually allows.
Start with the decision that will use the score
The most reliable way to choose your first score is to work backwards from a decision, not forwards from data.
Ask: what recurring decision do marketing and sales argue about today?
Common answers include which leads sales should call first, which accounts deserve account-based outreach, and which open deals need attention.
Each answer points to a different object.
If the decision is about who to call, you are ranking people.
If it is about which organizations to target, you are ranking companies.
If it is about which opportunities to forecast or rescue, you are ranking deals.
Building the score for the object where the decision actually happens keeps the project anchored to a real workflow.
If you already know the score will feed a segment, a workflow, or a report, it is worth reading how those three surfaces behave differently before you build.
Our guide on where a lead score should act: segment, workflow, or report covers that choice in detail.
Which object should you score first?
Contacts: the default first score for marketing-led teams
Contacts are where most teams should start, and there is a practical reason beyond habit.
Contact scoring is available with Marketing Hub, and contacts support all three score types: engagement, fit, and combined scores.
If your bottleneck is lead handoff — marketing generating interest, sales unsure who to prioritize — a contact score directly addresses it.
A contact score also tends to have the richest signal available.
Website visits, email opens, CTA clicks, and form submissions all live at the contact level, so an engagement score has plenty of events to work with.
Fit criteria such as job title and company size are also commonly stored on contact records.
The tradeoff: a contact score alone can mislead in account-based motions.
A junior contact at a perfect-fit company can outscore a decision-maker at a mediocre-fit one.
If your sales team sells to organizations rather than individuals, plan for a company score as your second build.
Companies: the first score for account-based selling
If your go-to-market is account-based, flip the order.
Companies support engagement, fit, and combined scores, and scoring is available with either Marketing Hub or Sales Hub.
A company fit score built on industry, employee count, and revenue answers 'which accounts look like our best customers' before anyone has interacted with you.
Company scores are also more stable than contact scores.
Individual contacts go quiet; companies accumulate activity across many people.
If your sales team works territories or named accounts, a company score gives them a ranking that survives personnel changes on the buyer side.
The tradeoff is signal density.
If your CRM has sparse company records — missing industry, stale employee counts — a fit score will rank accounts on incomplete data.
Clean the properties you plan to score on before you build, or the score will inherit the gaps.
Deals: the score for forecast and pipeline hygiene
Deals are the narrowest starting point.
Deal scoring is available with Sales Hub, and deals support combined engagement and fit scores only — you cannot build a standalone engagement or fit score on a deal.
That constraint tells you something about intent: deal scores are for ranking open opportunities by combining activity and profile signals, not for early-stage qualification.
Start with a deal score only if your primary pain is inside the pipeline: deals stalling, forecasts swinging, reps unsure where to spend selling time.
If your pain is upstream — too many raw leads, unclear handoff — a deal score will not help yet, because the records it ranks do not exist until qualification has already happened.
Which score type should you build first?
Fit scores: fastest to build, easiest to explain
A fit score ranks records on property values — job title, company size, industry, annual revenue.
It is usually the right first build because it is simple to construct and simple to defend.
Sales can look at a fit score and immediately understand why a record ranks where it does, which matters when you are asking a skeptical team to trust a new number.
Fit scores also do not depend on tracking infrastructure.
If your email tracking, website analytics, or event capture is incomplete, an engagement score will be built on holes.
Fit criteria are already in your CRM.
The tradeoff: fit scores are static.
A perfect-fit contact that never engages will sit at the top of the ranking forever.
Fit alone answers 'who should care about us,' not 'who is caring about us right now.'
Engagement scores: powerful, but only with reliable tracking
An engagement score ranks records on actions — page visits, email opens, CTA clicks, meetings booked.
It captures intent that fit cannot, and it changes over time, which makes it useful for timing outreach.
Build engagement first only if two conditions hold.
First, your tracking must be trustworthy.
If email opens are unreliable or web activity is misattributed, the score will misrank people in ways that are hard to diagnose.
Second, your team must understand that engagement decays in meaning — a contact who was hot last quarter is not hot today.
HubSpot's scoring tool supports group limits, so you can cap how much awareness-level activity contributes versus conversion-level activity like meetings.
This helps keep casual browsing from inflating a score.
Combined scores: start here only with a clear reason
A combined score looks at both engagement and fit, and it also populates the individual engagement and fit values so you can inspect them separately.
That sounds like the obvious best choice, and for mature teams it often is.
But as a first build, it front-loads every hard problem at once.
You must decide fit criteria, engagement criteria, and how the groups weigh against each other before you have learned anything.
A better sequence for most teams: build a fit score first, watch how sales uses it, then add engagement as a second score.
Only then consider a combined score if the two need to be read together.
The exception is deal scoring, where combined is the only option — there, the decision is made for you.
Let the downstream use settle the arguments
Score properties are not endpoints.
Once built, you can use them in segments, workflows, and reports, and knowing the destination resolves most weighting debates.
If the score will trigger a workflow, such as notifying a rep when a record crosses a threshold, the threshold matters more than exact point values.
Design the score around clean crossing behavior rather than fine gradations.
HubSpot's workflow tool lets you enroll records based on property criteria, so a score property can serve directly as an enrollment trigger.
If the score will primarily feed a report or a review meeting, precision matters less than distribution: you need the ranking to spread records out enough to be readable.
If it will feed a segment for a nurture campaign, you care about how the score interacts with the other segment filters.
One structural note: you can create multiple scores per object, labeled clearly for each team or region.
That means your first score does not have to serve everyone.
A regional team with different ideal-customer profiles can get its own fit score later rather than compromising the first one.
A practical build order
- Name the decision. Write down the recurring argument the score will settle. If you cannot name it, you are not ready to build.
- Pick the object where that decision happens. People-level handoff problems point to contacts; account targeting points to companies; pipeline triage points to deals.
- Check your subscription. Contact scoring requires Marketing Hub, deal scoring requires Sales Hub, and AI-assisted scoring has further plan requirements. Our article on which HubSpot subscription you need for lead scoring and workflows walks through the tiers.
- Start with fit unless tracking is your strength. Fit scores are explainable and independent of tracking quality. Add engagement once the fit ranking has earned trust.
- Design for the destination. Confirm the segment, workflow, or report that will consume the score before finalizing thresholds and group limits.
- Review and iterate. Treat the first score as a draft that sales and marketing critique in the field, not a finished system.
Common first-score mistakes
- Scoring on data you do not maintain. A fit score built on properties your team never updates will drift silently. Audit the properties first.
- Building combined before simple. If you cannot explain a simple score to sales, a combined score will not survive scrutiny.
- Ignoring group limits. Without caps per group, a burst of low-value activity can dominate the total. Use group limits to weigh conversion events above awareness events.
- Building for a use that does not exist. A score nobody reads is maintenance without benefit. Tie every score to a named segment, workflow, or report.
Connecting the first score to the rest of your stack
A first score is most useful when the systems around it are already connected.
That way your CRM sync, automation, and reporting deliver the score's outputs to the people who act on them.
And once your score is live and feeding reports, the next question is usually measurement: which attribution report type answers your revenue question picks up from there.
The short answer: build the score for the object where your team's recurring decision lives.
Start with fit criteria you can defend, and design it for the one downstream use you know you need.
Everything else — engagement weighting, combined scores, additional objects — can follow once the first score has proven itself in a real workflow.
Platform details reflect HubSpot's documented lead scoring and workflow capabilities.
Verify current behavior and your subscription's permissions in your own account before building.
Source references: knowledge.hubspot.com; knowledge.hubspot.com.
How Meshline can help. Connect automation, Organic Marketing (demand generation), and customer lifecycle management (Revenue Intelligence).
Bring topic planning, content publishing and performance feedback into the conversation about your workflow. Book a Meshline demo.