Should we buy software or build it ourselves?
Unstructured option appraisalCompare feasible options against the same outcome, lifecycle costs, constraints, and operating responsibilities. Include configuration and process change rather than forcing a simplistic build-versus-buy choice.
What to do now
- Define non-negotiable requirements
- Estimate lifecycle effort for each option
- Test critical assumptions with a small proof
- Record the decision and review triggers
When to escalate
Escalate when
A preferred option fails a mandatory requirement or lacks sustainable support.
Who decides
The accountable sponsor
Example
A small team chooses configurable software after including upgrades, security reviews, and support in the comparison.
Mistake to avoid
Comparing purchase price with development cost while ignoring operations.
Prevent a repeat
At each stage decision, check that the expected outcome, owner and justification remain valid.
Suggested ApprovedFlow setup
- Projects
- Documents
- Approvals
Keep the decision brief with the project and request a recorded sponsor decision before the next commitment. See the platform
Related cases
- We cannot tell whether this is a project or routine operational work. How should we organize it?Unclear work classification
- The sponsor says everything is equally important. How can we prioritize?Unresolved strategic trade-offs
- How do we build backup coverage without doubling staffing?Proportionate resilience planning
- We discover integration problems only before release. How can we improve?Late integration feedback