Begin with a narrow account hypothesis, collect only the evidence needed to evaluate it, preserve provenance, verify separately, and treat ambiguity as a reason to exclude. Never confuse deliverability with permission or relevance.
Start with accounts, not addresses
Define observable company characteristics tied to the offer: industry, business model, geography, product event, technology, hiring signal, or regulatory need. Identify companies that match, then determine whether a specific role plausibly owns the problem. This order prevents a large email database from becoming the strategy.
Write exclusions with the same care as inclusion rules. Existing customers, active opportunities, competitors, unsupported geographies, unsuitable company sizes, generic personal accounts, and previously suppressed recipients should be removed before enrichment.
Keep a compact provenance record
Provenance makes review possible and deletion meaningful. Storing an entire page forever is usually unnecessary; store the minimum evidence and a reference unless a specific retention need justifies more.
- First-party company domain and exact source URL
- Observation date and the fact supporting account fit
- Role or contact rationale
- How the business address was obtained or derived
- Verification result without flattening catch-all or unknown states
- Geographic and policy checks
- Prior contact, reply, opt-out, bounce, or complaint state
Verification answers a narrow question
An address verifier may classify an address as deliverable, invalid, disposable, catch-all, or unknown. Preserve those distinctions. “Valid” does not mean the person is appropriate, wants the email, holds the inferred role, or falls within the provider’s acceptable-use policy.
Do not manufacture confidence by guessing many address patterns and sending to see which one survives. That transfers the uncertainty to recipients and mail systems. Ambiguous identity should lower volume, trigger research, or exclude the record.
Compliance is broader than the list source
For U.S. commercial mail, the FTC highlights accurate identity and subjects, location disclosure, a clear opt-out, prompt suppression, and responsibility for vendors acting on the sender’s behalf. It also states that B2B email is not categorically exempt. Other countries and states may impose different or stricter rules; obtain qualified advice for the actual geography and data flow. [2]
Provider policy is an additional gate. Document the use case honestly and get approval where necessary. A list can be lawful to maintain yet prohibited on a particular platform.
A useful agent output explains every inclusion
Ask the agent to output the company, public source, observed fact, target role, relevance sentence, uncertainty, and exclusions checked. Sample the results manually before allowing enrichment or sending. Track false-positive reasons and revise the ICP, not just the copy.
Actually Agentic is designed around agent-supplied company seeds and bounded first-party sourcing rather than indiscriminate cross-site collection. It remains prelaunch, but the discipline of a reviewed source manifest can be used with any tool. [1]
Common questions
Questions, answered plainly
Is it ethical to email a publicly listed business address?
Public availability alone is not enough. Evaluate relevance, expectations, applicable law, source restrictions, provider policy, identity transparency, minimization, and easy suppression.
Does email verification create consent?
No. Verification estimates technical deliverability; it does not establish permission, lawful basis, relevance, or platform acceptance.
What is list provenance?
A record of where the account or contact evidence came from, when it was observed, why it supports inclusion, and which processing steps followed.
Evidence
Sources and methodology
Product capabilities were checked against first-party documentation available on September 9, 2026. Policies, plans, and prices can change; verify them before buying. General guidance is educational and is not legal advice.
- Actually Agentic product overview Actually Agentic. Product scope and operating model.
- CAN-SPAM Act: A Compliance Guide for Business U.S. Federal Trade Commission. Official U.S. guidance for commercial email, including B2B messages.
Your agent can do the thinking.
The infrastructure still needs a grown-up.