The classic build-vs-buy decision is incomplete. Configure-on-platform is now the third option. Decision framework included.
May 9, 2026·2 min read·By admin
At a glance
Topics
Advisory & Strategy · Custom App Development
Published
May 2026
The build-vs-buy decision is taught as binary. It hasn’t been binary for a decade. Configure-on-platform is now the third option for most enterprise needs.
The three options
Build: Custom code on infrastructure you own. Maximum flexibility; maximum cost.
Configure: Build on a platform (ServiceNow, Salesforce, Power Platform). Mid-flexibility; mid-cost.
The decision framework
Configure when: the workflow shape matches the platform’s opinions; you already pay for the platform; your needs may evolve in the same direction the platform evolves.
Build when: your differentiation is the workflow itself; configure-cost exceeds build-cost over a 3-year view; you have engineering depth.
Buy when: the workflow is undifferentiated commodity; vendors deliver it well; integration cost is manageable.
Most enterprises over-build
The default decision in most enterprises is “build” because that’s the model engineers know. Configure-on-platform delivers 80% of the value at 30% of the cost in most cases. Yet it’s often the last option considered.