Each capability has a defined input, visible output, and review boundary. Yesware does not turn weak evidence into buying intent or a draft into an approved send.
01
Define the account cohort
Translate an ICP into observable firmographic criteria, technographic clues, geography, stage proxies, exclusions, and a freshness window. The output is a candidate set with unresolved attributes still visible.
Review: confirm entity identity and reject criteria widened after the result appeared.
02
Verify contact context
Resolve company domain, function, seniority, employment evidence, professional address status, and provider disagreement. Waterfall enrichment may improve coverage, but every source adds provenance and consistency questions.
Review: separate role relevance, address match, deliverability risk, and lawful outreach basis.
03
Prepare a relevant draft
Use only approved account facts and role context. Avoid fabricated familiarity, private motives, unsupported pain claims, and exaggerated urgency. Preserve source notes beside the message for editing.
Review: check relevance, tone, opt-out language, suppression, and applicable CAN-SPAM, CASL, GDPR, or local requirements.
04
Audit the sequence
Inspect cadence, duplicate prevention, sender reputation, inbox-placement assumptions, hard-bounce handling, and SPF/DKIM/DMARC readiness. Track replies without promising a response rate.
Review: approve each automation boundary and retain an immediate stop path.
Test with accounts your team already knows
A known cohort reveals false matches, stale roles, missing evidence, and weak exclusions before the workflow reaches production. Include positive interest, referrals, timing objections, unsubscribe requests, delivery failures, and ambiguous replies in the test. Preserve original context beside every classification so a reviewer can challenge it.
Sensitive, uncertain, negative, and opt-out responses must stay human-routed, and silence must never be interpreted as permission. Document sender identity, the market policy, suppression sources, and an escalation path before any sequence connects to a mailbox. The safest workflow is the one an operator can pause, explain, and correct without guessing why it made a decision.