34%

annual B2B contact data decay rate

"Our database has 45,000 contacts" is not a data quality metric.

Neither is "we grew our list 30% last quarter." Neither is "we imported all of our tradeshow leads from the past three years."

These are volume metrics. Volume tells you how much data you have. Health tells you how much of it is actually usable — how much of it will deliver, enrich the right person, route to the right rep, and support a revenue conversation rather than bounce or sit silently in a queue that nobody works.

For most RevOps and marketing operations teams, there is a significant gap between contact count and usable contact count. Database health is the discipline of measuring, closing, and maintaining that gap. It is also — done right — a board-presentable metric that connects directly to pipeline and revenue.

This post explains how to build it.

Why Database Health Matters to the Revenue Organization

Before the framework, the business case — because database health initiatives require organizational investment, and investment requires justification beyond "our data is messy."

The specific revenue levers that database health affects:

Speed-to-lead. Contacts contacted within 5 minutes of converting are 21 times more likely to qualify than those contacted after 30 minutes. Lead routing failures — which are predominantly caused by missing or incorrect data — directly delay response time. Every routing exception that drops a lead into a default queue for manual triage is a speed-to-lead failure with a quantifiable conversion cost.

Campaign performance. Email campaigns sent to invalid or stale addresses generate hard bounces that damage sender reputation. As sender reputation degrades, inbox placement falls, and campaign performance drops for all recipients — including the valid ones. Database health directly affects whether your marketing spend reaches anyone.

Sales rep efficiency. Reps who work contacts with incomplete information spend time researching that should be spent selling. Studies consistently show that reps spend 20-30% of their time on data entry and research tasks that enriched, governed data would eliminate.

Forecast accuracy. Deals in your pipeline that are associated with contacts with bad data — wrong title, wrong company size, no phone number — are deals where your rep's understanding of the opportunity is built on a weak foundation.

Database health is not a CRM hygiene project. It is a revenue operations concern.

The Five Dimensions of Database Health

Database health is not one metric. It is a composite of five dimensions, each measurable independently and together forming an overall health picture.

Dimension 1: Active vs. Dormant Contacts

Not every contact in your CRM is a real opportunity. A meaningful portion of most databases consists of contacts who have never engaged, contacts who disengaged years ago, and contacts whose information has decayed to the point of uselessness.

Active contacts are those who have: a valid email address, at least one engagement signal in the past 12 months (open, click, form fill, meeting, call), and a company association that appears to still be active.

Dormant contacts are those who have: bounced email, no engagement in 12+ months, or a company that appears to have closed or been acquired.

How to measure it: In HubSpot, build a list with these criteria:

Email Status = Valid AND
Last Email Open Date is less than 365 days ago OR Last Meeting Booked Date is less than 365 days ago OR Last Logged Call Date is less than 365 days ago

Run this list against your full database. The ratio of contacts on this list to your total contact count is your Activity Rate. Most organizations find this is 30-50% of their total database — meaning 50-70% of their contacts are dormant.

This is not cause for despair. It is cause for a decision: remediate (enrich, re-engage) or archive (suppress from active marketing, reduce database noise).

Dimension 2: Completeness Rate on Critical Fields

Completeness is the most commonly measured quality dimension — but most teams measure the wrong fields. Measuring completeness on Phone Number tells you less than measuring it on the fields your GTM motion actually requires.

Define your critical field set: the minimum set of properties that a contact must have populated for a rep to meaningfully work them. For most B2B organizations, this is something like:

First name, last name
Email address (valid)
Job title
Company name
Company industry
Company size (employee count range)
Geographic location (country; state for US)

Calculate completeness per field and as an overall score. A contact that has 5/8 critical fields populated is 62.5% complete. The database average across all contacts gives you your overall completeness rate.

Target: 80%+ completeness on all critical fields for your active contact segment. Below 60% on any critical field is a meaningful routing and segmentation risk.

