ERP vs custom software: which should you build?

Most teams don’t actually need “an ERP” or “custom software.” They need fewer spreadsheets, cleaner handoffs, and numbers they can trust. The label comes later. The decision that matters is how much of your process is unique, and how expensive it is when the tool fights that process.

01 Start with the work, not the product category

Map the jobs your system must do every week: quoting, stock, invoicing, job cards, approvals, reporting. For each job, ask two questions: is this standard across your industry, or is it a competitive edge? And if the tool is awkward here, does someone invent a workaround that becomes the real system?

If most of the work is standard, a well-chosen ERP or mid-market platform usually wins. If the awkward edges are where you make money, custom software (or a hybrid) starts looking cheaper over a three-year horizon.

02 When an ERP is the right call

Your workflows match common patterns: inventory, finance, CRM, purchasing, and basic manufacturing or services.
You need audited accounting, tax reporting, and role permissions without inventing them from scratch.
Multiple departments must share one source of truth, and “good enough” process beats perfect process.
You have appetite to adapt the team a bit so the software can stay maintainable.

“ERP” here includes full suites and lighter operations platforms. The point is buying a proven spine instead of rebuilding payroll, stock ledgers, and audit trails for sport.

03 When custom software is the right call

Your quoting, scheduling, or fulfilment logic is genuinely unusual, and every off-the-shelf option needs painful configuration or spreadsheet side-doors.
Speed of change matters: you want to ship a workflow tweak in days, not wait on a vendor roadmap.
Integrations are the product: local payment rails, industry hardware, legacy databases, or partner APIs that packages treat as afterthoughts.
You need a focused tool for one high-value domain, not a company-wide suite on day one.

Keep finance in a trusted platform. Build a custom operations layer for the messy middle. ERP as system of record. Custom as system of work.

04 The hybrid most growing companies actually need

A common One Hog pattern: keep finance and core ledger in a trusted platform, then build a custom operations layer for the messy middle (job tracking, field apps, customer portals, pricing engines). The ERP stays the system of record. The custom layer stays the system of work.

That split keeps you from forcing accountants into a fragile custom stack, and keeps operators out of screens designed for auditors.

05 A simple decision test

List your top ten weekly workflows. Mark each as standard or unique.
Cost the workarounds: hours lost, errors, delayed invoices, missed stock.
Trial an ERP-shaped tool against your unique workflows only. If configuration still feels like rewriting the product, custom is honest.
Budget for ownership: licenses and consultants vs build and care. Compare three years, not three months.

06 What we recommend talking about first

Bring the workflows, the painful spreadsheet, and the report nobody trusts. Skip the buzzwords. We’ll tell you plainly whether you need an ERP spine, a custom build, or a hybrid, and what a sensible first release looks like.

If you’re stuck between options, start a conversation or read the next note on what to decide before building a mobile app.