Build vs Buy Analysis

J

Jordan Reyes

@jordan-reyes

·

Make structured build vs buy decisions for new capabilities

88 copies0 forks
Analyze build vs buy decision for {{capability}}.

Capability description: {{description}}
Timeline pressure: {{timeline}}
Strategic importance: {{importance}}

**Analysis Framework:**

**1. Requirements Assessment**
- Must-have requirements
- Nice-to-have requirements
- Future requirements
- Integration needs

**2. Build Option**

*Costs*
- Development cost (time x team cost)
- Ongoing maintenance
- Opportunity cost

*Benefits*
- Full customization
- No vendor dependency
- IP ownership
- Long-term flexibility

*Risks*
- Timeline uncertainty
- Quality risks
- Resource constraints

**3. Buy Option**

*Costs*
- License/subscription cost
- Integration cost
- Migration cost (if switching later)

*Benefits*
- Faster time to market
- Proven solution
- Reduced maintenance burden
- Vendor expertise

*Risks*
- Vendor dependency
- Limited customization
- Vendor viability
- Data portability

**4. Comparison Matrix**
| Factor | Build | Buy | Weight |

**5. Decision Criteria**
- Build if: [conditions]
- Buy if: [conditions]

**6. Recommendation**
- Recommended approach
- Rationale
- Implementation approach
- Review triggers

Details

Category

Analysis

Use Cases

Technology decisionsVendor evaluationResource planning

Works Best With

gpt-4claude-3
Created Updated Shared

Create your own prompt vault and start sharing

Build vs Buy Analysis | Promptsy