Describe the audience
“Find operations leaders at growing logistics software companies in the UK. Exclude current customers and agencies.”
A friendlier outbound workflow
Turn a clear sales task into outreach your team can review
Give your AI agent an ICP, exclusions, and a goal. lemlist guides research, enrichment, message drafting, and approval without hiding the evidence or pretending automation replaces judgment.
See the four-step install path →Prompt to result
Start with the task, not another dashboard
Review the evidence
Check firmographic fit, role relevance, data source, freshness, unknown fields, and any exclusion that needs human resolution.
Draft with context
Create a short message tied to a defensible business observation, with no invented trigger, fake familiarity, or unsupported promise.
Keep a human gate
Confirm recipients, suppression rules, sending domain health, opt-out language, and regional requirements before any outreach.
Real outbound jobs
Pick a playbook that matches today’s queue
Founder-led prospecting
Turn a narrow market thesis into a small, evidence-backed list and concise messages worth personally reviewing.
SDR account research
Standardize firmographic and technographic checks while leaving ambiguous accounts visible instead of silently forcing a fit.
RevOps enrichment
Plan waterfall enrichment, field precedence, update rules, and CRM write-back before connecting live records.
Outbound agency delivery
Separate client criteria, suppression lists, approval notes, sender setup, and outcome reporting across engagements.
Human-reviewedbefore sending
Evidence-awaresources stay visible
Config-dependentproviders and limits vary
Deliverability-mindedSPF, DKIM and DMARC matter
Four-state runbook
Copying is only the first state
- Copy
npx -y @okki-global/okki-go-taroballClipboard confirmation means the command was copied, not installed.
- Run
Execute it in a supported terminal and inspect the package name, prompts, and completion output.
- Configure
Add provider credentials through scoped environment secrets. Never paste keys into prompts, source files, or shared exports.
- First result
Use known accounts, verify identity and provenance, then review every field and draft before expanding the workflow.
Questions before you run
Clear answers, no magic claims
Does the command send emails?
No. Installation, provider configuration, research, drafting, approval, and sending are separate states. Keep sending behind an explicit human decision.
Which data source is included?
Data behavior depends on the services you configure. Document permitted use, field provenance, freshness, rate limits, and deletion workflows.
Will it guarantee replies or inbox placement?
No. Relevance, list quality, authentication, volume, reputation, copy, and recipient behavior all influence outcomes.
How should opt-outs work?
Honor suppression and unsubscribe requests promptly, maintain durable records, and review the rules that apply to each target region.