Sales and marketing teams use reverse IP identification to turn anonymous site traffic into named company accounts worth pursuing. The workflow breaks down the moment an ISP, a cloud hosting provider, or a VPN endpoint gets returned as the 'company' — which users across multiple tools report happening constantly. You can't build a pipeline from 'Comcast Business' or 'Amazon AWS' as a visitor record.

The reason this stays broken is that reverse IP lookup is a fundamentally noisy signal, and enrichment vendors tend to bolt company data onto it without a filtering layer that distinguishes 'a company visiting from their office' from 'a company visiting through a shared infrastructure provider.' The people who build the underlying data are database engineers; the people who suffer when it's wrong are SDRs and demand gen managers who may not even know why their visitor list is full of ISPs.

What's missing is a classification layer that sits between the raw IP resolution and the CRM record — one that can reliably suppress infrastructure providers, telcos, hosting companies, and known residential ISPs before a lead ever appears in a rep's queue. Users specifically complain that ISPs are 'displayed as companies' and that smaller or less-known organizations are frequently misidentified. An 80% accuracy ceiling is common feedback, which means one in five records is actively misleading.

This is a business and not a feature because every marketing team running account-based campaigns re-ingests new visitor data continuously. Bad company identification means ABM target lists are polluted with noise, ad suppression lists miss actual customers, and personalization logic fires on the wrong account. The cost is diffuse but recurring — wasted ad spend, wrong account scoring, reps chasing ghost leads — and it compounds quietly until someone audits the data.

What to build

Build a real-time API layer that takes raw reverse-IP company identifications, runs them through a multi-signal classifier — ASN type, company size signals, known hosting/ISP registry, domain category — and returns a verified company match with a confidence score and a suppression flag for infrastructure entities, designed to sit between any IP lookup service and a CRM or MAP.

Where to start

Target teams using a specific popular reverse-IP tool that has no filtering layer and is widely cited for ISP noise — offer a middleware connector that cleans output before it hits their CRM, positioning it as a 'data quality filter' rather than a competing product.

The hard part

The classifier needs to handle edge cases where a legitimate SMB routes traffic through a shared business ISP — suppressing too aggressively kills valid leads, and if false negatives are visible, buyers blame the product even when the upstream data is the actual problem.

How it makes money

Monthly subscription priced by volume of enriched visitor records processed, with tiers based on monthly unique visitors identified — scales naturally as traffic grows.

See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Lead Capture.

More ideas in Lead Capture