Build, buy or wait: an AI decision framework for technology leaders
Build an AI capability only when it is core to your product and you can evaluate it. Buy when it is commodity and a vendor can show evaluation results on your data. Wait when neither is true: model capability and prices change fast, and a six-month delay is often the cheapest option.
Last verified24 Sep 2026
Placeholder article. Replace this text with your own. Keep the structure: a BLUF in the frontmatter, then sections that each open with a direct answer.
When should you build?
Build when the capability differentiates your product and your team can measure its quality with an evaluation set built from your own data.
When should you buy?
Buy when the capability is the same for everyone, such as transcription or translation, and the vendor can show results on a sample of your inputs, not only on public benchmarks.
When should you wait?
Wait when the capability is neither core nor measurable yet. Model quality improves and prices fall quickly, so a planned delay with a review date is a legitimate decision, not a failure to act.
| Question | Build | Buy | Wait |
|---|---|---|---|
| Is it core to the product? | Yes | No | Unclear |
| Can we evaluate it on our data? | Yes | Vendor can | Not yet |
| Cost of being late? | High | Medium | Low |
Key takeaway
Write the decision down as a technical decision record, including the option you rejected and the date you will revisit it.