Volver a la biblioteca

Win-loss analysis

Analyses closed-won and closed-lost opportunities to reveal repeatable patterns by segment, source, size, competitor, stage, reason, and sales motion. Use for win-loss reviews, sales performance analysis, loss-reason coding, revenue insights, or quarterly sales planning.

por adlass TemplatesVersión 1Usa herramientas de adlassUniversal

Publicado 21 de ago de 2026 · Actualizado 26 de ago de 2026

Útil · 0Ver SKILL.md sin formato

Requisitos

Define taxonomy, dimensions, sample rules and periods. Map opportunity fields and recommendation owners.

Documento de la habilidad

El SKILL.md completo que tu agente lee y sigue.

Win-loss analysis

Purpose

Convert closed-opportunity records into reliable patterns that improve sales, marketing, product, and pricing decisions. Preserve the difference between recorded reasons and evidence-supported explanations.

Scope

Outcome, segment, source, size, cycle length, stage exit, competitor, reason, notes, product, price, process, and seller attributes.

Excluded: blaming individuals, changing historical records, and generalising from unsupported anecdotes.

Data basis

  • Closed opportunity table and reason taxonomy.
  • Call notes, surveys, and competitor fields in scope.
  • Historical periods for comparison.

Result

A coded opportunity sheet, pattern report, and action recommendations.

Quality criteria

  • Population and exclusions are stated.
  • Every coded reason traces to source evidence or is labelled recorded-only.
  • Win and loss cohorts use comparable definitions.
  • Small samples are flagged.
  • Recommendations name the pattern and affected segment.

Instructions

Use the configured reason taxonomy before adding new categories. Separate primary and contributing reasons when evidence supports both. Report counts and rates with denominators. Do not infer causation from correlation. Call out missing outcome interviews, inconsistent coding, and periods that cannot be compared.

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 opportunity and outcome fields.
  • Define reason taxonomy, segment dimensions, and minimum sample rule.
  • Set comparison periods and recommendation owners.

Habilidades relacionadas

  • 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.