Skip to main content
Leads.sh

Solution: RevOps

Give lead operations a workflow your team can audit.

Leads.sh turns list building into visible operations: queued jobs, credit spend, cache behavior, provider policy, exports, and downstream handoff.

Book demoPricing table
Dark analytics dashboard with charts

Scraped lead

1 credit

Cache hit

2 credits

Verified email

5 credits

Visible rates
Default rates are documented in the marketing site and surfaced inside the product with live balances.
Ordered waterfall
Provider order belongs to your API configuration, so Apollo, Hunter, cache, and other sources follow deployment policy.
Selective expansion
Teams can scrape first, then choose which leads deserve verified email discovery or deeper contact enrichment.

Operational control

Credits and job state stay visible before work expands.

The model is intentionally concrete: scraping, cache hits, and fresh provider calls are presented as different operations.

Use one default credit per scraped lead.
Use lower-cost cache hits where the deployment has data.
Reserve higher-cost verified email waterfall calls for selected records.
Show live balances and configured policy after sign-in.

Provider policy

Enrichment follows the order your stack is configured to use.

The marketing claim stays close to the product: Leads.sh runs the configured waterfall, not a mystery database promise.

Keep API keys in the server environment.
Handle cache before fresh provider work where configured.
Expose enrichment state back to the lead table.
Pair enrichment with exports and CRM action paths.

Operator notes

Specific boundaries make the product easier to trust.

Best fit: RevOps teams that need to explain data spend, job progress, and handoff before a list build starts.
Not positioned as: a bundled global contact database with guaranteed coverage.

Keep exploring

More detail for the rest of the workflow.