All posts
Data3 min read

Which Restaurants in Your CRM Have Already Closed?

Mert Iseri

A restaurant technology company shared a slice of its CRM with us: 392 accounts across two zip codes, 80501 in Longmont, Colorado and 01801 in Woburn, Massachusetts. Their CRM listed these as new openings for reps to work.

We asked two questions. Which of these restaurants have already closed? And which restaurants in the same two zip codes are missing from the list entirely?

What they sent

392 rows, two columns: restaurant name and a street address. No other fields left their system.

What we found

VerdictRowsShare
Sent392100%
Unique, open locations23660%
Duplicate rows3810%
Closed256%
Unverifiable9324%

Four in ten rows could be removed from their CRM. This saves time for the reps working their territories and thousands in enrichment costs for the Rev Ops team.

Even the 236 open, unique rows were not all restaurants. 14 were social clubs, a church, a golf course, a sign company, a senior living facility, and an office building.

What was missing

Then we looked at the same two zip codes from the other direction. Every food business that is open today and was not in the CRM at all.

Zip codeOpen businesses not in the CRMOf which strict restaurants
80501, Longmont, CO235134
01801, Woburn, MA11455
Total349189

Put the two tables side by side. The CRM had 236 open, unique locations in these ZIP codes. There were 349 more open food businesses in the same zips that it had never seen. The missing list is bigger than the working list.

The missing businesses skew toward the formats a sales team would want:

CategoryMissing from CRMIn CRM
Fast food637
Cafes5726
Takeaway5514
Coffee shops5017
Caterers4919
Bakeries4615
American3721
Breakfast3413
Mexican3321
Sandwich shops2810
Pizza2017
Bars2935

A location can carry more than one category, so the columns do not sum to the totals above. The pattern is clear anyway. Of these formats, bars were the only one where the CRM knew more locations than it was missing. For fast food, the CRM had 7 and was missing 63.

Why this happens

None of this is a knock on the team. It is what a CRM does when it is filled by hand.

Reps upload duplicates. A rep pulls a list, another rep pulls a similar list a quarter later, and both get imported. Slightly different names or addresses defeat the dedupe rule. Now the same taqueria is three accounts owned by two people.

Restaurants churn. Thousands of restaurants open and close in the US every month. A list built in the spring is missing every opening since and still carrying every closure since. We wrote about why restaurant data goes stale faster than any other category.

Nobody re-checks the file. Once a row is in the CRM it stays there. The enrichment budget gets spent on it every cycle whether it is a live restaurant, a copy of one, or a parking lot.

How Sync works

Sync is the check we ran above, run on your whole CRM.

  1. You send us a CSV with two columns: restaurant name and address. Nothing else leaves your systems.
  2. We verify every row against the live map and check the rows against each other.
  3. You get your file back with a verdict on every row:
ColumnWhat it is
row_idYour row, unchanged
statusopen, closed, duplicate, or unverifiable
duplicate_ofThe surviving row for each duplicate group
verified_name, verified_addressThe canonical name and physical address for every open location
  1. You also get a second file: every open restaurant in the geographies your file covers that is not in your CRM today. Name, address, category, and the same verification.

If you want the check to keep running, Daily Snapshot is the same verification every morning: send us your list and we flag what changed.

Sync puts every downstream dollar on a real, open, unique restaurant, and puts the restaurants that opened in your backyard onto the list before your competitors call them. Talk to us if you want to keep your CRM up-to-date forever.