Skip to content

fix(leads): stop scanning the businesses a project discovers - #135

Merged
ralyodio merged 1 commit into
masterfrom
fix/no-scan-project-leads
Jul 28, 2026
Merged

ralyodio merged 1 commit into
masterfrom
fix/no-scan-project-leads

Conversation

@ralyodio

Copy link
Copy Markdown
Contributor

Finding leads queued a free CrawlProof scan of every domain it turned up, and new campaigns did the same on every tick.

That only ever made sense for one pitch. The scan supplies findings for "we scanned your site, here's what we found" — so a project pitching its own offer gets nothing from it while still paying for it:

  • worker time spent producing evidence nobody will cite
  • a scanner pointed at people whose only involvement was appearing in a search result
  • prospects stranded at "new", waiting on a scan nothing was going to read

Changes

  • One-shot lead finding never scans. findLeadsAction passes skipScan, so discovery goes straight to contact lookup. The scanning count it used to report is gone rather than left reporting zero.
  • New campaigns default to scanning off.
  • Selecting the audit pitch turns it back on, since that pitch can't be written without findings — that's the escape hatch for the CrawlProof project itself.
  • The lead finder's own description promised a scan it no longer performs, so that copy goes too.

Checks

  • tsc --noEmit clean
  • 748/748 tests pass
  • production build compiles

🤖 Generated with Claude Code

Finding leads queued a free CrawlProof scan of every domain it turned
up, and new campaigns did the same on every tick.

That only ever made sense for one pitch. The scan exists to supply
findings for "we scanned your site, here is what we found" — so a
project pitching its own offer gets nothing from it, while still paying
for it: worker time spent on evidence nobody will cite, and a scanner
pointed at people whose only involvement was appearing in a search
result. It also stranded prospects, since a lead sat at "new" until a
scan landed that nothing was waiting for.

One-shot lead finding no longer scans at all, and new campaigns default
to scanning off. Selecting the audit pitch turns it back on, because
that pitch cannot be written without findings.

The lead finder's own description promised a scan it no longer performs,
so that goes too.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

vu1nz Security Review

0 finding(s) in PR #?

No security issues found.

@ralyodio
ralyodio merged commit 72d7c89 into master Jul 28, 2026
8 checks passed
@ralyodio
ralyodio deleted the fix/no-scan-project-leads branch July 28, 2026 03:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant