Three SaaS tools, one finance lead, and a Sydney board pack that takes nine days to assemble in Barangaroo
A custom ERP (Enterprise Resource Planning) for a scaling Sydney business runs $110k to $200k and 5 to 8 months. You build once Xero plus a billing tool plus a CRM (Customer Relationship Management) plus a warehouse app stop reconciling, and your monthly board pack takes a week of someone exporting CSVs and praying the revenue number ties. The trigger in Sydney is almost always post-raise: a Series B startup in Surry Hills or a professional-services firm in the CBD where multi-entity, multi-currency, and GST/BAS reporting have outgrown the SaaS stack.
You raised a Series B, headcount doubled, and the finance stack that worked at 20 people is now four disconnected tools held together by a finance lead who knows where every body is buried. Xero handles the ledger, a separate billing tool runs subscriptions, the CRM holds the revenue pipeline, and none of them agree on what a customer is worth. When the board asks for ARR by cohort, someone exports three CSVs at 11pm.
Off-the-shelf ERP like NetSuite or SAP can fix the fragmentation, but the SuiteCloud customization quotes land at six figures a year, and you are now renting a consultant who bills in US hours to bend a US-centric system around Australian GST, BAS lodgement, and Single Touch Payroll. For a fast-moving Sydney company that expects integrated, polished software, paying a NetSuite partner $250 an hour to recreate logic you understand better than they do is the worst of both worlds.
Where the off-the-shelf tools fall short
- Customer data split across Xero, the billing platform, and the CRM, so no single number for revenue or LTV survives scrutiny
- Multi-entity consolidation across AU and an overseas subsidiary done by hand in Excel every month-end
- GST and BAS reporting reassembled manually because the billing tool and Xero categorise the same transaction differently
- Board pack and investor reporting takes a week because ARR, churn, and cash runway live in four systems
Custom erp: what Sydney teams actually get
A custom ERP makes one model of a customer, an invoice, and an entity the spine, so subscription billing, the GL, and pipeline all read from the same record. Instead of paying a NetSuite partner to approximate Australian BAS and STP, the system encodes your exact entity structure, your AUD-and-USD consolidation, and your revenue-recognition rules. The board pack becomes a query, not a fire drill, and the revenue number is the same whether finance, sales, or the CEO pulls it.
Feature priorities for Sydney teams
Sydney ERP: the full scope
The engagements Sydney teams bring us most often: NetSuite customization, SAP integration, Odoo development, Microsoft Dynamics 365, ERP migration, cloud ERP and manufacturing ERP.
- Your NetSuite or SAP customization quote rivals or exceeds the annual license for Australian-specific logic
- You run two or more entities and consolidate AUD and USD by hand each month
- The board pack takes a week because revenue lives in four systems that disagree
- You have raised a Series B and a financial-statement audit is on the horizon
- You are a single AU entity under 30 staff and Xero plus one billing add-on still reconciles cleanly
- Your revenue model is simple enough that off-the-shelf SaaS reporting answers the board's questions
- You have no engineers to spare and need integrated reporting in weeks, not months
- NetSuite out of the box covers your entity and currency structure without heavy customization
The honest cost picture for Sydney
| Project scope | Typical cost | Timeline |
|---|---|---|
| Core financials, unified customer model, AU GST/BAS and STP | $110k to $150k | 5 to 6 months |
| Add multi-entity consolidation, multi-currency, revenue recognition | $150k to $175k | 6 to 7 months |
| Full investor reporting, audit-grade controls, integrations to billing/CRM | $175k to $200k | 7 to 8 months |
Timeline: what happens, and when
Exactly what you get
A finance backbone where one customer record drives billing, the ledger, and the pipeline, so the ARR number is identical no matter who pulls it. Subscriptions and usage feed revenue recognition; recognition feeds the GL; the GL produces BAS-ready output and an investor dashboard. Two entities consolidate in AUD without a manual Excel merge, and the month-end close stops depending on one person who knows where every reconciliation lives. The board pack becomes a saved query.
How to choose a developer in Sydney
Hire a team that has shipped financial software for an Australian scale-up, not just a generic ERP integrator. Ask them to walk you through GST treatment on a partly-overseas invoice and how they would consolidate two entities at month-end. Local fluency matters: a Sydney developer who knows ATO lodgement, STP, and the way a Barangaroo professional-services firm bills will build something that survives your auditor. Adjacent systems like a custom CRM for the revenue pipeline, business intelligence dashboards for board reporting, and internal tools for finance ops should come from the same team so your customer data finally lives in one place.
- One customer and revenue model across billing, ledger, and pipeline, so ARR ties on the first export
- Multi-entity, multi-currency consolidation (AUD/USD) that runs at month-end instead of a manual Excel merge
- GST and BAS reporting derived from one transaction source, so lodgement stops being a reconciliation project
- Investor and board reporting generated on demand, cutting the nine-day pack to a same-day query
- Workflows that fit an Australian scale-up instead of a US-centric template you pay a partner to override
- You own the build, so when the ATO changes BAS or STP rules you patch it, where NetSuite or Xero ships the update for you
- A custom GL that mishandles revenue recognition is a worse problem at audit than a documented Xero limitation
- Building during a high-growth year competes for the same engineers your product roadmap needs
- No vendor community hitting the same edge case first, so unusual multi-entity scenarios surface in your production
- !A vendor who has never handled GST, BAS, or Single Touch Payroll; ask them to explain how BAS lodgement works
- !They quote a fixed price before seeing your entity structure; ask how they handle AUD/USD consolidation
- !No plan for an audit trail when you are heading toward a financial-statement audit; ask how access is logged
- !They push you straight to a NetSuite reseller arrangement; ask what they would build versus configure
- !No mention of revenue recognition for subscriptions; ask how deferred revenue is modelled
If erp is on the roadmap, internal tools, shopify, inventory management usually follow within the year. Budget them as one conversation.
Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.
Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
Will a custom ERP handle Australian GST and BAS properly?
Yes, when it is designed around ATO rules from the start. The system tags every transaction with the correct GST treatment, including the edge cases an overseas subsidiary creates, and produces BAS-ready output that ties to the GL. It also exports Single Touch Payroll data. The difference from a US-centric tool like NetSuite is that BAS and STP are native, not a partner-built bolt-on you pay to maintain.
Why not just keep scaling on Xero plus add-ons?
For many Sydney businesses, Xero plus a billing tool is the right answer well past 30 staff. You go custom when the add-ons stop reconciling, when multi-entity consolidation eats a day every month, or when the board pack takes a week because four systems disagree on revenue. Below that, the SaaS stack wins on cost and speed.
How does this help before a Series C raise?
A financial-statement audit ahead of a Series C needs one source of truth with a clean audit trail. A custom ERP that unifies billing, ledger, and pipeline gives auditors a single revenue number they can trace, instead of three CSVs that nearly tie. It also produces the cohort and retention metrics a Series C investor will ask for, on demand.