If you run a service business, you know the math: you spend real money on ads, SEO, and a decent website — and most of the people who visit never call, never fill out a form, never come back. The lead-gen industry's answer was a new kind of tool that secretly identifies those visitors by fingerprinting them and matching them against massive identity databases. No opt-in. No disclosure. No record.
Plaintiffs' attorneys noticed. Lawsuits invoking decades-old wiretapping statutes — like the California Invasion of Privacy Act — started landing on small businesses that thought they'd just bought a marketing tool. The contractor gets the demand letter; the tracking vendor shrugs.
The industry's answer was to track harder and disclose less. Ours was to ask permission.
In late 2025, the three of us were watching this from different chairs. Andy Mentges and Jason Beyke were running VerticalResponse, an email platform that lives or dies by consent and data hygiene — they'd spent years on the right side of that line. Aaron Phillips had spent 20 years marketing hosting and security companies, including executive roles at cPanel, and was deep in privacy-law research while running a marketing shop for plumbers, roofers, and contractors in East Texas. He kept meeting good businesses unknowingly bolted to legal time bombs.
So we founded Consent Resolve in December 2025 around one non-negotiable rule: if you're going to identify a website visitor, the visitor has to say yes first. Stefan Dimitrov — writing production web code since 1999 — engineered the consent log so every single lead carries a timestamped record of exactly when and how that person opted in. It's not a disclaimer buried in a privacy policy. It's a receipt.
That decision costs us something. Consent-first identification produces fewer raw names than covert tracking. But the names it produces are people who raised their hand — which is why the leads convert, and why our customers aren't waiting on a process server. The full legal picture is on our why consent-first page, with sources on our stats & sources page.