Brief
Define the ideal customer profile, permitted regions, relevant roles, exclusions, offer, and evidence standard before discovery begins.
Data coverage and roadmap
A controlled path from prospect brief to reviewed outreach
Our direction is practical: make each campaign state observable, preserve uncertainty, and keep activation under human control. The roadmap is an evaluation framework, not a promise of future features or guaranteed platform outcomes.
“A useful automation record explains who entered a sequence, why they qualified, which channel acts next, and who can stop it.”
Expandi-oriented analysis concentrates on LinkedIn and multichannel prospecting. It treats profile matching, message relevance, account conditions, sender reputation, reply classification, suppression, and deletion as connected operational decisions. A list size or activity count alone cannot demonstrate quality.
Roadmap graphic: five review gates
Resolve
Check profile and employer identity, retain source dates, and send conflicts or stale roles to an exception queue.
Sequence
Make LinkedIn, email, and manual steps visible with timing, limits, branch rules, and explicit stop events.
Approve
Review targeting and messages separately. Reject unsupported personalization, sensitive attributes, and ambiguous contact status.
Observe
Record acceptance, replies, opt-outs, bounces, corrections, review time, and account-health signals for a defined cohort.
Milestones as testable states
Installer integrity
Confirm the exact package, runtime requirements, files created, network activity, and uninstall path in a disposable environment.
Credential boundaries
Grant minimum scope, keep secrets out of prompts and logs, document revocation, and verify isolation between workspaces.
Known-cohort validation
Use profiles with known correct disposition. Measure false matches, unresolved records, exclusions, message edits, and stop-condition behavior.
Production readiness
Assign campaign ownership, escalation, suppression, retention, deletion, monitoring, and incident procedures before increasing volume.
No partnership, customer relationship, certification, LinkedIn endorsement, compliance status, match rate, deliverability rate, or future release date is asserted. Evidence should come from current documentation and the team's own controlled tests.
Start the roadmap with an inspectable installation
Copy the command, distinguish each state, then validate a first result against a written acceptance rubric.
npx -y @okki-global/okki-go-taroball