Business Case Construction Chain

validated business chain v1.0.0 cc-by-sa

Block ID: 0a3bed2b-271c-4de8-9ec1-65d0082a44b2

Community-contributed block. PromptDNA makes no guarantee of output quality or fitness for purpose. User assumes all responsibility for use.

Template

Build a defensible business case for the proposal in {proposal_context}, one that survives a skeptical review rather than one that just sells. (1) State the problem or opportunity and the specific, measurable outcome the investment would produce, because a business case built to justify a predetermined answer rather than to test the decision is advocacy dressed as analysis, and reviewers see through it. (2) Quantify the benefits honestly, separating hard benefits (measurable revenue or cost savings, with the mechanism shown) from soft benefits (strategic, harder to measure), and resist the temptation to inflate or double-count — the credibility of the whole case rests on the benefits being believable. (3) Cost it fully: not just the visible investment but the ongoing costs, the organizational effort, and the opportunity cost of the resources, since understated costs are the most common way business cases mislead. (4) State the assumptions explicitly and identify which ones the case is most sensitive to, then show the numbers under a conservative case, not just the optimistic one — a case that only works in the best scenario isn't a case. (5) Address the risks and what could make it fail, since acknowledging them builds credibility rather than undermining it. (6) State the recommendation, the honest expected return with its range, and the assumption a skeptic should probe first — building the case you'd want to see if you were the one being asked to fund it.

Build a defensible business case for the proposal in {proposal_context}, one that survives a skeptical review rather than one that just sells. (1) State the problem or opportunity and the specific, measurable outcome the investment would produce, because a business case built to justify a predetermined answer rather than to test the decision is advocacy dressed as analysis, and reviewers see through it. (2) Quantify the benefits honestly, separating hard benefits (measurable revenue or cost savings, with the mechanism shown) from soft benefits (strategic, harder to measure), and resist the temptation to inflate or double-count — the credibility of the whole case rests on the benefits being believable. (3) Cost it fully: not just the visible investment but the ongoing costs, the organizational effort, and the opportunity cost of the resources, since understated costs are the most common way business cases mislead. (4) State the assumptions explicitly and identify which ones the case is most sensitive to, then show the numbers under a conservative case, not just the optimistic one — a case that only works in the best scenario isn't a case. (5) Address the risks and what could make it fail, since acknowledging them builds credibility rather than undermining it. (6) State the recommendation, the honest expected return with its range, and the assumption a skeptic should probe first — building the case you'd want to see if you were the one being asked to fund it.

Variables

Name	Type	Required	Trust level
proposal_context		yes

business-caseinvestment-justificationroichain-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 James P FounderMod via mcp · 2026-07-18