We build lead lists from public business sources: company registers, trade and association directories, and the businesses' own websites. You get a clean CSV, or the records loaded into your CRM, with the source link and the date collected on every row, so any value can be checked. How you contact the people on the list is your decision and your responsibility. We build the list; we do not run outreach.
Tell us what you needSee typical projectsA written scope before we start, so you know what you're getting before work begins.
What we hear from businesses before a project like this starts.
The requests that come up most often for this kind of work, and what each one takes to work properly.
You describe who you want, such as trade, size, area or a recent registration, and we turn that into a search across public sources.
Company name, registered address, status, filing dates and officers as published, one file per group of data.
Trade directories and association member pages collected into one sheet, with the same business merged where it appears in several.
Phone numbers, general email addresses and contact pages that the business shows on its own site, with a note of where each was found.
The source link and the date collected beside each value, so you can check any row or drop a whole source.
Names and addresses put in one style, duplicates merged, closed businesses and dead websites flagged, and role addresses such as info@ kept apart from named people.
Records created in HubSpot, Zoho, GoHighLevel or your sheet with fields mapped, a source tag added, and your existing customers and do-not-contact list left out.
The same search re-run on a schedule, new and changed businesses flagged, and the row count checked on every run.
Tools that come up most: Python, public company registers, trade directories, the Google Places API, Google Sheets, Excel, CSV, HubSpot, Zoho CRM, GoHighLevel, Airtable, email verification services.
Concrete pieces, each one something you can open and check when it's done.
Who you want, where, how many, which fields, and which sources are in or out, written down and agreed before collection starts.
Written brief, column listAbout a hundred rows from the first source, with the column list agreed, before the full list is built.
Sample file, column listScheduled collection at a polite pace from registers, directories and company websites, using an API, feed or download wherever one exists.
Python, APIs, scheduled runsNames and addresses standardised, the same business matched across sources, and closed or duplicate entries flagged.
Matching rules, address standardisingEvery value keeps the link it came from and the day it was collected.
Source column, date columnAddresses checked for format and for whether the domain accepts mail, through a verification service you choose, with the result in its own column.
Email verification serviceRecords created with your fields mapped and a source tag, skipping customers and do-not-contact entries you give us.
HubSpot, Zoho, GoHighLevel, Airtable APIsPages requested, rows saved, rows rejected, and an alert when the row count drops, so a changed source is noticed.
Run log, alertsExample packages to show the shape of the work. These are examples, not past clients; yours gets its own written scope.
Example package
About a hundred rows from one source, so you can judge the fit before a full list.
You get
Example package
The whole list, cleaned and ready to use.
You get
Example package
The list loaded as records in the CRM you use.
You get
Example package
The same search re-run, with changes flagged.
You get
The habits that keep this kind of project from going wrong.
We collect from sources that anyone can open: registers, directories and the businesses' own pages. Nothing that sits behind a login you have no right to use.
Each value keeps the link it came from and the date, so a doubtful row can be checked in one click.
We use an API, feed or download where one exists, keep to a polite pace and follow a site's terms. We do not build around blocks or CAPTCHAs. If a source cannot be collected cleanly, the scope says so.
The list is the deliverable. Who you write to or call, and how, is yours to decide under the rules where you and they are. We can keep role addresses apart and your do-not-contact list out, but we do not run outreach.
You describe it. We write it down, build it, and hand it over.
Tell us what you need in your own words, and which tools you already use. A few lines is plenty to start.
We reply with a short written scope: what gets built, what is out of scope, which accounts we need, and how we'll both know it works. You know what you're getting before work begins.
The work is split into milestones. At each one you see it working in your own account and sign it off before we go on.
You get the working system, its documentation and a walkthrough. If anything we built breaks in the next 30 days, we fix it at no charge.
Pushbuild has built software for businesses since 2010, for more than 40 clients. Every project is led by a former public-company CTO, from Groton, Massachusetts. See example builds.
Public business sources: company registers, trade and association directories, and the businesses' own websites. We name the sources in the scope before collection starts, and every row keeps its source link and the date we collected it.
No. We build the list. How you contact the people on it is your choice and your responsibility, including the rules on email, calls and texts where you and they are. We can mark role addresses and keep your do-not-contact list out of the file.
We do not build around protections a site has put up to stop automated collection. We look for an API, a download, a slower pace or another public source for the same businesses. If none of those work, the scope says so before you agree to anything.
We do not collect from sites whose terms forbid it, and social networks generally do. If you export a list from your own account or tool, we can clean it and load it.
Public data goes out of date, so we measure rather than promise. The sample shows you the match rate before the full run, including closed businesses and wrong categories, and the email check column shows the rest.
Yes. The same search can run on a schedule, with new and changed businesses flagged and the row count checked each time. The scheduler sits in your account.
Yes. We map the fields with you, add a source tag, and leave out customers and do-not-contact entries you give us. You get a count of what went in and what was skipped.
You do. The list is yours, and the collection scripts go into a repository you own, with a short run book for the next person.
Once the brief is agreed, the sample comes first. The scope gives a time estimate for the full list, which depends mostly on how many sources there are and how each publishes its data.
For 30 days we repair anything we built that does not work as the scope describes, at no charge. After that, further work is scoped the same way and agreed with you before we start.
Do it once, we automate it. Show us the job one time and it runs on its own after that, in the tools you already use.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com