The Problem
Every sales team needs local business leads, but manually searching Google Maps and copying data is painfully slow. I needed...
For further actions, you may consider blocking this person and/or reporting abuse
The part that stands out is how quickly these tools stop being “just a scraper” and become a full infrastructure problem.
One thing I’d keep in mind is where your app is doing repeated heavy work. If you’re generating previews, thumbnails, map screenshots, or other media assets as part of the workflow, it’s usually better to normalize and deliver those through a dedicated pipeline instead of making the app redo that work on every request.
That doesn’t solve Google’s rate limits, obviously, but it does keep the non-scraping parts of the system from becoming a second bottleneck. In these products, the boring delivery layer can end up being as important as the scraper itself.
Would be cool to have a Zapier integration so I can auto-trigger outreach sequences when new leads are exported. Any plans for that?
Good idea! We're considering Zapier and Make integrations. For now the CSV → HubSpot import workflow works well but direct API integration is on the roadmap.
Nice write-up! Curious about the proxy rotation strategy — are you using residential proxies or datacenter? I've been hitting rate limits with datacenter IPs when scraping at scale.
Started with datacenter but switched to a mix of residential + mobile proxies. The key is randomizing request intervals between 2-5 seconds and rotating user agents. Haven't been blocked since.