Coral Shark Lab · Least-New-System Ladder
Built-In Feature, Integration or Custom Software — Which Should You Choose?
Direct answer
Start with the least new technology that meets the real requirement: stop or simplify, use an existing feature, configure it, connect current systems, add small custom logic, then consider custom software last.
Least-New-System Ladder
Tool comparisons start too late
“Zapier vs Make vs custom” assumes a new layer is necessary. The more profitable questions come first: can the work disappear, can the process be simplified, is a native feature enough, and is the custom requirement real or compensating for an undefined process?
Least-New-System Ladder
The Least-New-System Ladder
Move up only when a lower level fails a requirement that actually matters: control, data access, exception handling, reliability, auditability, user experience, cost or another evidenced constraint.
Least-New-System Ladder
Separate MUST from preference
Example: “disputed invoices never receive a routine reminder” may be a MUST. “The dashboard has bespoke animation” is a preference.
Least-New-System Ladder
Compare every level against the same real requirements
- Workflow fit and exception/human-boundary support.
- Authoritative data/source of truth.
- Reliability, retry and idempotency.
- Audit/evidence and security/access scope.
- Provider dependence and replaceability.
- User experience.
- Implementation and ongoing cash cost.
- Ongoing human maintenance.
- Reversibility and exit path.
If an existing feature meets all critical requirements, it wins even if custom software could look more elegant.
Least-New-System Ladder
Know when integration is the right middle layer
Integration is useful when systems of record should stay separate and there is a clear event/data/action boundary. The design should identify authoritative state, minimise copied data, detect partial failure, retry safely and record what happened.
Least-New-System Ladder
Small custom logic is different from custom software
A bounded transformation, validation, exception-routing, reconciliation or AI-interpretation adapter can sometimes meet a specific requirement without becoming a new core platform. It still creates ownership for code, deployment, monitoring, security and change.
Custom software earns its place only when durable requirements cannot be met economically/control-wise at lower levels and the business deliberately accepts long-term product ownership.
Least-New-System Ladder
Name the source of truth before integrating
State which system owns customer identity, order/job state, price/contract state, payment status, workflow status and evidence. Do not create conflicting copies merely because an automation tool makes copying easy.
For custom adapters, prefer explicit internal contracts and provider boundaries so a provider can be replaced without rewriting business truth.
Least-New-System Ladder
Use the “one level lower” challenge
Question: Can we meet every MUST requirement one level lower on the ladder?
If yes, prefer the lower level unless a material reason outweighs the simplicity.
If no, write down the exact MUST that fails before moving upward.
Evidence and claim boundary
What this page is — and is not.
Least-New-System Ladder is a Coral Shark decision framework, not a claim of scientific or industry consensus. Synthetic examples are illustrative, not customer proof. Where a material external fact is added later, it should be sourced to a current primary source and dated.
Related reading
Need this applied to one real job?
The Owner’s Brief applies the same discipline to one recurring job: what you told us, your estimates, our interpretation and what is still unknown stay separate. The answer can be stop, wait, start smaller or proceed.
Apply this to one job · £249 + VAT