How to measure it in HubSpot: Use the Property column analytics in the contact index view — it shows percentage of contacts with a property populated. Or create a custom calculated property using HubSpot's Operations Hub that sums populated fields and divides by the total.

Dimension 3: Freshness

B2B data decays at 34% annually. Job titles turn over at 65.8% per year. Emails at 37.3% per year. A contact record that hasn't been touched in 18 months has a statistically significant probability of being wrong on at least one critical field.

Freshness measures how recently your records have been verified or enriched. It is not the same as completeness — a record can be completely populated but with data that is 3 years old and significantly inaccurate.

How to measure it: Add an Enrichment Date property to your contact records. Every time a contact is enriched (via any source), update this property. Your freshness distribution then becomes:

Enriched within 90 days: Fresh (A)
Enriched 91-180 days ago: Acceptable (B)
Enriched 181-365 days ago: Stale (C)
Enriched 366-730 days ago: Very Stale (D)
Never enriched or enriched 730+ days ago: Critical (F)

Build a HubSpot custom report that shows the distribution of your active contacts across these bands. A healthy database has >60% in A or B, <10% in D or F.

If you are not currently tracking enrichment date, a proxy metric is Last Modified Date — though this captures any record modification, not just quality-relevant enrichment.

Dimension 4: Duplicate Density

Duplicates silently corrupt every process that touches your database. They double-count contacts in reports. They cause reps to call the same person twice. They route a lead to a rep who already owns that account — or to a different rep who doesn't.

The average B2B CRM has a duplicate rate of 10-30%. Most teams dramatically underestimate their duplicate density because HubSpot's native deduplication is email-match-based — a duplicate who used two different email addresses is invisible to native tooling.

How to estimate your duplicate density: Run a sample-based audit. Take a random sample of 500 contacts. Manually review for duplicates — same name and company, slightly different email (john.smith@company.com vs. jsmith@company.com), or same person at different job stages. Multiply your sample duplicate rate by your total database size to get an estimate.

More rigorously, use a tool with probabilistic matching (Insycle, Dedupely, or similar) to run a full database analysis and get a confidence-weighted duplicate count.

Tracking over time: If you're actively deduplicating, track: merges per month, net change in contact count (not just gross adds), and the ratio of new contacts created to merges performed. A healthy database keeps the merge-to-add ratio low — meaning you're preventing duplicates more than you're creating and later fixing them.

Dimension 5: Deliverability Health

Your deliverability health is the measure of whether your database can actually receive your communications. It is the most directly revenue-linked dimension because a database with poor deliverability health cannot be marketed to effectively, regardless of how complete or fresh the records are.

Key metrics to track:

