Which Lead Score Should You Build First? Type and Object Decision

Most teams know they need lead scoring.

Fewer know where to start.

You can score contacts, companies or deals, and you can build an engagement score, a fit score or a combined score.

That is several possible first projects, and picking the wrong one wastes weeks of setup on a score nobody uses.

This article gives you a decision path.

By the end you will know which score type to build first, which object to attach it to, and what to check in your own CRM before you start.

First, understand the three score types

The three types answer different questions, and the distinction matters more than most teams expect.

An engagement score measures what a record has done: website visits, email opens, form submissions, meetings booked.

It answers, 'How interested is this lead right now?'

Engagement signals can go stale quickly, because a contact who was hot last quarter may be cold today.

A fit score measures what a record is: job title, company size, industry, annual revenue.

It answers, 'Is this the kind of customer we win?'

Fit changes slowly, because a contact's attributes rarely shift week to week.

A combined score blends both.

It answers, 'Is this lead both the right kind of buyer and actively interested?'

In HubSpot's lead scoring tool, combined scores also populate the individual engagement and fit values HubSpot's lead scoring documentation.

You can still see the components separately when you need them.

The tradeoff is simple.

A combined score is the most useful single number, but it is also the hardest to build well, because you must define both halves correctly at once.

If either half is wrong, the combined number misleads everyone who trusts it.

Which score type should you build first?

Start with the question your team actually argues about.

The score you build first should settle an existing disagreement, not create a new dashboard nobody asked for.

• If sales complains about lead quality ('these leads are never our buyers'), build a fit score first. Fit is the fastest to define because it uses property values you already store, and it directly addresses the complaint.
• If sales complains about lead timing ('we call these people and they have gone cold'), build an engagement score first. It surfaces who is actively showing interest right now.
• If both complaints are common, or if marketing and sales disagree about which leads to work, a combined score is the right destination, but consider whether you can define fit and engagement criteria confidently enough to build it in one pass.

A practical pattern for teams new to scoring: define your fit criteria first, even on paper, because fit forces you to articulate your ideal customer profile.

If you cannot list the attributes of a well-fitting lead, you are not ready to score anything.

Then layer engagement on top.

Whether you ship them as two separate scores or one combined score depends on your tooling and how your team wants to read the numbers.

There is a deeper comparison of the two component scores, including when one alone is enough, in our guide to fit score versus engagement score prioritization.

Which object should you score: contact, company or deal?

Object choice depends on what your subscription supports and who consumes the score.

In HubSpot, contact scores require Marketing Hub, company scores need Marketing Hub or Sales Hub, and deal scores are Sales Hub only the supported objects list.

Only combined scores are supported for deals.

Check your subscription before planning, because it may decide for you.

Beyond tooling, think about who acts on the score:

• Contact scores suit teams where an individual person is the unit of follow-up. SDRs working inbound leads, event follow-up and newsletter audiences all think in people.
• Company scores suit account-based motions where the account is the target and multiple contacts matter. A company score aggregates signals across the account, which matches how an AE plans outreach.
• Deal scores suit pipeline management. A deal score reflects engagement and fit at the opportunity level, which is useful for forecasting and for deciding which open deals deserve executive attention.

For most teams building their first score, the contact object is the right starting point.

It is where engagement signals live, it is what marketing can act on without sales involvement, and it produces the fastest feedback loop: score, route, observe, adjust.

One caution: do not build a company score first if your data hygiene at the company level is weak.

Company records often have more missing properties than contact records, and a fit score built on empty fields produces blank or misleading values.

Score the object whose data you trust.

A decision path you can run this week

Work through these questions in order.

Stop at the first answer that applies.

1. Does your subscription support the object you need? If you only have Marketing Hub, contact and company scores are your options; deal scores need Sales Hub HubSpot's subscription requirements.
2. Is the primary complaint about lead quality or lead timing? Quality points to fit; timing points to engagement.
3. Can you list your ideal customer attributes from existing CRM properties? If yes, fit criteria are ready. If no, fix your property data before scoring anything.
4. Who will act on the score, and at what level? Person-level follow-up means contacts; account planning means companies; pipeline review means deals.
5. Do marketing and sales need one shared number? If yes, plan for a combined score, possibly after validating the components separately.

Most teams land on one of two first builds: a contact fit score to fix quality complaints, or a contact engagement score to fix timing complaints.

Both are defensible.

The wrong first build is a combined score assembled before either component is understood.

How scoring mechanics shape your first build

Understanding how scores are calculated helps you scope a first project realistically.

Scores are built from score groups, each containing property or event rules with point values.

You can set an overall score limit and separate group limits, letting you weigh categories differently how scores are calculated.

For example, allow more points for conversion events like meetings than for awareness events like page visits.

Two behaviors matter for your first design.

First, separate property or event rules update the score independently, even within the same group, so a contact does not need to meet every rule to earn group points.

Second, rules that combine multiple criteria for the same property follow AND logic, updating only when all criteria are met filter criteria behavior.

Knowing this prevents the common mistake of stacking criteria and wondering why scores stay flat.

Also plan for multiple scores over time.

The same tool supports creating several scores per object, such as one score for prospects and another for existing customers multiple scores per object.

Region-specific fit scores also work where your ideal profile differs by market.

Your first score should be labeled clearly so later scores do not create confusion about which number means what.

Common first-score mistakes to avoid

• Scoring events you cannot act on. If no workflow or routing rule consumes the score, it is decoration. Decide the action before the criteria.
• Building fit criteria from aspirational data. Score the attributes you actually capture today, not the ones you wish you captured.
• Ignoring permissions. Viewing and editing lead scores in HubSpot requires specific Lead Scoring permissions, so confirm your team has access before kickoff permissions requirements.
• Skipping the review cadence. A first score is a hypothesis. Schedule a review to check whether high-scoring leads actually convert better, and adjust points where they do not.

Connecting your first score to routing and automation

A score earns its keep when it drives routing.

Once your first score exists, use it in segments, workflows or reports, which is exactly how score properties are designed to be consumed using score properties in other tools.

The natural next step is an automated routing rule that sends high-scoring leads to the right owner quickly.

Our guide to building an automated inbound lead routing system in HubSpot covers that workflow.

It helps you sequence the data sources that feed your scores.

And once your first score is live, the question becomes how to keep the whole qualification process reliable.

The short answer

Build the score that settles your loudest current argument, and attach it to the object whose data you trust.

For most teams that means a contact-level score, wired into one concrete routing action on day one.

Rule of thumb: score the object whose data you trust, with the score type that answers the question your team is already asking, and connect it to one concrete action on day one.

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.