Build, Buy, or Partner? The Question Most Data Teams Answer Wrong

Your engineers want to build it, your CFO wants to buy it - here’s the framework that settles it in 30 minutes.

Start with one sentence: “We need [capability] to [business outcome].” If you can’t write that sentence, you’re not ready to decide.

Then rate on five criteria. Time to value. Total cost (capex plus opex over 3 years). Strategic fit. Risk - lock-in, security, data residency. Internal capability to maintain it.

Now the uncomfortable question: “Can we really maintain this?” Most teams overestimate their ability to support custom builds. I’ve watched a team of four build a beautiful data quality layer. Six months later, two engineers left. Nobody could touch the code.

Force a choice by asking: “If we pick Build, what must be true? If Buy, what guarantees do we need? If Partner, who owns outcomes?”

The answer changes as your team matures. What you should buy at 20 people, you might build at 100. Review this every 6 months.

What data capability are you currently debating build vs buy on?