Lead and sales systems
A searchable database of the companies and people you sell to, kept fresh, with outreach lists one click away. Assistants draft the follow-ups, and a person sends them.
- 21,900+companies in one database for Growthy
- 2 weeksto ship the first version, against a 4-week budget
- 0messages sent without a person approving them
One list the whole sales team can trust.
Growthy is a Web3 growth agency, and I'm its Head of Technology and Innovation. Its sales team needed to know who to contact, so I built the database they now work from.
A company and contact database
- Source 01
- Source 02
- Source 03
- Source 04
- Source 05
- Source 06
- Source 07
- Source 08
- Source 09
- Source 10
- Source 11
- Source 12
- Northwind Labsnorthwindlabs.exampleSource 03
- northwind labs inc.www.northwindlabs.exampleSource 07
- Northwind Labs (NWL)northwindlabs.example/homeSource 11
Two duplicate rows removed. All three sources stay on the record, each with its date.
- Need
- The sales team had no single, current list of who to contact.
- Built
- A database that pulls about a dozen sources together, removes duplicates and keeps the source and date of every field. The team searches and filters it, opens any record to see where each value came from, and exports a list in one click.
- Outcome
- 21,900+ companies in one database. The first version shipped in 2 weeks against a 4-week budget.
Outreach lists in one click
The database has ready-made lists for the kinds of people the team contacts most. Any filter can also be exported exactly as it is shown.
Every row keeps its source and last-checked dateAn inbox assistant that drafts follow-ups
It reads a team member's inbox, works out which conversations need a reply or a follow-up, and drafts one in that person's voice. Each draft is compared with what the person actually sent, so the next ones sound more like them.
Read-only. A person sends every messageA job-board watcher
I built this for my own contract work. It scores each new posting for fit and has a proposal draft waiting for the good ones. I read the draft and submit it myself.
It has no way to send anythingEvery field says where it came from.
A list is only useful if you can trust it. So each value in a record keeps two things beside it: the source that supplied it and the date it was last checked.
- Website
- northwindlabs.example
- Source 03 · 2 Nov 2026
- Category
- Developer tools
- Source 07 · 28 Oct 2026
- Team size
- 11 to 50 people
- Source 11 · 2 Nov 2026
- Based in
- Lisbon, Portugal
- Source 07 · 28 Oct 2026
- Contact
- Head of Partnerships
- Source 03 · 15 Nov 2026
- partnerships@northwindlabs.example
- Source 11 · 15 Nov 2026
- You can see where a value came from
Each field carries the source that supplied it. If something looks wrong, you know where to look.
- You can see how old it is
Each field carries the date it was last checked, so nobody builds a list on stale details.
- Your corrections stay put
A new source fills in blanks. It never replaces a value that is already there, so a fix your team makes survives every later update.
Ask a question, get a list, keep the conversation going.
The database is the start. The same system turns a filter into a list your team can use, and drafts the follow-up so no conversation goes quiet.
- 1 · FilterCategory: Developer tools Role: Partnerships Has a verified email Checked this month
38 companies match
- 2 · List
- Northwind LabsHead of Partnerships
- Acme ProtocolBusiness Development Lead
- Example HarborPartnerships Manager
- Placeholder ChainHead of Growth
and 34 more
- 3 · Exportpartnerships-list.csv38 rows · ready
Each row keeps its source and last-checked date.
- 4 · Follow-up draftTo: Northwind Labs · Head of Partnerships
Hi Alex, good to meet you last week. You mentioned the launch is moving to January. Would a short call on Tuesday work to go through the plan?
Waiting for a person to approve
From scattered sources to one working system.
It starts small, with one source and one list, and grows from there.
- 1Define who you sell to
We agree on what a good customer looks like and which sources list them. That decides what goes in.
- 2Pull the sources together
Every source goes through the same path, so a company listed in three places becomes one record.
- 3Keep the source and date
Each field records where it came from and when it was last checked. You can see how far to trust it.
- 4Build the lists
Filters your team can use without help, and ready-made lists that export in one click.
- 5Add follow-up help
An assistant drafts the next message. A person reads it, changes it if needed, and sends it.
What people ask first.
How does the data stay fresh?
The system checks its sources again on a schedule, so nobody has to remember to update it. The team can also start a refresh by hand when they want one sooner. Running a source twice is safe, because nothing is added a second time. Every field shows the date it was last checked, so you can see how old a value is before you rely on it.
Does it send anything automatically?
No. Nothing is sent without a person approving it. The inbox assistant can read and draft, and it cannot send. A person reads each draft and sends it. My own job-board watcher works the same way: it drafts the proposal and I submit it myself.
What happens when the same company shows up twice?
It happens constantly, because sources spell names and web addresses differently. Clear matches are merged into one record, and every source that listed the company stays attached to it. When the evidence conflicts, the system does not guess. It puts the pair in a review list for a person to decide.
Can it use the spreadsheets and lists we already have?
Yes. A spreadsheet upload goes through the same path as every other source. It is matched against the records already there and fills in the blanks. It never replaces a value that is already in place, so a correction your team made by hand stays.
How long does a system like this take to build?
It depends on how many sources you need and how tidy they are. For Growthy, the first version shipped in 2 weeks against a 4-week budget. I start with one source and one list your team will use straight away, then add the rest.
Need a lead system like this?
Add it to your stack with anything else you need, and I'll come back with how I'd approach it. Or send me a few lines about the project.
