/05

Build or Buy

A workflow-level build, buy, or hybrid framework without vendor hype.

Intermediate

7 min

Open +

Buy the commodity. Own the part of the workflow that creates advantage. Mix the two when your context, rules, permissions, or interface are the valuable layer.

Leave knowing / Know which layer is worth owning

The decision rule

Use existing software when the problem is common and the workflow is standard. Build a thin layer when the intelligence is common but your context or integrations are unique. Build custom only when the workflow itself creates meaningful advantage and somebody can own it after launch.

Start with the workflow, not the technology.

Before custom

Custom should earn the right to exist.

01

The workflow matters enough to differentiate the business.

02

Existing products leave a material gap, not a cosmetic preference.

03

The system needs proprietary context, logic, permissions, or integrations.

04

A named team can maintain, secure, test, and improve it after launch.

05

The value is larger than the long-term operating cost.

Try it

Use existing software.

Best when the problem is common, the workflow is not a competitive advantage, and several mature products already solve it well.

Ask: can we get most of the value by configuring something proven?

Build a thin layer.

Best when the intelligence is common but your context, rules, permissions, interface, or integrations make the workflow yours.

Ask: what is truly unique here, and can we own only that layer?

Build custom.

Best when the workflow itself creates meaningful advantage and your team can own testing, maintenance, security, and improvement after launch.

Ask: are we willing to own this system after the exciting first version?

Start with the workflow, not the technology. A useful answer can be different for two teams facing the same category of problem.

Notes / Subscribe

Get the next note.

No schedule. No content calendar. A note goes out only when there is something worth understanding.