Build vs. buy: a practical framework.

Start with the real question

"Build vs. buy" is usually asked too early. The more useful question first is: how core is this capability to what makes your business different? A tool that handles something every business needs — accounting, email, scheduling — is rarely worth building from scratch. A workflow that reflects exactly how your business wins is a different story.

When buying usually wins

• The need is common. If dozens of mature products already solve this problem well, you're unlikely to build something better for less.
• Speed matters more than fit. You need something working this month, not this year.
• The workflow is standard. Your process doesn't meaningfully differ from how most businesses in your space operate.
• You don't want ongoing ownership. Buying shifts maintenance, security patching, and uptime onto the vendor.

When building usually wins

• It's core to your advantage. The workflow, data, or customer experience is part of what actually differentiates you.
• Off-the-shelf tools force compromise. You're bending your process to fit the software, not the other way around, and that's costing you.
• You're paying twice. You already own several tools and are manually connecting them — a sign the real need is integration, not another subscription.
• Data ownership and control matter. You need full visibility into how a process works and where your data lives.

How AI changes the calculation

AI has quietly moved a meaningful slice of the "build" column into the realm of realistic. Custom AI agents, document processing, and workflow automation used to require a large engineering team to build well. That's no longer strictly true — a focused, well-scoped AI system can now be built faster and more affordably than a broad off-the-shelf platform that only fits 70% of what you actually need.

That doesn't mean "build everything with AI." It means the honest comparison has shifted: a narrowly-built AI solution designed around your exact workflow is now a realistic competitor to a generic SaaS subscription — not just a large-company luxury.

A short way to decide

If you can answer "yes" to most of these, building is worth seriously evaluating: this workflow is close to what makes us different; existing tools force real compromises; we're stitching together multiple tools already; and we're prepared to own what we build (or have a partner who will). If most answers are "no," buying is very likely the faster, cheaper, lower-risk path — at least for now.