May 2026
Every few months a client arrives with the same opening line: we have outgrown our current system, and we need to decide whether to configure another product or build something that matches how we actually operate. The question sounds binary. In practice it is a spectrum of fit, ownership, and ongoing cost.
Start With Workflow Fidelity, Not Feature Lists
Packaged products are designed around a generic model of your industry. That model may be close enough for a startup or a branch office. It stops being close enough when approvals zigzag across roles, when pricing rules depend on site-specific contracts, or when compliance requires fields your vendor considers custom objects at extra cost. We ask clients to map three workflows end to end — the ones that would hurt most if wrong — before comparing licence tiers.
Custom software is not automatically the answer. Building from scratch to replicate basic CRM or accounting functions is rarely justified when mature products exist. The case for custom strengthens when differentiation lives in operations: how jobs are scheduled, how inventory moves between depots, how exceptions are recorded for audit. Small Pea Software typically recommends custom development when workflow fidelity gaps would force daily workarounds that staff compensate for with spreadsheets and informal messaging.
Feature checklists mislead because vendors count capabilities that your staff will never enable. A long feature matrix creates false confidence. We prefer workshops where operational staff walk through real scenarios: a rush order, a partial delivery, a credit adjustment, a compliance exception. If the packaged demo cannot represent those paths without awkward detours, the gap is structural rather than configurational.
Total Cost Includes Change, Not Just Licences
Packaged software looks cheaper in year one because subscription fees are predictable and implementation partners quote fixed packages. Hidden costs accumulate: per-seat pricing as headcount grows, integration middleware to connect systems the product does not talk to natively, consultant hours each time the vendor changes their data model. We encourage clients to model a five-year horizon including internal time. Staff who re-key data between systems are paying a tax that never appears on an invoice.
Custom development front-loads design and build cost but can reduce recurring fees and eliminate duplicate data entry when the application is shaped around a single source of truth. Maintenance is not free — applications need security updates, dependency refreshes, and feature evolution — yet ownership means you control priority. A critical regulatory change can be scheduled rather than waiting for a vendor roadmap.
Australian organisations should also factor data residency, support hours aligned to local time zones, and contractual terms under Australian law. A global SaaS bargain loses appeal when every support ticket crosses midnight or when export controls complicate where backups may be stored.
When Packaged Software Is the Right Call
- Standard processes with minimal exception handling.
- Need to go live quickly with low initial capital outlay.
- Vendor ecosystem covers most integrations you require.
- Internal IT capacity is limited and prefers outsourced upgrades.
When Custom Development Earns Its Place
- Operational advantage depends on proprietary workflow logic.
- Multiple existing systems must converge into one staff-facing portal.
- Compliance or reporting requires granular audit trails not offered off the shelf.
- Per-user licensing would scale poorly against your staffing model.
We have seen organisations spend more adapting a generic product than they would have spent building a focused tool — not because the product was bad, but because the mismatch was fundamental.
Hybrid Approaches Are Common
Many stable solutions combine both: accounting stays on a proven ledger platform while operations run in a custom web application fed by API integrations. Small Pea Software often builds the operational layer and connects it to finance, identity, and messaging systems clients already pay for. The integration plan becomes as important as the build itself.
Hybrid models fail when boundaries are vague. Document which system owns customers, inventory, and invoices before writing code. Without that clarity, teams debate numbers in meetings instead of trusting dashboards.
Before you sign another multi-year subscription, document your non-negotiable workflows and estimate rework hours when the product says no. If those hours exceed a structured build, custom software deserves serious consideration. We are happy to review your scenario in a discovery session and tell you honestly when packaged software is sufficient.
The decision rarely needs to be permanent. Organisations that start with a focused custom operational layer while retaining proven finance platforms often revisit the balance after two or three years of stable operations. What matters is making the choice with eyes open about workflow fidelity, integration cost, and who will maintain the result — not chasing the lowest year-one licence quote.
