Use this guide to run Lead Discovery reliably.
Lead Discovery is optional. Satua remains your CRM workspace whether records arrive from CSV, manual entry, lists, or a connected data source.
Setup Checklist
Before enabling a schedule:
- Data connection status is
connected. - Provider terms and Satua DPA summary have been acknowledged.
- ICP is described in the discovery's chat panel.
- Schedule is set to
manual,daily, orweekly. - Leads per run is configured (maximum 100 per run — see Why per-run is capped below).
- Optional per-run cap is configured if your team needs a lower ceiling than 100.
- Optional monthly cap is configured if your provider quota requires one.
- Any compliance gate has been acknowledged by a account admin.
Run Status Meanings
| Status | Meaning |
|---|---|
| Completed | Run finished successfully. |
| Partial | Run finished, but fewer unique records were inserted than requested. |
| Retrying | Run is still attempting another pass. |
| Failed | Run did not complete successfully. |
A Partial run is usually a signal about your ICP, not a system outage. It often means the ICP is too narrow, available unique records are running low, or your Hunter credits / criteria constrained the run.
What Run History Shows
Run history focuses on operational facts:
- Requested volume.
- Inserted volume.
- Duplicate count.
- Rejected count.
- Runtime and trigger.
- Error message, if any.
Satua's internal quality-control and orchestration details are intentionally not documented here.
Cap Behavior
Satua enforces configured limits before or during execution:
- Requested target volume (hard ceiling: 100 per run, platform-wide).
- Per-run cap, when set lower than 100.
- Monthly remaining volume, when set.
- Provider-side quota or plan limits.
If monthly remaining volume is zero, the run is rejected before execution.
Why Per-Run Is Capped At 100
Lead Discovery is tuned for quality over volume. The 100/run ceiling is platform-wide and not negotiable. Beyond that ceiling:
- Duplicate rates climb sharply as Satua works the same ICP slice repeatedly.
- Hunter credit consumption scales linearly without proportional unique-record gain.
- Quality-control passes lose focus, increasing the chance of a partial-completion outcome.
If your team needs more than 100 records per day, use a daily schedule instead of pushing a single run higher. Two daily runs of 100 reliably outperform one large run — Satua gets a fresh dedup snapshot, fresh provider state, and a clean budget per execution.
Troubleshooting Matrix
| Symptom | Likely cause | Checks | Fix |
|---|---|---|---|
| + New Discovery is disabled | DPA not acknowledged, no connected provider, or all discovery slots are in use | Lead Discovery page banners and slot count | Acknowledge DPA, connect provider, or archive an old discovery |
| Run blocked before start | Monthly cap exhausted or compliance gate pending | Discovery settings and compliance banner | Raise cap, wait for next month, or acknowledge compliance gate if appropriate |
| Failed with auth or permission error | Hunter API key invalid, revoked, downgraded, or missing the Discover endpoint | Settings → Data Connections → Test | Rotate key, restore your Hunter plan, and retest |
| Repeated Partial runs | ICP too narrow, market saturated, or Hunter credits low | Run history, duplicate count, inserted count, ICP chat | Broaden ICP, lower target volume, or adjust cadence |
| Want more than 100 leads per day | Per-run cap is 100 platform-wide | Schedule and discovery setup | Switch to a daily schedule — two runs of 100 yields better quality than one large batch |
| High duplicates, low inserts | The current market slice overlaps records already in your account | Duplicate count and existing CRM density | Broaden criteria or steer toward a different segment |
| Zero-yield but no provider error | Over-filtered ICP | Titles, seniority, location, exclusions | Relax one dimension at a time |
| Provider details hidden on leads | Rights prompt not accepted | Lead detail -> Provider Details | Acknowledge only if your account has rights to display those fields |
Recommended Operating Cadence
- Start with manual runs while calibrating a new ICP.
- Move to weekly once quality is stable.
- Move to daily only when your team can review and work the volume.
- Track insert rate, duplicate rate, and rep feedback together.
- Treat persistent partial runs as an ICP/schedule tuning signal.