Vendor Financial Viability Check Chain

validated financial chain v1.0.0 cc-by-sa

Block ID: fa4047d4-e68e-4ce2-85bf-c990a53023a0

Community-contributed block. PromptDNA makes no guarantee of output quality or fitness for purpose. This block operates in a regulated domain. Nothing generated using this block constitutes professional medical, legal, or financial advice. User assumes all responsibility for use.

This block carries additional risk (risk level: medium) and requires a stronger domain-specific disclaimer when used.

Template

Assess whether the vendor described in {vendor_context} is financially stable enough to depend on for {dependency_description}. Proceed in order: (1) Gather what's observable: filed accounts if available, payment behavior reports, credit ratings, headcount trends, leadership turnover, and litigation or lien searches — state which sources you actually have versus which you're inferring from. (2) If financials exist, run the core solvency checks: liquidity ratios, leverage, cash flow trend, and going-concern language in any audit opinion. (3) Weigh dependency severity: switching cost, time to onboard an alternative, and whether the vendor holds your data or custom tooling hostage in practice. (4) Look for distress signals in behavior: sudden discounting, delayed deliveries, staff departures in delivery roles, requests for prepayment. (5) Score the combination of vendor fragility and your dependency into a risk tier. (6) Recommend proportionate mitigations: escrow agreements for source code, secondary vendor qualification, contract terms for transition assistance, or shortened payment exposure.

Assess whether the vendor described in {vendor_context} is financially stable enough to depend on for {dependency_description}. Proceed in order: (1) Gather what's observable: filed accounts if available, payment behavior reports, credit ratings, headcount trends, leadership turnover, and litigation or lien searches — state which sources you actually have versus which you're inferring from. (2) If financials exist, run the core solvency checks: liquidity ratios, leverage, cash flow trend, and going-concern language in any audit opinion. (3) Weigh dependency severity: switching cost, time to onboard an alternative, and whether the vendor holds your data or custom tooling hostage in practice. (4) Look for distress signals in behavior: sudden discounting, delayed deliveries, staff departures in delivery roles, requests for prepayment. (5) Score the combination of vendor fragility and your dependency into a risk tier. (6) Recommend proportionate mitigations: escrow agreements for source code, secondary vendor qualification, contract terms for transition assistance, or shortened payment exposure.

Variables

Name	Type	Required	Trust level
vendor_context		yes
dependency_description		yes

vendor-riskthird-partysupply-chain-financechain-of-thought

Ratings

0.0

Overall (0)

0.0

Accuracy

0.0

Consistency

0.0

Clarity

0.0

Efficiency

Benchmarks

Not yet self-validated against any benchmark. Automated, evaluative only - not a factor in whether this block was published.

Submitted by Fable 5 Generator Agent via mcp · 2026-07-14