Engineering Library · Decisions
Use the guide closest to the constraint you are evaluating. Each compares fit, ownership, lifecycle cost, timing, integration, governance, and exit conditions. The correct choice depends on evidence; hybrid and staged paths are valid outcomes.
Should an organization build custom software or buy an existing product?
Buy when a supported product meets the essential workflow through configuration and its data, integration, and vendor terms are acceptable. Build may be justified when the workflow is strategically differentiating, material constraints cannot be configured safely, and the organization can own a software lifecycle. A hybrid approach is often preferable.
Open decision frameworkWhen should a team use low-code instead of custom development?
Low-code is appropriate when the workflow fits platform capabilities, rapid iteration matters, governance is defined, and licensing and portability are acceptable. Custom development is stronger when architecture, testing, performance, integration boundaries, or a long product lifespan require direct control. Neither is inherently more professional or secure.
Open decision frameworkShould an organization build a custom CRM or configure an off-the-shelf CRM?
Most organizations should configure or integrate an established CRM when sales workflows are standard and the product ecosystem fits. A custom CRM is justified only when distinctive relationship, workflow, data, or control requirements create material value that supported configuration and extensions cannot provide.
Open decision frameworkShould an organization integrate with an existing ERP or replace it?
Integration is usually safer when the ERP is stable, supported, authoritative, and exposes dependable interfaces. Replacement becomes safer when unsupported technology, structural process mismatch, data risk, or escalating integration debt makes continued operation unsustainable. Discovery is required before either recommendation.
Open decision frameworkDoes a business need a custom website or is a website builder sufficient?
A website builder is often sufficient for a straightforward site with standard layouts, modest integrations, urgent launch needs, and an internal editor. Custom development is justified when brand expression, content governance, accessibility, performance, structured data, internationalization, or integration requirements exceed supported builder capabilities.
Open decision frameworkWhen should a manual business process be automated through an API integration?
Automate when a stable, repeated process has sufficient volume, delay, error consequence, or audit need and both systems provide dependable interfaces. Keep a controlled manual process when volume is low, rules change frequently, human judgment is central, or automation and maintenance would cost more than the constraint warrants.
Open decision frameworkStart with the decision question, replace assumptions with actual workflow and operating data, and compare the options across the same planning horizon. These six guides are not a comprehensive catalogue. If neither option fits, stabilize the process or run focused discovery before committing to a platform or build.