Make vs Buy vs Partner Chain

validated business chain v1.0.0 cc-by-sa

Block ID: 1c2c1437-67d0-4151-8fb7-200e57ceced5

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

Template

Decide whether to build, buy, or partner for the capability in {capability_need}, reasoning from strategic importance and current position. (1) Classify the capability: is it core — a source of competitive differentiation customers pay for — or context, necessary but not differentiating? This classification drives the default: build what differentiates you, source what doesn't, and the most expensive error is building commodity capabilities or outsourcing your actual edge. (2) Assess your current position honestly: do you have the capability, the ability to build it well, and the time before you need it? (3) Model each path's full cost and timeline: build (development plus the ongoing maintenance and opportunity cost that estimates omit), buy (acquisition plus integration plus culture risk), partner (speed and lower commitment against dependency and margin sharing). (4) Weigh control and reversibility: building maximizes control at the cost of speed; partnering is fast but creates dependency that's hard to unwind; buying is a large irreversible bet. (5) Consider the strategic risk of each — especially handing a differentiating capability to a partner who could become a competitor or hold you hostage. (6) State the recommendation, the decisive factor, and the condition under which the answer would change. Present the case for the path you didn't choose.

Decide whether to build, buy, or partner for the capability in {capability_need}, reasoning from strategic importance and current position. (1) Classify the capability: is it core — a source of competitive differentiation customers pay for — or context, necessary but not differentiating? This classification drives the default: build what differentiates you, source what doesn't, and the most expensive error is building commodity capabilities or outsourcing your actual edge. (2) Assess your current position honestly: do you have the capability, the ability to build it well, and the time before you need it? (3) Model each path's full cost and timeline: build (development plus the ongoing maintenance and opportunity cost that estimates omit), buy (acquisition plus integration plus culture risk), partner (speed and lower commitment against dependency and margin sharing). (4) Weigh control and reversibility: building maximizes control at the cost of speed; partnering is fast but creates dependency that's hard to unwind; buying is a large irreversible bet. (5) Consider the strategic risk of each — especially handing a differentiating capability to a partner who could become a competitor or hold you hostage. (6) State the recommendation, the decisive factor, and the condition under which the answer would change. Present the case for the path you didn't choose.

Variables

Name	Type	Required	Trust level
capability_need		yes

make-buy-partnersourcing-strategycapabilitieschain-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