Qualified B2B leads, with the evidence attached
The one field that qualifies a church-giving SaaS prospect — which donation platform they use today — isn’t for sale. This 11-stage pipeline reads it off each church’s own site and ranks them for outreach.
A real scan of North County San Diego, replayed
Every number is from one end-to-end run in July 2026. Press replay to watch 932 raw map records compress to 317 scored, evidenced prospects.
This replays a real scan in seconds. The live pipeline runs politely over ~2–3 hours across ~500 church servers — which is exactly why this page is cached and not a live button.
The 317, sorted into outreach buckets
The payoff is the 37 “rails-only” churches — on a bare PayPal or Venmo button with no church tool. They’ve proven they want digital giving and have nothing purpose-built doing it. A column no purchased list contains.
A machine built to distrust itself
932 raw records → 317 scored prospects
Detected platforms — 1,208 evidenced detections
Fingerprinted against 32 platforms and 189 signals — and only inside a real surface (a script src, an iframe, the give button’s destination), never loose prose.
Sample classifications (names withheld)
Real rows with the church name removed. The pipeline extracts names and emails, but a public demo shouldn’t publish a targeting list of real congregations or the people who work there.
| Church (generalized) | Platform detected | Bucket |
|---|---|---|
| Non-denominational · Vista · small | PayPal (direct) | Top prospect |
| Adventist · Oceanside · small | Venmo (direct) | Top prospect |
| Episcopal · Escondido · small | PayPal (direct) | Top prospect |
| Non-denominational · San Diego · small | Planning Center Giving | Switch play |
| Episcopal · Del Mar · small | Breeze ChMS | Switch play |
| Episcopal · Vista · small | Tithe.ly | Suppress |
| Non-denominational · Oceanside · micro | — none found | Greenfield |
| Methodist · Encinitas · small | unresolved (JS-rendered) | Review |
Why I threw out the obvious data source
Google Maps Platform ToS 3.2.3 forbids storing Places names and addresses outside the service — exactly what a prospecting pipeline does. Overture (CDLA-Permissive / Apache-2.0 / CC0) is licensed for it, and returns more churches and an email for 6 in 10.
| On the same region | Google Places | Overture (chosen) |
|---|---|---|
| Religious places found | 913 | 1,019 |
| Have a website | 82% | 82.7% |
| Have an org email | 0% | 61% |
| Cost per lead | ~$0.17 | $0 |
| Licensed for this use | Prohibited | Permitted |
I’d work the buckets in order. The 37 rails-only churches go first — the pitch writes itself (“I noticed you take gifts through a PayPal button”), no incumbent to displace, small enough to decide fast, and every rep opens with a true, specific observation that earns the meeting.
The 128 on a competitor are a second wave; the 28 existing customers get suppressed. Because every row carries the evidence and source URL, a rep verifies any claim in one click. The unlock is the economics: ~$0.04 per evidenced lead makes it a repeatable engine I can point at any metro.
Limits & honesty
A proof of concept I built for myself — no client, no NDA. Here's where it's honest about what it can and can't do.