How to build a local business email list

A plumber has no LinkedIn profile with a work address behind it. There is no HR record, no corporate directory, no domain pattern to guess from.

The email exists in one place: a page on the firm’s own website. A contact page, a footer, a form, a mailto link, a photo of a van with an address painted on it.

So the chain runs like this.

• The Maps listing gives you the website address.
• The website gives you the email, if the owner put one there.
• No website means no contact page. No contact page means no email.

That chain has one snap point, and it is the same one every time. A firm with no website has no email for anyone to find, and no tool on earth can invent it.

Most B2B data tools grew up on software sales. They map a company to its domain, then map people to that domain by job title.

That model needs three things. A domain, a set of named staff, and a public profile per person. A four-person joinery in Bergen has none of them.

• No domain in many cases, so the whole model has nothing to hang on.
• No named staff, because the owner is the sales team and the van driver.
• No job titles to filter by. There is one title, and it is owner.
• No pattern to guess. A firm on a free webmail address breaks every rule.

So you search a big database for painters in Aarhus and get a handful of rows, most of them wrong. The tool is not broken. It was built for a different world.

The route that does work is dull. Crawl the map, follow each website, read the contact page, keep what you find, and flag the rest as missing.

Anyone selling you a local list with full email coverage is selling you guesses. Here is what an honest crawl returns across the trades we publish list pages for.

• Norway: 9,632 records, 38% with an email on file.
• Sweden: 6,404 records, 19% with an email.
• Denmark: 3,927 records, 17% with an email.
• Finland: 3,883 records, 16% with an email.

Norway is the outlier, and Norway is the ceiling. Three of the four countries sit under one row in five.

The spread by trade is wider still, and it is the spread you should plan around.

The two ends of the same file

Only 3% of Danish painters have an email on their listing. Buy a thousand of those rows and you get thirty addresses.

57% of Swedish opticians do have one. Same crawler, same week, nineteen times the coverage.

The difference is not our data. It is the trade. Opticians run shops with opening hours and appointment pages. Painters run vans.

So the question is never how good the data is. It is which trade you picked.

Mailbox providers watch how often your mail hits an address that does not exist. A high bounce rate reads as a sign that you bought a stale list, and they treat you as such.

The damage lands on the sending domain, not on the campaign. Burn it, and every future email from that domain starts life in a worse place.

How verification works

A verifier opens a conversation with the receiving mail server and asks whether an address exists. It never sends a message.

The server answers in one of three ways.

• Valid. The mailbox exists and the server says so.
• Invalid. The mailbox does not exist. Drop the row.
• Catch-all or unknown. The server accepts everything, so it tells you nothing.

That third bucket is the one people misread. A catch-all domain is not a bad address. It is an address nobody can check, and small local firms sit in that bucket often.

Treat catch-all rows as a separate send, at low volume, and watch what comes back.

Rules that keep a domain healthy

• Send from a domain you can afford to lose, not from your main one.
• Set up SPF, DKIM and DMARC before the first send, not after the first problem.
• Warm the domain over weeks. A new domain sending hundreds on day one looks like what it looks like.
• Verify within days of sending. A list checked in March is a guess by June.
• Watch the bounce rate per send and stop the moment it climbs.
• Keep a suppression list and honour it forever.

None of this is exciting and all of it is load-bearing. Deliverability is the tax you pay for reaching anyone at all.

1. Pick the trade before the country. Trade drives coverage far harder than borders do. Check the trade first, then pick where.
2. Pull the full list, not the emailed slice. You want every row, with a flag for what each one carries. The gaps are half the information.
3. Split the file in two on that flag. One file with email, one without. They get different campaigns, not one campaign with holes.
4. Verify the email half before you send. Drop the invalid rows. Park the catch-all rows for a small, careful test send.
5. Route the rest to phone. The no-email half is not waste. It is the half your competitors never call.
6. Log every reply against the row. Opt-outs go straight into suppression. Interest goes into the calendar, not into a nurture flow.
7. Re-pull the list each quarter. Firms close, sites go up, addresses change. A local file decays faster than people expect.

That plan gives you two working campaigns instead of one broken one. It also stops you paying for a list and then blaming the list.

Building it yourself means a Maps crawl, a website crawl, a parser for contact pages, proxies, and a job that runs again next month. That is real engineering, and the second month is when people quit.

Buying it means a subscription and a filter. You lose the fun and you keep the afternoon.

The honest rule is need frequency. One list, once, for one town? Build it by hand and enjoy the walk. A list a month across four countries? Buy it, and spend the saved time on the sending.

Whichever way you go, hold the file to the same standard. Every row dated, every gap flagged, and no invented addresses anywhere in it.

If you want to see the shape of a finished file first, the Google Maps guide lists what a usable export holds.