Satua
← All docs

Lead Discovery Onboarding Quickstart

Fast launch path for tenant-owned data connections, ICP chat, and first discovery run.

This quickstart is for account admins and managers launching Satua Lead Discovery.

Satua does not provide, sell, broker, or resell leads. Lead Discovery runs against data connections your organization controls. Satua's role is CRM workflow, orchestration, deduplication, auditability, and outreach readiness.

You can use Satua without Lead Discovery by importing CSV files or adding leads manually.

Before You Start

Make sure you have:

  • A account admin or manager account.
  • A supported provider account your organization is authorized to use.
  • An API key or credential with the provider permissions required for search and enrichment.
  • Confirmation that your organization has a lawful basis to process and contact records returned by that provider.
  • A verified sender domain before external outreach.

Lead Discovery requires an active connected data source. CSV import and manual entry do not.

Step 1: Acknowledge the Satua DPA Summary

On your first visit to Lead Discovery, Satua shows a one-time DPA acknowledgment prompt. It covers controller/processor roles, retention, data subject requests, and data-source responsibility.

Click Read the DPA if you need to review the summary, then click I acknowledge when your account is ready to proceed.

Step 2: Connect a Data Provider

Go to Settings -> Data Connections.

  1. Pick a supported provider.
  2. Review the plan requirement shown in the form.
  3. Paste the API key.
  4. Confirm your account has read and accepts that provider's API Terms of Service.
  5. Keep Test connection before save enabled.
  6. Save.

If the connection does not show connected, open Data Connection Setup and use the troubleshooting matrix.

Satua stores the key encrypted and only shows a masked hint after save.

Step 3: Create a Discovery

Go to Lead Discovery and click + New Discovery.

The button is disabled until:

  • The DPA summary has been acknowledged.
  • At least one connected provider exists.
  • your account has an available discovery slot.

In the modal:

  1. Describe your ideal customer in plain English.
  2. Pick the connected provider.
  3. Optionally name the discovery.
  4. Optionally open Advanced to set schedule and volume. Per-run volume is capped at 100 leads — for larger weekly or monthly targets, use a daily schedule rather than a single large run.
  5. Click Create & open chat.

each account can have up to 3 active discovery slots. Archive a discovery to free a slot while keeping history for audit.

Step 4: Refine The ICP In Chat

The discovery detail page includes an ICP chat. Use it to refine the discovery in business language:

  • "Also include Head of Revenue Operations."
  • "Exclude agencies and consulting firms."
  • "Focus more on the Midwest US."
  • "Move upmarket to 500-2,000 employees."

Each accepted change saves a new ICP version. Prior assistant responses can be reverted from the chat when an older version performed better.

Keep the chat focused on target-market facts: industries, company size, locations, titles, seniority, exclusions, and compliance constraints.

Step 5: Run And Validate

On the pipeline detail page:

  • Click Run now for a manual test run, or
  • Click Activate to enable scheduled runs.

Run history shows status, requested volume, inserted volume, duplicate count, rejected count, and errors where applicable. The docs intentionally do not document Satua's internal quality-control and orchestration mechanics.

After the first run:

  • Open Dashboard and confirm inserted records appear.
  • Open a lead and review core fields.
  • If provider details are available, acknowledge the one-time rights prompt before viewing provider-proprietary fields.
  • Assign a few leads and move them through status changes to confirm the CRM workflow is ready.

Step 6: Enable Outreach

Go to Settings -> Email & Domain and verify your sender domain.

Then:

  • Generate an AI draft from a lead.
  • Send a test email to an internal inbox.
  • Confirm unsubscribe and suppression behavior.
  • Launch external outreach only when your team has reviewed the target list and legal basis.

Compliance Gates

Some target geographies commonly require opt-in or special care for B2B outreach. If Satua flags the pipeline, activation is paused until a account admin acknowledges responsibility for lawful basis, outreach rules, and data-subject rights.

The acknowledgment is logged for audit.

Recommended Launch Checklist

  • DPA summary acknowledged
  • Provider connection saved with connected status
  • Provider terms acknowledged in Satua
  • Discovery created with a clear ICP description
  • First discovery run completed and inserted records reviewed in Dashboard
  • Owners, statuses, and follow-up workflow validated
  • Sender domain verified
  • Internal outreach test sent successfully
  • Compliance gate acknowledged if the ICP targets an opt-in-sensitive geography

Related Guides