Begin with fit and permission
Define the business audience before you collect a row of contact data.
Outbound starts with a business reason to contact a narrow group, not a large list. Write the account criteria, roles, locations, exclusions, problem you can help with and the evidence behind the message. For a facilities-services company, that might be operations leaders at multi-site commercial properties in a defined service area, excluding existing customers and anyone who has opted out.
Apollo’s people search can filter prospects by criteria such as title, seniority and organization information, but its search response does not return email addresses or phone numbers. Treat research, enrichment and contactability as separate stages. In Clay, use the selected validation process to identify a usable result, deduplicate and exclude rows that fail the brief. That separation helps the team review whether a person belongs in the audience before any contact data or message enters a sending system.
- State the legitimate business reason and the specific offer before defining filters.
- Keep suppression, current customers, competitors and sensitive categories out of the starting audience where applicable.
- Collect only fields needed for review, personalization and the next authorized transfer.
Use a controlled row map
Make each system’s input, output and approval point visible.
- 01
Research a small Apollo set
Use the agreed account, role and location filters to create a small reviewable set. Export or call the documented API only under the account permissions and limits the team has approved.
The first output is a research set, not an instruction to contact everyone in it.
- 02
Enrich and validate in Clay
Map the minimum fields into Clay: company, role, domain, service-area fit, verification status and approved personalization inputs. Mark a row for exclusion when the evidence is missing, stale or outside the brief; keep deduplication and exclusion reasons visible to the reviewer.
A row should have an explicit approval state before it can leave the review table.
- 03
Prepare an approved transfer
Use an authorized vendor API with the documented request and fixed field map, or a reviewed CSV with the same columns. Include the reviewer and approval date with every transfer record so the team can identify what moved and why.
Keep the transfer map with the campaign record so an owner can audit what fields moved and why.
- 04
Prepare the existing Smartlead campaign
Set up the campaign, messages, sender rules and suppression policy inside Smartlead under the team’s own account and review process. Clay’s Smartlead action adds a lead to an existing campaign; it does not create that campaign. Import a controlled test batch to an existing drafted campaign, then activate only after the team has reviewed the mapping and sender setup.
No row enters an active sequence until the owner approves both the list and the message set.
Illustrative finished architecture
Beacon Works keeps research, approval and response handling as separate jobs.
Operate after approval
Make replies, opt-outs and CRM updates part of the design before anything sends.
The owner reviews the audience, the selected rows, the message set, the existing campaign and the suppression policy before a transfer reaches an active sequence. That approval should identify the source set, the review date and the person responsible for handling replies. A technical transfer can be correct while the business decision to contact someone is still wrong; keep both checks visible.
If the team needs replies, bounces, unsubscribes or qualified conversations reflected in a customer-owned CRM, it separately configures and verifies that webhook or export path before relying on it. Provider test events for a reply and unsubscribe should reach the owner’s review path before the team depends on them. Record the outcome and suppress records that should not receive further sequence activity. Do not infer delivery, inbox placement or conversion from a successful API call or CSV import. Review the workflow with real operating evidence before expanding it.
- Use sample rows to test the field map, approval state and suppression logic before a live transfer.
- Keep a human owner for reply handling and an explicit process for opt-outs and corrections.
- Pause the transfer when audience criteria, message approval, sender rules or suppression policy changes.
Reusable outbound operating brief
Write the operating decision before creating a list or connecting an API key.
Business offer and reason to contact: [specific value]. Account criteria: [industry/location/size]. Roles and exclusions: [titles, current customers, suppression]. Apollo research fields: [minimum set]. Clay validation rules: [fit and exclusions]. Transfer method: [authorized API or reviewed CSV]. Smartlead campaign and approval owner: [existing campaign/owner]. Reply, opt-out and CRM owner: [person/process].
A field map is not permission to send. Approval belongs to the selected audience and message set, not just the technical connection.