Custom ERP development for businesses NetSuite and SAP do not fit.

100% Australian team. Symfony stack, you own everything. No licence reseller incentives. No bias towards a platform.

The case for a custom ERP

Most mid-market businesses end up at the same crossroad. QuickBooks or MYOB has been outgrown. NetSuite is quoted at $300,000 of implementation plus per-user licence fees forever. SAP Business One is dismissed inside the first demo. Microsoft Dynamics is on the table but the consulting partner is more expensive than the licence. None of them quite fit.

The default decision is to pick the least-bad fit and absorb the implementation cost. The result is an 18-month rollout, half of which is bending the platform around your business, and the other half of which is bending your business around the platform. Five years in, you are paying licence fees on top of consulting fees, and the system still does not do the three things that actually drive your competitive edge. The platform won. The business lost.

Custom ERP is the answer when the off-the-shelf options demand more compromise than building. It is not the answer for everyone. For many businesses, NetSuite or Microsoft Dynamics genuinely is the better economic decision. The difference is operational complexity. If your business is shaped like every other business in your industry, a platform will fit. If it is shaped like your business and only your business, custom is usually the cheaper answer once you measure five years out.

The honest moment most ERP consultancies skip: we have no licence resale relationships. We do not get a kickback when you buy NetSuite. We do not get a kickback when you buy Microsoft Dynamics. We will tell you to buy them if they fit. About one in three discovery sessions we run ends with us recommending a platform implementation rather than a custom build. That recommendation is the audit deliverable, not a sales failure.

If you have already done the NetSuite or SAP evaluation and walked away, call 0431 000 062.

Symptoms to look for

Custom ERP enters the conversation predictably. These are the patterns that consistently push businesses across the line.

• The big-name ERP demos felt impressive but wrong. Your team kept asking how to model the workflows that actually make you money. The vendor’s answer was “you will adapt.” Translation: the platform cannot model your business and the implementation partner will charge you to bend it.
• The implementation quote is more than the licence. And the consulting partner has more leverage in the project than your own IT. You are about to commit to a multi-year programme where the people delivering it have a stronger commercial interest in the platform than you do.
• Your competitive edge is something the standard ERP cannot model. A unique product flow, a specific service delivery model, a regulatory environment the vendor does not understand. The workflows that make you successful do not match the workflows the ERP market assumes.
• You are running on a patchwork. MYOB or Xero for finance, a CRM, a few spreadsheets, an Access database, all manually reconciled. The patchwork mostly works, but it is now consuming more administrative effort than running the business itself.
• Reports are generated by exporting from three systems and joining them in Excel. Real-time operational visibility is unavailable. Strategic decisions are made on Monday morning, based on Friday’s data, after a four-hour reconciliation.
• You have already paid for a failed ERP implementation. The previous attempt stalled at month nine. The consulting partner moved on. The licence is still being paid for, even though nobody uses the system end to end. The sunk cost has become its own argument against trying again the same way.
• Acquisition or expansion has revealed the systems gap. A new site, a new product line, a new regulatory market: each one would require an expensive platform extension or a third-party module. Growth is being throttled by infrastructure choices made years ago.

DIAGNOSTIC

If three or more apply, custom ERP is worth costing properly. The big platforms are not always cheaper once implementation is in the picture.

The four-phase model

Custom ERP is not built by replacing all of finance, operations, and sales at once. It is built in well-chosen phases, each one delivering value on its own. The big-bang rollout is the failure mode of every platform ERP project. We do not repeat that pattern.

Phase one: the core domain

Every ERP has a core. For some clients it is inventory. For others it is jobs, or contracts, or members, or service appointments. We start by building the core. The thing the business runs on, modelled properly, with proper data integrity. This is usually three to four months. The first phase is the only phase that has to be right. Everything else builds on it.

Phase two: the surrounding workflows

Once the core is stable, we add the workflows that depend on it. Purchasing, fulfilment, service delivery, customer support. Each one comes with its own UI, business rules, and integrations. Each one ships when it is ready, not at the end of the programme. By the end of phase two, the operational team is already working in the new system for most of their day.

Phase three: finance and reporting

