Lead sourcing to a verified CRM campaign

The operational effort is not in the individual click. It lies in the sum of many small review decisions: Is the hit relevant? Does the brand belong to this company? Is there already a CRM record? Is the record duplicated? Are website, contact situation and company relationship reliable? May a lead be created from it? And is this lead complete enough to move directly into a campaign?

This work is difficult for enterprises to organize cleanly on a sustained basis. It sits between sales, marketing operations, research, CRM maintenance and data quality. Nobody truly owns the full run end to end. The result is media breaks, inconsistent standards, duplicates, incorrect assignments and campaign inventories that sales does not fully trust.

The outcome: lead sourcing is done, but it is not really guided. Enterprises gain data, but lose quality. They create leads that must be cleaned up later. They start campaigns on unreliable foundations. And they bind qualified employees to manual review and correction work instead of conversations, closing opportunities or strategic market work.

From that point, Jadey guides the process throughout. Relevant companies are identified, checked, evaluated and prepared for the campaign. Every potential lead receives a business rating and is prequalified; only highly rated leads enter the campaign inventory. Existing CRM data is considered, duplicate entries are avoided and unclear cases are visibly routed out. Research, qualification, data review and campaign build are therefore no longer distributed between sales, marketing, research and CRM maintenance, but guided in one coherent process.

A major difference lies in quality assurance during the run. Incomplete, contradictory, non-uniquely assignable or insufficiently rated records are not silently taken into the campaign. They are corrected, checked again or deliberately blocked until company relationship, data quality, contact situation, rating and CRM readiness are reliably clarified. This avoids a downstream cleanup problem and creates controlled construction of usable campaign data.

The result is a verified CRM campaign inventory. Leads, brands, companies, assignments and required data are prepared so that sales can continue on a clean foundation. The run counts as complete only when the campaign is complete, unambiguous and usable in CRM.

A lead counts as CRM-ready only when campaign, lead and brand records, campaign binding, brand-lead relation and required fields have been written in CRM and confirmed by readback. CRM First-Time-Right therefore does not describe later sales impact, but successful CRM completion against target state, field findings, relation evidence and parent CRM audit.

A full campaign contains 50 potential leads. From a new need, the configured standard run creates a CRM campaign in roughly 260 minutes instead of an intermediate list maintained manually.

The reported metrics refer to this configured standard run. Counted are additional CRM-ready leads that emerge without newly built manual research and cleanup effort. Special cases, incomplete data situations and required approvals are checked and controlled separately instead of diluting the quality of the entire campaign.

The new capability therefore does not lie in faster search. It lies in Jadey guiding the full operational context: from recognized lead need through selection, review, correction and CRM readiness to the verified campaign inventory. Lead sourcing becomes a repeatable, controllable and evidenced enterprise run instead of a manual research task.

The deployment deliberately ends at CRM campaign completion. A run is complete only when campaign, leads, brands, relations, CRM readback and parent CRM audit are documented. A later outreach or sales-meeting run is not part of this deployment.

Agents and roles in the deployment

Four agent areas participate in the lead-sourcing run. cron starts the daily run technically and hands the run to opportunity. opportunity takes over business case guidance: triage clarifies the need and creates the campaign case, ops-parent keeps the run together and commissions ops-child for individual review and playbook steps.

For business prequalification, rating is also involved. rating evaluates potential leads, returns a score and ensures that only highly rated leads continue toward the campaign inventory. crm takes over CRM subtasks when existing CRM data must be checked, campaign, leads and brands must be written or CRM inventory must be read back.

External register and research sources complement the run as data sources. Research source, DPMA, EUIPO, website and Northdata return review signals to the opportunity case, but are not independent target-state agents. The run therefore remains clearly guided: cron orchestrates the start, opportunity/ops-parent carries outcome responsibility per campaign case, rating adds business evaluation and crm/sales delivers CRM precheck, write, readback and audit input.

Service hierarchy

flowchart TB
  cron_runner[cron/runner]
  triage[opportunity/triage]
  parent[opportunity/ops-parent]
  child[opportunity/ops-child]
  rating[rating]
  crm_sales[crm/sales]
  github[(GitHub)]
  crm[(Dynamics Dataverse CRM)]
  research[(Research source)]
  dpma[(DPMA)]
  euipo[(EUIPO)]
  website[(Website)]
  northdata[(Northdata)]

  cron_runner --> triage
  triage --> parent
  triage --> github
  parent --> child
  child --> rating
  child --> crm_sales
  crm_sales --> crm
  parent --> github
  child --> research
  child --> dpma
  child --> euipo
  child --> website
  child --> northdata

Systems in the deployment

Only the systems and data sources required for intake, review, CRM write and final evidence are used in the deployment. GitHub documents intake, run reference and closing note. Research source, DPMA, EUIPO, website and Northdata provide review signals for brand, company, contact situation and campaign readiness. CRM is the leading completion location for campaigns, brands, leads and relations.

Artefacts in the deployment

The artefacts form the evidence chain from search signal to verified CRM campaign. The website shows the most relevant artefacts. In the actual run, every agent role additionally creates its own handover to the next role, so that state changes, findings and blockers remain traceable.

For enterprise environments, this artefact chain is central. It makes visible which need was reviewed, which criteria applied, which leads continued or were blocked, whether the CRM result is reliable and which exceptions remain open.

