GUIDE

OUTREACH

Using a public-data list without becoming the problem.

A tool that turns a map into a contact list makes it easy to reach a lot of businesses quickly. Whether that is useful or corrosive depends entirely on choices you make after the export. This guide sets out the practices we would expect of anyone using LeadForge. It is not legal advice — requirements differ by country and often by state or province, and you need to check what applies to you.

11 sections · LeadForge documentation

Start from what the data does not say

A LeadForge result means one thing: a business of this type is mapped at this location, and here is what its public listing contains. It does not mean the business is trading, that the phone number reaches anyone, that the e-mail address is monitored, or that anyone there has any interest in what you sell.

Every bad outreach campaign starts by forgetting this — treating a row in a file as a qualified prospect because it arrived neatly formatted. The completeness score measures the record, not the opportunity. A fully populated listing for a business that closed two years ago scores exactly as well as one for a thriving practice.

Verify before you use anything

Verification is not a formality you can skip when the list is long. It is the step that decides whether your outreach is informed or embarrassing.

  • Confirm the business exists as described. Open its website. Does the name match? Does the address match? Is there any sign the site has been maintained recently?
  • Confirm the contact detail at its own source. A phone number or e-mail address published by the business itself beats one recorded by a third party. Where they disagree, trust the business.
  • Check the record is not a duplicate of another row under a slightly different name, and that a branch is not being mistaken for a head office.
  • Check the category is right. Map tagging is approximate; a business filed under “clinic” may do something quite different from what you assumed.

Records that fail verification should be deleted, not kept “just in case”. A short verified list outperforms a long unverified one on every measure that matters, including how you feel about sending it.

Establish relevance before you make contact

The honest test is whether you could explain, in one sentence, why this specific business would want to hear from you — without using the word “everyone”. If the only answer is that they appeared in a radius search, the outreach is not targeted, it is volume.

Relevance is also what makes the work efficient. Contacting 30 businesses you have a genuine reason to approach produces better conversations and fewer complaints than contacting 300 chosen by proximity. Use the filters to get there: category, distance, presence of a website, opening hours that suggest an active business. Narrowing the list in the tool is faster than apologising later.

Do not send indiscriminate bulk messages

Mass unsolicited messaging is the use LeadForge is explicitly not built for, and it is prohibited by the terms of use. Beyond the rules, it fails on its own terms: recipients mark it as spam, sending reputation degrades, the messages stop being delivered at all, and the businesses that might genuinely have wanted to hear from you never see it.

Some practical restraints: keep volumes proportionate to your actual capacity to follow up; do not send a second and third message to someone who did not respond to the first; and never disguise a bulk send as a personal one. If your message would be indistinguishable from every other message the recipient received that week, the list is not the problem.

Business contacts and personal contacts are different

A general business line — info@, reception@, a switchboard number — is published so that people can reach the organisation. A named individual’s work address, or a personal mobile that happens to appear on a small business’s website, carries a stronger expectation of privacy even though both are technically public.

In many jurisdictions the legal treatment differs too: rules that are relaxed for corporate contacts are considerably stricter for identifiable individuals, and sole traders often fall on the stricter side. Prefer the generic business address wherever one exists. If contact discovery returns several addresses, choosing the role-based one is nearly always both the safer and the more effective option.

Do not use the tool to build lists about people. LeadForge is for finding organisations.

Honour opt-outs immediately and permanently

When someone asks not to be contacted, that request outlives the file it came from. Keep a suppression list, apply it before every send, and — this is where public-data workflows go wrong — apply it to new exports too. Because you can re-run the same radius search next quarter and get the same businesses back, an opt-out that lives only in a deleted spreadsheet will quietly stop working.

Make opting out easy: a working reply address, a clear instruction, and no requirement to explain themselves. Where the law specifies how quickly you must act on a request, treat that as the deadline, not the target — and act immediately in practice.

Know which rules apply to you

Marketing and privacy law varies widely. Depending on where you are and where your recipients are, obligations may cover the legal basis for contacting someone, whether prior consent is needed for particular channels, what identifying information a message must carry, how quickly opt-outs must be honoured, what records you must keep, whether a do-not-call registry must be checked before telephoning, and what rights individuals have over the data you hold about them.

These rules can apply to you because of where your recipient is, not only where you are. They also change. We cannot tell you what applies to your situation, and you should not rely on any tool — this one included — to have done that assessment for you. If your outreach is significant in scale or crosses borders, get advice that is specific to your jurisdiction and your channel.

Do not mislead

Say who you are and why you are writing. Do not imply an existing relationship, a referral, or a prior conversation that did not happen. Do not suggest that appearing in a directory means the business requested contact. Do not disguise a sales approach as a survey, a compliance notice, or a customer enquiry. Use a genuine sender identity and a working reply path.

Where you found the details is a fair question, and being able to answer it plainly — “from your public listing and your website” — is a good sign your approach is defensible.

Keep lists current, and keep them small

A prospect list built from map data decays quickly: businesses close, move, rebrand, and change numbers. A list from last year is not a list, it is a set of guesses. Re-verify before reusing, and re-run the search rather than trusting an old export for anything time-sensitive.

Alongside currency, practise minimisation. Keep only the fields you actually use — a phone list does not need coordinates, and a mail-merge does not need opening hours. Keep records only as long as you have a reason to. Delete campaign exports when the campaign ends. Less retained data means less to secure, less to keep accurate, and less to be wrong about.

LeadForge helps here by keeping saved lists in your own browser rather than on a server, and by making it a single action to clear them from the About page. Once you export, the file is yours to look after — store it somewhere access-controlled rather than a shared drive everyone can read. Exporting business data covers that in more detail.

Respect access controls and technical limits

Contact discovery in LeadForge reads a business’s public homepage and at most one linked contact or about page. It does not attempt to get past logins or other access controls, and neither should you. If a business publishes contact details only behind a form, that is a decision on their part — use the form.

The same restraint applies to the shared services this tool depends on. Rate limits and result caps exist because public map and tile services are community infrastructure. Working around them to extract data in bulk takes capacity away from everyone else, and it is prohibited by the terms of use.

A short pre-send checklist

  • Every record verified against the business’s own site.
  • A one-sentence, specific reason this business would want to hear from you.
  • Role-based contact addresses preferred over personal ones.
  • Suppression list applied, including to newly exported rows.
  • Sender identity accurate, opt-out path present and working.
  • Volume proportionate to your ability to have a real conversation.
  • Only the fields and records you need, stored somewhere appropriate.
  • Your obligations checked for your jurisdiction and channel.

Business data © OpenStreetMap contributors (ODbL). City data © GeoNames. Basemap © OpenFreeMap. Coverage varies by location.