ERPy Pricing
Keep your existing systems. Add the intelligence between them.
ERPy can connect with suitable business systems you already use, work with ERPNext as a complete open-source business platform, or be configured as a custom multi-system solution. Final pricing is confirmed after assessment of integrations, workflows, users, governance, data requirements and implementation scope.
How pricing is structured
ERPy pricing is based on business complexity, systems and integrations, workflow scope, and governance / customisation effort. A solo operator connecting one simple workflow is priced very differently from a multi-location organisation connecting several systems with approvals, role-based access and custom automation.
Three ways to use ERPy
ERPy Connect
Connect ERPy to suitable systems your business already uses, such as accounting, POS, eCommerce, CRM, ERP or other API-enabled software.
- Natural-language voice & text interaction
- Business information retrieval
- Guided and approved workflows
- Roles, permissions and governance
- REST API and authorised connector integrations
ERPy + ERPNext
For businesses that need a complete ERP foundation as well as ERPy. ERPNext can provide Accounting, Inventory, Sales, Buying, CRM, HR, Projects, POS and more.
- ERPNext implementation and configuration
- ERPy AI interface
- Workflow and permission configuration
- Data migration where required
- Training, testing and rollout support
ERPy Custom
Tailored multi-system integrations, industry workflows and governance for more complex operations.
- Multiple system connectors
- Custom APIs and webhooks
- Multi-location / multi-entity workflows
- Custom approvals and operational logic
- Specialised automation and reporting
Starter reference package
Solo / Sole Trader
A$2,000 setup
or A$250/week for 8 weeks
A$250/month ongoing
- 1 business entity
- Basic ERPy setup and configuration
- One straightforward primary workflow or system connection
- Standard AI assistant configuration
- Basic CRM / inquiry handling where applicable
- Standard messaging integration where applicable
- Initial testing and onboarding
Good fit for: a solo operator or small service business wanting a practical first ERPy deployment without replacing software that already works.
Indicative implementation ranges
The ranges below are retained as general public guidance. The exact amount depends on what ERPy must connect to, how much configuration is required, and whether ERPNext or custom development is included.
| Implementation Type | Setup Fee Range (AUD) | Indicative Monthly | Typical Scope |
|---|---|---|---|
| Light / Micro Integration | A$750 – A$1,500 | A$250 – A$350 | Very light configuration, one business, one simple workflow or connector, limited customisation. |
| SME / Multi-System or Multi-Branch | A$2,000 – A$6,000 | A$350 – A$650 | Multiple workflows, additional system connections, multi-branch setup, admin logic and moderate integration complexity. |
| Advanced / ERPNext / Mid-Market | A$6,000 – A$20,000 | A$650 – A$1,200 | ERPNext implementation or advanced multi-system integration, governance, approvals, data migration, custom modules or broader rollout. |
| Large / Legacy / Enterprise | A$20,000+ | Custom Quote | Full architecture, security and governance review, complex integrations, multiple entities, large-scale operations or specialised development. |
What drives implementation complexity?
Simple ERPy Connection
- One business entity
- One main system or workflow
- Standard inquiry / CRM handling
- Basic data retrieval
- Limited custom rules
Operational Integration
- Several workflows or systems
- Accounting / CRM / inventory integrations
- Projects or procurement workflows
- Role-based access and approvals
- Multiple branches or business functions
Advanced / ERP / Multi-System
- ERPNext implementation or migration
- Inventory / POS / manufacturing
- Multiple external systems
- Complex approval chains
- Custom reports, dashboards and automation
Add-ons and variations
| Add-on / Variation | Effect on Pricing | Examples |
|---|---|---|
| Operational complexity | Raises setup and ongoing scope | Advanced booking logic, approval chains, multi-step business workflows |
| Additional systems / connectors | Additional setup or connector fee | Accounting, POS, CRM, eCommerce, ERP or specialised third-party software |
| Extra branches / entities | Raises setup and support scope | Multi-location businesses and multi-company structures |
| Messaging channels | Add-on fee or pass-through cost | WhatsApp, Telegram and other supported channels |
| Custom integrations | Quoted separately where required | REST API development, webhooks, external CRM, payment gateways and custom software |
| ERPNext implementation | Depends on modules and migration scope | Accounting, Inventory, CRM, HR, Projects, POS, Buying, Selling and custom workflows |
| Support / optimisation | Monthly uplift | Priority support, tuning, reporting, connector maintenance and governance updates |
How we decide whether you need ERPNext
ERPNext is not mandatory for ERPy. If your current systems already do their jobs well, our first approach is to determine whether ERPy can securely integrate with them.
ERPNext is recommended when a business needs a new operational backbone, wants to consolidate fragmented tools, or would benefit from an open-source ERP covering areas such as Accounting, Inventory, CRM, HR, Projects, POS, Buying and Selling.
Commercial policy
- Starter pricing may be shown publicly as a guide.
- Final proposals are confirmed only after discovery and assessment.
- More complex integrations move into higher setup and monthly tiers.
- Custom connectors, unusual workflows and advanced governance are quoted separately.
- Third-party subscriptions, transaction costs and platform fees remain the client’s responsibility unless otherwise stated.
- Staged payment arrangements may be offered where agreed in writing.
Final quotation note
All pricing shown is indicative only. Final quotation will be confirmed after assessment of the company’s existing software, required integrations, workflows, data structure, locations, user roles, permissions, approval requirements, AI usage, support requirements and any ERPNext or custom-development scope.
Not sure which option fits?
Tell us what software your business currently uses and what you want your team to be able to ask or do. We can then determine whether the best fit is ERPy Connect, ERPy + ERPNext, or a custom ERPy implementation.
Last updated: 3 November 2026