Confidence you can act on

Company & individual record matching

Match with confidence

Upload two lists — companies or people — and CertiFind tells you exactly how sure it is about every match, so review time goes only where it's actually needed.

Files never stored

Uploads are matched in memory during the request and discarded — nothing lands on disk or in a database.

Verified accounts only

Every signup confirms email ownership before first use.

Code-based sign-in

A fresh 6-digit code is emailed on every login, in addition to your password.

Hashed everything

Passwords and session tokens are hashed before storage — never kept in readable form.

Two ways to match

Choose your mode when you start a match — the underlying pipeline adapts to what you're comparing.

Company Matching

Match organizations by name and location. Legal suffixes, punctuation, and casing are normalized away, so "Aquinnah Pharmaceuticals, Inc." and "AQUINNAH PHARMACEUTICALS" resolve to the same company.

Individual Matching

Match people by name and location. Nicknames resolve (Bob/Robert), initials are recognized (J./John), and a conflicting suffix — Jr vs Sr — is treated as evidence of a different person, not the same one.

How a match gets decided

The same four-stage pipeline runs on every record, in order — whichever mode you're in.

01

Normalize

Company suffixes, punctuation, and casing — or, for people, titles, nicknames, and generational suffixes — are stripped so equivalent records collapse to the same key.

02

Match in two tiers

Exact normalized keys are matched first. Everything left over goes through fuzzy scoring: token-based similarity blended with Jaro-Winkler for typos and reordering.

03

Confirm with corroborating detail

State and ZIP either confirm a fuzzy match or veto it. For people, a conflicting suffix (Jr vs Sr) does the same job. A trap, not a win, is downgraded to review.

04

Band the results

Every pair lands in exact, auto-accepted, needs review, or no match — so a human only has to look at the genuinely ambiguous middle.

Four bands, not one score

Exact

Normalized keys match, and corroborating detail doesn't conflict. No review needed.

Auto-accepted

A high blended score with no conflict. Safe to trust by default.

Needs review

Either a strong match with a conflict, or a moderate score. This is where a human looks.

No match

Nothing scored high enough to be worth a second look.

Example run · 581 records

Exact412
Auto-accepted96
Needs review51
No match22

Only the 51 in review need a human — the rest are already decided.

Simple pricing

Start free. Upgrade when you need more than a few matches a month.

Free

Try it on a real list

$0

  • 3 matches per month
  • Company & Individual matching
  • Excel export with review tab
Create a free account

Pro

For ongoing individual use

Contact us

  • Unlimited matches
  • Larger file sizes
  • Priority support
Get in touch

Enterprise

For teams and organizations

Custom

  • Multiple seats
  • Volume pricing
  • Dedicated support
Contact sales

Upload two files. Get one answer.

Free to try. Your account is protected with email verification and a sign-in code sent to your inbox every time.

Create a free account