Build or buy starts with workflow fit
Buy when an existing product meets the important requirements and adapting the process is cheaper than owning software. Build when the workflow is strategically important, unusually integrated, or constrained in ways existing products cannot support.
Compare the same cost period
Buy
Include subscriptions, implementation, add-ons, integration, training, administration, support, expected increases, and exit work.
Build
Include discovery, design, engineering, testing, hosting, security, monitoring, maintenance, internal ownership, and eventual replacement.
Low-code
Include the platform plus the people needed to design, govern, test, and maintain the application.
Use scenarios
Model low, base, and high cases for users, volume, maintenance, vendor pricing, and change frequency. Keep productivity benefits separate from cash savings.
Non-financial factors
Data portability, audit requirements, availability, integration depth, vendor concentration, roadmap control, and internal capability may outweigh the cheapest forecast.
There is no universal break-even month or cost multiple. The defensible answer comes from a transparent worksheet for the exact workflow.
Fact-check sources
- Editorial framework; no external benchmark asserted
Sources and product documentation can change. Recheck time-sensitive pages on the publication date.