Concept
Buy versus build
You might say: service choice, own the task
Use third-party software for proven capabilities when customization matters less; build the task policies, checks, and feedback that differentiate the factory.
- What it does
- Keeps local engineering effort on the work and controls that create differentiated value.
- Ask
- Which part is a commodity service, and which task or policy must the team understand and change itself?
What to look for
- Hosted tracker, git host and runner used with stock settings
- Repository-owned task prompts and check definitions
Sources
- Thoughtworks, Build vs. buy: A strategic framework for evaluating third-party solutions, Introduction
When you buy third-party software, you gain proven capabilities quickly, at the cost of customization and control.
- Thoughtworks, Build vs. buy: A strategic framework for evaluating third-party solutions, Defining your needs
Differentiator capabilities are how your company differentiates itself in the market.
- Anthropic, Building effective AI agents, How and when to use frameworks
We suggest that developers start by using LLM APIs directly: many patterns can be implemented in a few lines of code.
Use it on your project
teardown-apply: hold "Buy versus build" (buy-vs-build) from the teardown at https://teardownatlas.com/software-factory/ against my project
Paste it into a coding agent that has the teardown skills.
An AI agent wrote this map with the teardown skill. It can contain errors: check the sources before you rely on a part. About and legal