Hard bounce rate (last 90 days): Target <0.5%, concerning >1%, critical >2%
Soft bounce rate (last 90 days): Target <3%, monitor trend upward
Spam complaint rate: Target <0.1% (Google's threshold for filtering)
Email valid rate: Percentage of contacts with Email Status = Valid vs. Bounced/Unsubscribed
Unsubscribe rate (trailing 90 days): Target <0.5% per send, >1% suggests audience-message mismatch

In HubSpot, these metrics are available in the Email Analytics dashboard for campaign-level data. For database-level analysis, build a contact-based report filtered to Email Status = Hard Bounced and Email Status = Unsubscribed to see absolute counts and trends.

The compound effect: As hard bounce rate rises, your deliverability reputation decays, which suppresses inbox placement, which reduces open rates, which makes soft engagement metrics look worse than they are. Deliverability health is the canary in the coal mine for database quality overall.

Building a Database Health Dashboard in HubSpot

Here are the specific report templates to build in HubSpot:

Report 1: Database Composition (Single-number and list-based)

Total contacts (all statuses)
Active contacts (list per Dimension 1 criteria)
Dormant contacts (total minus active)
% Active: Active / Total

Report 2: Completeness by Critical Field

Contact-based table report
Columns: each critical field, % populated
Segment by: New vs. Existing (created in last 90 days vs. before)

Report 3: Freshness Distribution

Contact-based report, grouped by Enrichment Date bands
Stacked bar chart: A, B, C, D, F by quarter created

Report 4: Deliverability Health Trend

Email sends report, grouped by month
Metrics: Hard bounce rate, Soft bounce rate, Unsubscribe rate
12-month trailing view to see trend

Report 5: Routing Exception Rate

Contact-based report, filtered to Routing Exception = true
Grouped by month: how many exceptions per month, trend direction

Combine these five reports on a single HubSpot dashboard. Update monthly. Review quarterly in your RevOps team meeting.

Setting Targets and Tracking Trend Over Time

Point-in-time measurement is useful; trend measurement is where the operational insight lives.

Establish baselines in month one. Set targets for month six and month twelve. Review quarterly and adjust targets based on operational capacity.

A practical target framework:

Dimension	Current (Baseline)	6-Month Target	12-Month Target
Activity Rate	Measure	+10%	+20%
Completeness (avg critical fields)	Measure	75%	85%
Freshness (% A or B)	Measure	50%	65%
Estimated Duplicate Rate	Measure	-30% reduction	-60% reduction
Hard Bounce Rate	Measure	<1%	<0.5%

The numbers in this table are placeholders — your baselines will determine what realistic improvement targets look like. The structure is the value: a scorecard with a before-and-after view that you can track over time.

How to Present Database Health to Leadership

Leadership doesn't care about bounce rates. They care about pipeline and revenue. The translation layer is your job.

The framing that works: Connect every database health metric to a revenue outcome.

"Our active contact rate is 38%. That means 62% of the contacts we're paying to store in HubSpot — and theoretically marketing to — cannot be reached. If we improve that to 55%, we expand our addressable audience by 44% without buying a single new contact."
"Our hard bounce rate is 1.8%, which is approaching Google's filtering threshold. If our emails start landing in spam for Gmail users, our effective open rate will drop roughly 30%. On a list of 20,000, that's 6,000 fewer opens per send — and at our current click-to-demo rate, approximately X fewer demos per month."
"Our average completeness score on critical routing fields is 61%. Based on last quarter's routing exception log, we had 340 leads fall into the default queue — a process that added an average of 4.7 hours to our response time. At our current 5-minute vs. 30-minute conversion ratio, we estimate X leads were impacted."

The model is: data quality metric → operational failure mode → quantified revenue impact. You don't need perfect numbers. You need directionally credible estimates that give leadership a reason to fund improvement.

Database Health Is a Leading Indicator of Revenue Health

There is a temporal relationship between database health and revenue outcomes: database quality problems show up in the data months before they show up in the pipeline.

A deliverability crisis that begins in October — driven by a large import of stale data in September — doesn't peak in your pipeline reports until December, when the campaigns you sent in October fail to generate meetings that would have closed in Q4. By then, it is too late to fix Q4. You can only fix Q1.

Database health metrics are leading indicators. They tell you what your pipeline will look like in 60-90 days if you do nothing. They give you a window to act before the revenue impact is fully realized.

That is why this belongs on your RevOps dashboard alongside pipeline metrics, not in a separate "CRM hygiene" initiative that nobody reads.

We built MarketingSoda Refine™ around this belief — that database health should be continuously monitored, automatically scored, and actionable without a quarterly manual audit. Our free database health scan connects to HubSpot via OAuth and returns an A-F grade distribution across your contact database in 60 seconds. Join the waitlist for MarketingSoda Refine to be among the first to run it on your database.

Your contact count is not a data quality metric. Your database health score is.

Interested in automated database health scoring for HubSpot? We're building MarketingSoda Refine to make this continuous and automatic. Join the waitlist for MarketingSoda Refine for early access.

What "Database Health" Actually Means — and How to Measure It