←
Work/Vericast

Vericast

Enterprise CRM data decays around 30% a year. I designed the review workflow that fixes it systematically, inside Dynamics rather than bolted on top.

Vericast

The data-quality dashboard — built entirely from native Dynamics patterns, so it reads as part of the CRM rather than a guest inside it.

The data-quality dashboard — built entirely from native Dynamics patterns, so it reads as part of the CRM rather than a guest inside it.

The issue

A ten-second fix nobody could find

Account records in Dynamics rot — wrong tags, stale revenue, dead websites, departed contacts. Fixed by hand: no queue, no source comparison, no audit trail.

It had to feel like it shipped with Dynamics 365, not like a third-party tool.

The decisions

Three things the workflow needed

01

A queue, not a discovery problem

Data issues become cases in a reviewable list, with bulk approval — a hundred corrections aren't a hundred clicks.

The review queue — cases, owners, and bulk approval.
The review queue — cases, owners, and bulk approval.
02

Four sources, side by side

ZoomInfo, Dun & Bradstreet, LinkedIn and Wikipedia in one view, not four browser tabs.

Sources compared in place, so a correction is a decision rather than a research project.
Sources compared in place, so a correction is a decision rather than a research project.
03

Duplicates caught at creation

New accounts check existing records and external databases first. The cheapest duplicate is one never created.

Account creation, checked against internal and external records before saving.
Account creation, checked against internal and external records before saving.
The constraint

Native, or it doesn't get used

The client's reference was a Salesforce-style version of this. Copying it would have been faster and wrong, so every component came from Fluent UI. Teams route around anything that makes them relearn their own tool.

Outcome

Approved as the direction

The deliverable was a high-fidelity Figma prototype, used for exactly that: executive review and roadmap planning.

Being straight: this never shipped to users. No adoption or accuracy numbers, and I won't estimate any — what's here is the model, not a result.

Every company, contact and figure here is demo data.

Want the reasoning behind each decision, and what I turned down?