Run Summary

Owner: opportunity/ops-parent

Produced by: cron/runner + opportunity/ops-parent

Meaning: Operating evidence for start, monitoring and terminal run status.

Relevance: Proves that the run was started, monitored and completed or blocked in a controlled way. Important for operational governance.

Intake & Scope Summary

Owner: opportunity/triage

Produced by: opportunity/triage

Meaning: Business starting point of the campaign run with need, scope and rules.

Relevance: Evidences why sourcing need existed and which criteria applied: target segment, category, seeds and exclusions. Important against implicit defaults.

Qualification Decision Summary

Owner: opportunity/ops-parent

Produced by: opportunity/ops-parent, supplied by opportunity/ops-child

Meaning: Business decision evidence for continuation, exclusion, repair or blocker.

Relevance: Shows which checks were passed and why leads or brands continue or drop out. Important for business traceability.

CRM Result & Readback Summary

Owner: crm/sales

Produced by: crm/sales, evaluated by opportunity/ops-parent

Meaning: Evidence of the created or updated CRM inventory and its readback.

Relevance: Proves the business outcome: campaign, leads, brands, bindings, relations and readback. Important because CRM write alone is not enough.

Governance Exception Summary

Owner: opportunity/ops-parent

Produced by: opportunity/ops-parent, supplied by crm/sales and opportunity/ops-child

Meaning: Exception and risk evidence for incomplete or unreliable subcases.

Relevance: Shows open Tier-S, Tier-A, Tier-B or Tier-C gaps, ambiguities, blocked cases and missing contracts. Important for audit, risk and escalation.

From search signal to verified CRM campaign

The lead-sourcing run connects daily start, intake, issue queue, parent case guidance, child playbooks, CRM precheck, dedupe, research and register review, business rating, CRM campaign, readback and parent audit into one guided operating process. The standard path ends in a verified CRM campaign. Side paths apply when no need exists, mandatory values are missing, child returns are incomplete, a lead is rated too weak, CRM duplicates are ambiguous or readback shows gaps.

flowchart TB
  subgraph cron_lane["cron/runner<br/>Daily run"]
    c1[Start daily sourcing run]
    c2[Start opportunity/triage<br/>waiting]
    c3[Wait for triage return]
    c4[Write run logs and<br/>runner report]
    c1 --> c2 --> c3 --> c4
  end

  subgraph triage_lane["opportunity/triage<br/>Intake"]
    t1[Check sourcing need]
    t2{Need<br/>present?}
    t_no[Return no need]
    t_yes[Materialize<br/>business defaults]
    t_issue[GitHub issue<br/>with mandatory fields]
    t1 --> t2
    t2 -->|no| t_no
    t2 -->|yes| t_yes --> t_issue
  end

  subgraph parent_lane["opportunity/ops-parent<br/>Campaign run"]
    p1[Start parent run<br/>from issue]
    p2[Provide<br/>canonical_run_state]
    p3[Commission ops-child<br/>playbooks]
    p4[Collect and evaluate<br/>returns]
    p5{Parent gate}
    p6[Parent CRM audit]
    p7[Handoff<br/>campaign_id + name]
    p_block[Document<br/>hard block]
    p1 --> p2 --> p3 --> p4 --> p5
    p5 -->|advance| p6 --> p7
    p5 -. retry/repair .-> p3
    p5 -->|hard block| p_block
  end

  subgraph child_lane["opportunity/ops-child<br/>Playbook steps"]
    ch1[CRM precheck<br/>and dedupe]
    ch2[Check sourcing, register<br/>and website]
    ch3[Check portfolio and<br/>company data]
    ch4[Prepare<br/>opportunity analysis]
    ch5[Prepare CRM campaign<br/>and upsert]
    ch1 --> ch2 --> ch3 --> ch4 --> ch5
  end

  subgraph rating_lane["rating<br/>Company evaluation"]
    r1[Business lead evaluation]
    r2[Scoring and<br/>rating finding]
    r1 --> r2
  end

  subgraph crm_lane["crm/sales<br/>CRM service"]
    crm1[Check Dynamics CRM<br/>inventory]
    crm2[Write campaign, lead<br/>and brand]
    crm3[Readback and<br/>audit input]
    crm1 --> crm2 --> crm3
  end

  triage_parent_gap[ ]

  c2 --> t1
  t_no --> c3
  t_issue --> c3
  t_issue --> p1
  p3 --> ch1
  ch1 -. CRM check .-> crm1
  crm1 --> ch2
  ch4 --> r1
  r2 --> ch5
  ch5 --> crm2
  crm2 --> crm3
  crm3 --> p4
  p7 --> c3
  %% Layout help: keeps distance between intake and parent lane.
  t_issue ~~~ triage_parent_gap
  triage_parent_gap ~~~ p1
  style triage_parent_gap fill:transparent,stroke:transparent,color:transparent
  %% Layout help: keeps rating and CRM service readable as separate lanes.
  ch4 ~~~ r1
  ch5 ~~~ crm2

What was implemented here for lead sourcing can be transferred to comparable campaign, research and CRM processes in your enterprise - with your existing system landscape, your approval paths and the rules that govern your operations.

In a first conversation, we assess whether this deployment is suitable as a starting point for your enterprise and where Jadey can create near-term operational impact.