USE CASE ROUTER
Different operators need different evidence. Start with the business decision, constrain the task, and keep a review gate between an agent result and downstream outreach.
OPERATOR WORKFLOWS
Brief: named segment, region, account criteria, exclusions, and target role. Output: a shortlist with selection reasons, role hypotheses, contact status, and source notes.
Guardrail: verify critical contact fields and approve every message before sending.
Brief: one narrow problem, a recognizable company pattern, and an offer hypothesis. Output: a small set of accounts plus the open questions that block confident outreach.
Guardrail: do not turn an exploratory result into a market-size claim.
Brief: accepted fields, source policy, update rules, and null handling. Output: proposed enrichment with provenance, checked time, and conflict status.
Guardrail: govern waterfall enrichment and remote retention provider by provider.
Brief: input source, permission scope, processing step, review checkpoint, and destination. Output: a reproducible path with configuration-dependent behavior labeled.
Guardrail: use least-privilege credentials and test rate limits and failure handling.
Brief: representative task, quality rubric, cost boundary, and approval policy. Output: test results that separate setup friction, research quality, review effort, and downstream readiness.
Guardrail: compare measured workflows, not unverifiable performance promises.
Brief: client-specific ICP, exclusions, credentials, voice, and approval owner. Output: isolated research and draft artifacts for the correct client reviewer.
Guardrail: never reuse secrets, suppression data, or unapproved claims across clients.
SELECTION GUIDE
A good agent brief is less about prompt cleverness and more about operational boundaries. If any answer is unclear, narrow the task before adding automation.
Research, enrichment, prioritization, or message preparation require different evidence.
Explicit exclusions prevent a broad total addressable market from becoming a noisy daily list.
Email verification, title freshness, and role relevance should not share one confidence label.
Name the human owner for list acceptance, copy review, suppression, and send decisions.
Plan package removal, key revocation, destination cleanup, and retention checks before production use.
Copy the installer, review the runtime output, configure the minimum access, and inspect a first result.