Many teams waste months rebuilding tools that already exist. Other teams buy a tool and then spend years fighting it.

The smart move is usually a blend. Buy proven systems for commodity work. Build only where the business is unique.

The A.C.E. Rule

A.C.E. is a fast filter for Build vs Integrate?

A . Advantage

Build when it creates a competitive edge.

Signals:

The workflow is unique to the company
The process affects revenue, margin, or retention
Speed and accuracy here matter more than anywhere else

C . Commodity

Integrate or buy when it is common across most companies.

Examples:

Email
Payroll
Basic accounting
Standard CRM functions

E . Ecosystem

Prefer tools that already connect well to what is in place.

Questions:

Does it have a stable API?
Does it support webhooks or exports?
Does it have reliable integration options?

This is responsibility in practice. The goal is lower risk and fewer moving parts. It is also speed. Integration often ships faster than building from scratch or worse, rebuilding.

The “Thin Custom Layer” Pattern

A common best practice is a thin custom layer over proven systems:

Custom portal for customers or staff
Custom approvals and routing
Custom dashboards and alerts
Custom automation that stitches systems together

This is where craftsmanship matters. Clean integrations, stable data contracts, and good logging prevent silent failures.

Mini Case Study. Agriculture Ordering and Inventory

Problem: An agriculture supplier wanted a full custom system for customer ordering, inventory, and delivery planning.

Mistake: The plan was to rebuild everything, including standard product and invoice management. That would have duplicated what their ERP already did well.

Fix: The project used A.C.E.

Commodity: Keep ERP for core product and invoicing
Ecosystem: Use the ERP’s API for data exchange
Advantage: Build a custom ordering portal with smart rules for seasonal availability, customer-specific pricing, and delivery windows

Generosity showed up as proactive guidance. Our team recommended what not to build, even though building more would have increased revenue.

Result: The portal launched sooner, staff had fewer workarounds, and the business kept the stability of proven systems while gaining custom advantage where it mattered.

Quick Takeaways

Build for advantage. Integrate the rest.
A.C.E. keeps decisions fast: Advantage, Commodity, Ecosystem.
A thin custom layer often beats rebuilding entire systems.
Good integrations require craftsmanship, not shortcuts.

Build or Integrate? When Custom Software Isn’t the Answer