Account data quality engine

Infoblox account validation and enrichment

I owned the Greenfield, POC, and enrichment intake, the front door into CRM, as the data steward for incoming accounts. The job was filtering out weak account data before it could break quoting and planning downstream.

Employer / client: Infoblox
Duration: Jan 2020 - Apr 2022
Project type: Account validation and enrichment

Architecture and stewardship model

The account data-quality engine

Architecture diagram: four intake lanes (Greenfield, POC, enrichment, IC) pass through source-confidence checks into a steward decision gate, then into governed CRM and downstream quoting, territory, and analytics, with failure patterns looping back to tighten the rules. — Four intake lanes pass through source-confidence checks into a steward decision gate, then into governed CRM and downstream use. Failure patterns loop back to tighten the rules.
Account data-quality engine

Stewardship as a loop, not a one-off cleanup: define standards, validate at intake, monitor quality, escalate and resolve, then feed governance.

Data stewardship operating model

Process flow

How I work the steps

01
before Intake request
Greenfield, POC, enrichment, or IC-account request hits the queue.
Sales / Partner teams
02
control Source confidence check
Sales Navigator, D&B Hoovers, ZoomInfo, and the Salesforce context reviewed.
BA
03
risk Duplicate / ownership decision
Open, verify, reject duplicate, or escalate the conflict.
BA / Sales Ops
04
after Salesforce load / handoff
Validated account moves into quoting, territory assignment, and reporting.
BA / CRM teams

How I worked the problem

Ran due-diligence-style checks on the account and contact signals before any record entered quoting, territory assignment, or ownership transfer.
Worked through the Greenfield, POC, enrichment, and validation queues, then took on IC account handling when continuity and accountability mattered more.
Wrote handoff criteria for source confidence, hierarchy completeness, and contact validity so the quality didn't depend on tribal memory.
Pushed the repeated failure patterns back to governance and reporting so the intake rules got tightened over time.

Measured results

What I delivered

4 volume

Intake tracks owned

Greenfield, POC, enrichment, and IC account handling.

60K+ volume

CRM records governed in wider programme

Validation fed the broader Infoblox governance and reporting scope.

Outcomes

Validated and enriched account/contact records so Sales Ops and partner teams could trust CRM context before they quoted or planned anything.
Stabilised the Greenfield and POC workflows, then took on IC account handling as the process matured and needed firmer ownership.
Tied account validation back into CPQ, governance, and reporting so the quality gains showed up in daily execution, not just in periodic cleanup.