The everyday problem
Turn search results into useful contacts.
A long list is not much use when sources are missing or the same shop appears three times. I build research tools that help you find relevant businesses, check their data and put the results to work.
Turn individual results into a traceable dataset with sources, useful fields, deduplication and a clear next step. Discovery and enrichment stay separate so failed lookups can be retried. We agree on scope, permitted source use and the required data before implementation.
What we will work on together.
The scope follows your project.- 01
Search with a purpose
Scoped research by industry, region or defined directories
- 02
Bring the data together
A shared data format, deduplication and agreed enrichment
- 03
Use the results
Searchable results, filters and exports that fit the workflow
- 04
Keep track of lookups
Visible run status and retryable lookups, with CRM integration where needed
From my work
See what this looks like in practice.
Shop research and contact pipeline
From a shop directory to contacts a sales team can use.
Public shop directories become usable data: cleaned, enriched, searchable and ready to export.
- Separate discovery and enrichment
- Deduplicate returning shops
- Search and export contacts
- Python
- Next.js
- MongoDB
- +3
Regional business research
Find the businesses around your next opportunity.
Industry, location and radius become a systematic search. Four directories provide businesses and enriched contact details.
- Four sources, one radius search
- Cover regions by postcode
- Enrich contact details automatically
- Python
- Playwright
- MongoDB
- +1
Research and outreach automation
Find the right brand. Reach the right person. Keep the thread.
From relevant brands to the right contact and a deliberate follow-up. A daily view keeps the next steps visible.
- Find brands from real opportunities
- Connect research and contact sequences
- Keep follow-ups visible
- Next.js
- TypeScript
- PostgreSQL
- +3
Our first conversation
What makes a result worth keeping?
You do not need a finished technical specification. Your idea, an example or a look at the current workflow is enough to start.
Let us talk it through- 01
Which businesses or shops are you looking for, and what makes a result relevant?
- 02
Which sources and fields should be used, and how do you intend to use the data?
- 03
How should results be reviewed, exported or connected to your CRM?
You might also be wondering:
Felix SchumannAI automation engineerName it, I build it.
If something here looks like the problem you have, write to me. A short description of what is not working is enough to start.