Skip to content

OYN UK ICP Adaptation Plan (Leadgen + Cold Outreach Stack)

Context

This folder contains the existing AgentFlow UK media-market outbound research and sample Vayne exports.

For OYN, we are reusing the same operational stack and adapting targeting + qualification to OYN's UK ICP once ICP/keyword research is final.

Confirmed stack to reuse

  • LinkedIn Sales Navigator (discovery)
  • Vayne export flow (lead extraction from Sales Nav)
  • Enrichment waterfall (Icypeas → Prospeo, email-focused)
  • Email verification step (provider to confirm: Prospeo/MillionVerifier/other)
  • Zapmail + Instantly (sending + sequencing)

Note: keep this document scoped to ICP discovery + list quality adaptation. Sequence copy/outreach strategy is tracked separately.


What we already have in this repo

  • Sample extracted lead datasets:
  • docs/leadgen-coldoutreach/leads/1-10-Employees-AgentFlow-Ads-8-Jan-advanced.csv
  • docs/leadgen-coldoutreach/leads/11-50-Employees-AgentFlow-Ads-8-Jan-advanced.csv
  • docs/leadgen-coldoutreach/leads/50-200-Employees-AgentFlow-Ads-8-Jan-advanced.csv
  • Prior workflow research + implementation notes:
  • docs/leadgen-coldoutreach/research/waterfall-implementation-complete.md
  • docs/leadgen-coldoutreach/research/waterfall-complete-package.md
  • additional enrichment/community research docs

OYN adaptation objective

Convert the existing AgentFlow-oriented leadgen process into an OYN-specific UK accounting/virtual FD ICP pipeline.

OYN target segments (to lock after Prompt 3 output)

  1. Practice owners / managing partners (accountancy/bookkeeping firms)
  2. Advisory-led accountants
  3. Virtual FD / fractional CFO operators
  4. Delivery leads in accounting practices (client manager / advisory manager)

Adaptation workflow (once ICP research lands)

Phase 1 — ICP filter definition

From Prompt 3 output (gtm-deep-research-prompts): - Title taxonomy (include UK variants + exclusions) - Company/firm size bands - Service-model qualifiers (advisory, management accounts, outsourced FD) - Geographic scope (UK first)

Deliverable: icp-filters-oyn-v1.json (new file)

Phase 2 — Sales Navigator query rebuild

Replace AgentFlow media-market searches with OYN-specific saved searches.

For each search: - include positive title/keyword filters, - include exclusions to reduce low-fit leads, - include activity overlays (where useful), - map to segment label (A/B/C/D).

Deliverable: sales-nav-queries-oyn-v1.md (new file)

Phase 3 — Vayne export normalization

Map Vayne CSV fields to canonical lead schema.

Suggested canonical schema

  • lead_id
  • first_name
  • last_name
  • job_title
  • linkedin_url
  • location
  • company_name
  • company_website
  • company_linkedin_url
  • company_size_band
  • industry
  • segment
  • fit_score
  • fit_reason

Deliverable: vayne-to-oyn-schema-map.md + parser script

Phase 4 — enrichment + verification policy

Apply waterfall with quality gates: 1. Icypeas primary 2. Prospeo fallback 3. verification pass before Instantly import

Quality thresholds: - invalid + risky = drop - catch-all = route to lower-volume warm lane - unverifiable = hold list

Deliverable: enrichment-policy-oyn-v1.md

Phase 5 — list scoring for sending readiness

Before list handoff to outreach stack: - assign segment priority (A/B/C) - assign confidence (high/med/low) - assign source quality notes

Only A/B + verified leads flow to Instantly by default.

Deliverable: sending-readiness-rules-oyn-v1.md


Data quality checks (mandatory)

  • duplicate rate
  • missing company domain rate
  • title parse quality
  • UK relevance rate
  • verified-email rate
  • bounce-risk estimate (pre-send)

If any metric fails threshold, list is not promoted to campaign ingestion.


Immediate next steps

  1. Finalize ICP outputs from Prompt 3 run
  2. Generate OYN query pack and exclusions
  3. Build Vayne CSV normalization script
  4. Apply enrichment waterfall + verification gate
  5. Produce first OYN-ready lead batch for outreach pipeline

Security note

Some imported research files previously contained test credentials. These have been redacted in repo copies. Keep all live credentials in secret manager only (never in markdown/docs).