2.2.2 - Buy vs Build Is a Strategy Choice, Not an Engineering One

Buy versus build decision

Is this buy-vs-build choice improving the first user outcome?

The call

Make the buy-vs-build decision based on where value lives. Otherwise AI helps you build things that should have been bought and buy things that needed to be yours.

Why it matters

Buy vs build is a strategy choice because the right decision depends on which option improves the first useful user outcome. AI can compare options quickly, but human judgement decides which trade-off protects speed, reliability and focus. The difference is between shipping a technical preference and shipping a strategy that users actually feel.

Explainer

Buy versus build is not a tooling preference. It is a strategy call about where your effort creates advantage and where it does not. Until you can name one decision area, one reason to buy or build and one constraint that decides it, the discussion will loop. AI can help compare options, but it cannot choose your leverage point.

Make the buy versus build decision concrete

Compare the broad version with a version you can actually test.

• Too vague: We should decide whether to use an existing service or build it ourselves.
• Concrete enough to test: Buy authentication because it is not where value lives. Build the context-shaped search because that is where the product makes a unique decision for the user.

The second version lets two people choose the same leverage point from it.

Check the buy versus build decision

• Pass: You can say what the decision is about, why one side wins and which constraint makes the call.
• Fail: If the discussion still lives at the level of flexibility or control in general, it is not specific enough yet.

Do not move into vendor selection or implementation work until this passes.

What you'll walk away with

This post is about the framing decision: the words that pin down what this idea actually means for your build, before any code. You'll come out with your own knowledge-base/build/buy-vs-build.md written and sharpened: the buy versus build decision pinned down as a decision, three worked examples to map against your own surface and an AI prompt that pressure-tests it until two people would make the same call.

The code that brings these decisions to life lives in the build-in-public repos (subCancel, ghostMarketingFlow and flowRun), which are works in progress growing alongside the writing. We work through the code together each week in the free weekly workshops; that is where these ideas get put into practice with hands on the keyboard.

If you sign up, this idea continues with how it all fits together, a worked example, how to use it with AI, how to evaluate it on a real change, the risks worth naming and how to mitigate them, the key takeaways and a copy-paste AI prompt you can drop straight into your next chat. Examples are shown on the Cloudflare Workers stack with AI-assisted coding tools; the ideas apply equally on any other platform.