We do not rebuild Xero or MYOB. We integrate with them. Custom ERP handles the operational complexity. The accounting system handles the accounting. They talk to each other through clean, event-driven integrations. Xero’s API is stable and well-documented; same for MYOB AccountRight. Trying to replace your accounting system at the same time as building your ERP is how programmes turn into a four-year nightmare.

Phase four: extension and refinement

Once the ERP is the system of record, the cost of new features drops dramatically. Phase four is the long tail. Mobile apps. Customer portals. Supplier portals. Reporting refinements. Each one a small, additive build. The phase that never ends, in the best possible way. The ERP becomes the platform you build the next decade of capability on.

Three engagement shapes

We structure custom ERP engagements one of three ways. All three start with discovery.

• ERP discovery. From $8,000. Four to six weeks of discovery. Domain model, prioritised roadmap, fixed-scope build quotes for each phase. You can take it anywhere. About one in three discoveries ends with us recommending a platform implementation rather than a custom build.
• Phased custom ERP. From $80,000. Phase one (core domain) delivered as a fixed-scope build. Each subsequent phase quoted as the previous one completes. Best for businesses that want to start where the impact is highest and expand based on what they learn.
• Embedded team. From $18,000 per month. Two senior engineers as continuous capacity. Best fit for clients with a multi-year build roadmap who want a team they can rely on without hiring permanently.

Call 0431 000 062 to talk it through with an engineer.

Custom ERP we have built

Three ERP programmes. Named clients. Real outcomes. Reference calls available.

Quickway, civil construction

• Problem: Eight legacy systems with no shared customer or job record. Project management, plant tracking, finance, and field operations all had different views of the same job. NetSuite had been quoted at $480,000 of implementation plus annual licence fees the business could not justify.
• Built: Full custom ERP rebuild on Symfony over nine months. Project management, plant tracking, finance integration, field operations, customer record. Replaced all eight legacy systems with one unified platform.
• Result: $90,000 a year recovered in licence fees alone. Three FTE redeployed from admin to higher-value work. Two years live with no major incidents. Total programme cost less than half the NetSuite implementation quote.
• Stack: Symfony 7, PostgreSQL, AWS Sydney, Xero API integration, Doctrine ORM, API Platform.

Corporate Bodies, strata management

• Problem: Strata-specific compliance, levy calculation, and contractor management. No off-the-shelf platform modelled the body corporate regulatory environment properly. Existing system was a seven-year-old legacy build with no source control.
• Built: Strata-specific custom ERP and CRM with companion mobile app for on-site managers. Custom levy calculation engine, body corporate compliance reporting, contractor management. Built over 14 months.
• Result: Reporting reduced from days to hours. Mobile app rebuilt with proper offline support. Original budget held within 5%. Strata-specific business rules now codified and provable from the audit log.
• Stack: Symfony, React Native mobile, PostgreSQL, AWS, custom compliance reporting engine.

Motiv8sports, multi-site franchise

• Problem: Franchise model with split payments to franchisees, parent enrolments, and fundraising. None of the major franchise ERPs handled the Stripe Connect payment model the business needed. Weekly reconciliation across the network was a four-person job.
• Built: Franchise-specific ERP combining sales pipeline, parent enrolment, fundraising, and franchise reconciliation. Stripe Connect handling split payments across the franchise network. Built over six months.
• Result: Two admin roles removed by parent self-service. Franchise reconciliation moved from weekly to daily. Platform now supports 100+ franchises Australia-wide.
• Stack: Symfony, Stripe Connect, PostgreSQL, React Native mobile app, AWS Sydney.

Who you will work with

ERP programmes are multi-year commitments. You should know the people doing the work, and they should know you. The two engineers who run discovery are the two engineers who build, deploy, and hand over. No discovery handover. No offshore subcontract. The person who hears your business rules is the person who writes the code that enforces them.

How we ship it

Five named stages. Each one is fixed scope and fixed price. You can pause between any two phases without losing progress.

Most custom ERP programmes run 9 to 14 months end to end. The first useful phase is in production inside four months. You are not waiting a year to see value.

Custom ERP FAQs