Zurück zur Bibliothek

Lead source conversion analysis

Compares lead sources by volume, qualification, conversion, cycle time, revenue, and data quality to show which sources create useful pipeline. Use for lead-source analysis, marketing-to-sales reporting, funnel review, channel performance, or budget planning.

von adlass TemplatesVersion 1Nutzt adlass-ToolsUniversell

Veröffentlicht 21. Aug. 2026 · Aktualisiert 26. Aug. 2026

Hilfreich · 0Rohes SKILL.md ansehen

Voraussetzungen

Map funnel and attribution fields and define cohorts. Set maturity, sample, currency and period rules.

Skill-Dokument

Das vollständige SKILL.md, das dein Agent liest und befolgt.

Lead source conversion analysis

Purpose

Measure how lead sources progress through the sales funnel and revenue outcomes, while exposing attribution and data-quality limitations. Support channel decisions with comparable denominators rather than volume alone.

Scope

Source, cohort date, lead status, qualification, opportunity, outcome, amount, cycle time, segment, owner, and attribution fields.

Excluded: changing attribution, reallocating budget automatically, and claiming source causation from incomplete records.

Data basis

  • Lead, opportunity, and outcome tables.
  • Funnel definitions and source taxonomy in scope.
  • Historical cohorts for comparison.

Result

A source-funnel sheet and analysis memo with patterns, caveats, and decision questions.

Quality criteria

  • Funnel stages and cohort windows are explicit.
  • Every rate shows numerator and denominator.
  • Duplicate and unattributed records are counted.
  • Revenue is reconciled to opportunity outcomes.
  • Recommendations distinguish evidence from hypothesis.

Instructions

Use source taxonomy and stage definitions exactly. Compare equivalent cohorts and allow for cycle length. Separate first-touch, last-touch, and multi-touch fields when present. Do not rank a source with insufficient sample or immature cohort as final performance.

Adapt before use

Keep a clear audit trail throughout the run. Use the source wording and field values that support each material conclusion, and retain uncertainty when the evidence does not decide the issue. Separate a missing record from a negative result and a contradictory record from an exception. Prefer a short, prioritised result over unsupported completeness. Check that counts, identifiers, dates, and labels agree across the written result and the structured output. When a rule, source, or mapping is unavailable, name the limitation and explain how it affects interpretation. Do not silently infer ownership, approval, timing, or business intent.

  • Map lead, opportunity, source, stage, outcome, and amount fields.
  • Define cohorts, funnel stages, attribution model, and minimum sample.
  • Set currency and reporting-period conventions.

Verwandte Skills

  • Account growth plan

    Builds a practical growth plan for an existing account from revenue, product usage, stakeholder, service, contract, and opportunity evidence. Use for key-account planning, expansion planning, whitespace analysis, relationship mapping, or strategic account reviews.

  • Account news scan

    Scans recent public developments about a target account and turns them into dated, sales-relevant talking points with citations. Use before a customer or prospect call for account news, business triggers, company updates, market signals, or timely meeting preparation.

  • Account research brief

    Builds an evidence-backed account research brief from CRM history, firmographic records, public company materials, and prior interactions, with buying signals, stakeholders, risks, and a ranked account plan. Use for strategic prospect research, account planning, territory reviews, named-account preparation, and enterprise sales research.

  • Account technology landscape

    Builds a cautious, source-backed view of the technologies and vendors an account publicly appears to use, with confidence, relevance, and research gaps. Use for account research, technology landscape review, prospect preparation, vendor context, or solution positioning.