Should we build custom software or buy an existing platform?
Buy when the function is common, regulated, or a system of record. Build when the workflow is how you win, or when bought tools force you to bend your process around them. Most companies have four options, not two: buy, configure a platform, build in-house, or build with a partner. The question that sorts them is who owns the software in year two.
When this matters
The decision is already being made inside most companies. In McKinsey's 2026 State of AI survey, 32% of respondents said their organization decided against buying at least one software product or feature because it could build the functionality in-house with agentic coding tools (n=1,719, fielded 2026-05-04 to 2026-06-08). See McKinsey, The state of AI in 2026.
Options and trade-offs
|
Path |
Fits when |
Watch for |
Year-two owner |
|---|---|---|---|
|
Buy |
The function is common (payroll, email), regulated, or a system of record |
You bend your process to the tool; renewal price increases |
The vendor |
|
Configure a platform |
Your process fits a platform with configuration, such as Quickbase |
Apps left half-built; one person who knows how it works |
You, or a support partner |
|
Build in-house |
You have developers and the workflow is how you win |
Maintenance load, security review, key-person risk |
Your team |
|
Build with a partner |
You want custom software without staffing the upkeep |
Choose a partner who documents and stays |
Shared, by agreement |
Five questions that decide it
- Is this function common, or is it how we win? Common functions usually belong with a vendor.
- Would a bought tool make us bend our process? If yes, a platform or a custom build may fit better.
- Who maintains it in year two? Name a person or a firm. If you cannot, plan for it before you start.
- What happens to our data if we leave? Ask for a test export before you sign.
- Can we afford the upkeep? Count review, security, and change requests, not just the first build.
Why year two matters
- Building is cheap now. Owning is the bill. In a study of AI-generated files across 100 popular open-source repositories, human developers did the large majority of the maintenance on AI-generated code. The same study found AI-generated files need less frequent maintenance than human-written ones. These are open-source repositories, not business applications. See arXiv 2605.06464.
- Security does not fix itself. AI-generated code passes security tests 56% of the time, virtually unchanged since last year. See the Veracode 2026 GenAI Code Security Report.
Real example
Geisinger replaced two $100K compliance systems with one custom app, saving $200K+ annually. Two bought systems became one built app. See the Geisinger case study.
Cost and timing
Cost and timeline depend on scope, so we do not quote either without a review. We also say when buying is the right call. A common function that a vendor already serves well should stay with the vendor.
How VeilSun can help
- Technology Blueprint and App Checkup. A structured first step before you commit. See the App Checkup.
- Build on Quickbase or full-stack. See Quickbase at VeilSun and full-stack development.
- Support after launch. Our Ongoing Development Plan keeps an app current as your business changes.
Weighing a decision right now? Book a call and we will talk it through. No pressure, no pitch.