SkillVaultskills Browse all 500 skills

Sales · Version 1.3.0 · Reviewed 2026-08-02

Deal Risk Analyst

Improve single-threading risk and approval mapping with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Identifies structural risks in a deal including single threading, unstated approvals, and timeline fiction.

₹99 one-time

Get this skill archive

What this skill helps you do

  • Single-threading risk
  • Approval mapping
  • Close-date validation

How Deal Risk Analyst works

You provide

Call notes, deal context, and the decision being pursued

It inspects

Confirmed decision process behind single-threading risk

It decides

A approval mapping assessment separating said from inferred

You verify

Each qualification claim tied to a quoted excerpt

What it checks first

Deal Risk Analyst identifies structural risks in a deal including single threading, unstated approvals, and timeline fiction. Use it when the work involves Single-threading risk, Approval mapping, Close-date validation.

  1. Whether the buyer articulated the problem or the seller supplied the framing.
  2. Whether an economic buyer and a decision process have been confirmed rather than assumed.
  3. What the objection protects against, since the stated objection is rarely the real risk.
  4. Whether next steps are owned by the buyer, which is the strongest indicator of real intent.

Failure modes it recognizes

  • Champion enthusiasm mistaken for buying authority, so the deal stalls at approval.
  • A price objection that is actually an unquantified value or risk objection.
  • Discovery notes recording features requested rather than outcomes required.
  • A single-threaded deal that dies when the one contact changes role.

Answers it will reject

  • Answering the stated objection immediately rather than establishing what it protects.
  • Treating activity metrics as pipeline health, which improves without revenue improving.
  • Forecasting from optimism rather than from confirmed decision criteria and timing.

Decision rules it applies

  • Qualify on decision process and economic impact, not on interest.
  • Separate what the buyer said from what was inferred in every summary.
  • A next step without a buyer-owned commitment is not a next step.

Evidence it asks for

  • Quote the call excerpt behind each qualification claim.
  • Track buyer-owned actions completed, not seller activity logged.
  • Test the deal by naming who signs and what they must approve.

The method inside

  1. Extract buyer evidence without filling gaps from seller assumptions
  2. Map the exact decision process, risk, and missing commitment
  3. Separate stated objection from underlying purchase risk
  4. Produce a buyer-verifiable next step with owner and date

Deliverables

  • Single-threading risk scorecard
  • Approval mapping gap register
  • Close-date validation plan

Evidence requirements

  • Call transcripts, CRM notes, and buyer correspondence
  • Opportunity stage, stakeholders, dates, and known commitments
  • Approved product, pricing, security, and commercial evidence

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

This deal is forecast to close this month at 90 percent confidence. Stress test it before the forecast call.

Expected output

Ninety percent with one contact and no procurement conversation is a confidence number, not a probability. Two risks dominate: nobody has confirmed who signs, and the close date matches your quarter rather than any buyer-side event...

Boundaries and compatibility

Ideal for

  • Single-threading risk: produce a decision or artifact grounded in supplied evidence.
  • Approval mapping: produce a decision or artifact grounded in supplied evidence.
  • Close-date validation: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Inventing buyer intent or authority
  • Making unsupported product, legal, or pricing commitments

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.