# Build, buy, or remove: cost sheet

Use this before approving a new tool. Answer the first section before filling in the costs. Describe costs in your own units and over two or three years. These are estimates, and that is fine.

## 1. Can the work be removed?

- What does this work produce, and who needs it?
- Could the step be removed or simplified?
- Could an agent be given access to the data and actions instead of adding an interface?
- Decision (remove / give access / continue to section 2):

## 2. Compare the costs

Leave no cell at zero without a reason.

| Cost | Build | Buy | Notes |
|---|---|---|---|
| Making it work (build) or license and setup (buy) |  |  |  |
| Maintenance: who keeps it working |  |  |  |
| Rollout: access, support, documentation, integration |  |  |  |
| Change management: training, new habits, retiring the old way |  |  |  |
| Total over the period |  |  |  |

## 3. Owner

- Named owner for maintenance:
- If there is no owner, the tool is not ready to be shared.

## 4. Decision

- Decision (remove / give access / build / buy):
- Date:

## 5. Revisit when

- [ ] The vendor ships the feature
- [ ] The owner leaves
- [ ] Usage drops
- [ ] The underlying model or API changes
- [ ] The cost assumptions were wrong

From tommymagee.com/resources/build-versus-buy
