Research specification

GMass turns an approved list into a testable Gmail sequence

Email verification, sender authentication, merge-field completeness, suppression status, and reply handling determine whether a sequence is ready for review. They do not guarantee inbox placement or response. This methodology makes every check visible before a person approves sending.

human-reviewed prospect event research method

Structured research specification

Recipient preparation

Input
Approved account list, target roles, verified addresses, exclusions, and suppression records.
Output
A recipient table with verification state, merge fields, and unresolved rows.
Boundary
Verification signals can age; uncertain addresses stay out of the send queue.

Sender readiness

Input
Gmail account scope, sending policy, SPF, DKIM, DMARC, and suppression controls.
Output
A documented preflight state with unresolved authentication or policy issues.
Boundary
Authentication supports trust but cannot guarantee inbox placement.

Decision-maker research

Input
Buying function, seniority, responsibility clues.
Output
Role candidates with verification status and evidence.
Boundary
Titles vary; responsibility must be reviewed.

Outreach preparation

Input
Approved account evidence and message constraints.
Output
A restrained draft for human editing.
Boundary
No automatic sending or response guarantee.

Numbered methodology

  1. Write observable criteria.

    Replace “promising startup” with industry, operating region, company stage proxy, dated change signal, and disqualifiers.

  2. Resolve the entity.

    Compare legal name, operating name, website domain, location, and event participants before combining records.

  3. Separate fact from inference.

    Store the source-supported event independently from the commercial interpretation your team wants to test.

  4. Review the smallest cohort.

    Measure false positives, unresolved fields, source freshness, review time, and downstream correction work.

  5. Approve outreach separately.

    Verify professional contact data, suppression status, applicable regional rules, and human-edited relevance.

Run the method on accounts you already know

A known cohort reveals whether identity, event timing, and role interpretation meet your internal acceptance policy.

Score each candidate against a written rubric: correct entity, event inside the stated window, source available, required role supported, exclusions respected, and reviewer decision recorded. Report unresolved fields separately from rejected matches so coverage gaps do not disappear inside a single accuracy percentage.

npx -y @okki-global/okki-go-taroball