Direct answer
Use an off-the-shelf product when the job is common, speed matters, and the business can adopt the product's workflow. Consider a configured or custom system when the process is differentiating, crosses several systems, requires specific controls or experience, or needs portability. Compare total ownership cost and fit, not only purchase price.
Build, buy, or combine
Match the implementation approach to the work
Likely fit
Configured product plus custom workflow
Use proven software where the capability is common, then design the integrations, controls, and operating workflow around it.
Three real options
Compare product, configured system, and custom capability
| Model | Best when | Cost shape | Tradeoff |
|---|---|---|---|
| Off-the-shelf product | The capability and workflow are common | Lower setup, recurring license | The company adapts to vendor features and limits |
| Configured product system | A proven product fits the core job but needs company knowledge, rules, and connections | Moderate implementation plus licenses | Customization depends on vendor extension points |
| Custom system | The workflow is differentiating, integrated, or control-sensitive | Higher discovery and build plus ongoing ownership | The business accepts greater design and maintenance responsibility |
Fit criteria
Pay for custom work only where it changes the outcome
- The process creates meaningful competitive differentiation
- Several existing systems must work as one workflow
- A specialized user experience materially affects adoption or quality
- Company knowledge, permissions, or decision rules are central
- The required control cannot be achieved in the product
- Ownership, portability, or vendor independence has strategic value
- Normal product configuration would force harmful process compromises
Total ownership cost
Model cost over the period the decision must last
| Cost | Product | Custom or hybrid |
|---|---|---|
| Initial | License, setup, migration, configuration | Discovery, design, implementation, integration |
| Recurring | Per-user or usage fees, premium controls | Hosting, models, monitoring, maintenance, support |
| Change | Vendor roadmap and configuration limits | Internal or partner development capacity |
| Exit | Export, migration, contract timing | Code, documentation, infrastructure, replacement expertise |
| Risk | Vendor concentration and terms | Build quality and ongoing ownership |
Hybrid architecture
Buy commodities and design the differentiating workflow
A strong hybrid may use a commercial model, automation platform, database, identity provider, and CRM while custom work defines how approved knowledge is retrieved, how decisions are controlled, what users see, and where outcomes are recorded.
This avoids rebuilding mature infrastructure while preserving the company-specific part of the system.
Before deciding
Test product fit with real cases and real contract terms
- Run representative examples, including exceptions
- Confirm the exact service tier, data terms, limits, and controls
- Check APIs, export, identity, audit logs, and deletion
- Estimate internal configuration and adoption time
- Model price at normal and high volume
- Identify what breaks if the vendor changes model, limits, price, or roadmap
- Document an exit path proportional to the system's importance
The value point
After this page, you should be able to decide:
Which delivery model creates the best fit and lowest defensible total cost over the expected life of the system.Your working output should be a build-buy recommendation, total-cost comparison, portability questions, and hybrid architecture.
Questions business leaders ask
Frequently asked questions
Is custom AI always more expensive?+
It usually costs more to discover and implement, but a poor-fit product can become expensive through workarounds, unused licenses, manual exceptions, and switching cost.
When should a business buy instead of build?+
Buy when the capability is common, product fit is strong, time matters, controls are adequate, integrations are supported, and the vendor's economics remain acceptable at expected use.
What does a hybrid AI system mean?+
It combines commercial models or software with company-specific knowledge, integrations, controls, interfaces, and workflows.
How should vendor lock-in affect the decision?+
Weight it according to the system's strategic importance, data sensitivity, switching difficulty, and expected life. Require workable export, documentation, and termination terms.
Research anchors
Primary and authoritative sources
- NIST AI Risk Management Framework↗
- CISA: Secure by Design↗
- FTC: Privacy and confidentiality commitments for AI companies↗
Examples and planning ranges are clearly labeled. Source terms, provider behavior, and regulations can change; verify current requirements for your organization and jurisdiction.
Prepared and reviewed by the Future Made Useful systems editorial team. Material guidance reviewed July 17, 2026.