Requirements and fit
Map business processes and compare standard capabilities with genuine gaps.

Business systems · Align the process, the data and the people.
ERP changes affect people, processes and data. The implementation plan needs to account for all three.
Understand the capability
ERP implementation coordinates the systems and processes behind finance, inventory, procurement or production. The difficult work is often aligning business rules and data, then preparing people for a consistent way of operating.
A coordinated rollout with reconciled data and prepared users.

Key takeaways
Where progress gets stuck
Customisation begins before standard processes are understood.
Master data is not ready for migration.
Testing focuses on screens instead of end-to-end transactions.
Users meet the new process only at go-live.
Make the problem and baseline visible before selecting a tool.
Design the workflow around real users and operating constraints.
Test important decisions, data and exception paths.
Leave an accountable owner and a practical handover.
What the work can include
Combine the capabilities the outcome requires. Each engagement is scoped around your existing systems, the team using them and the decisions they need to make.
Map business processes and compare standard capabilities with genuine gaps.
Configure roles, approvals, master data and transaction flows around agreed operating rules.
Connect surrounding systems with ownership and reconciliation rules for exchanged information.
Clean, map and validate records using rehearsal migrations before final acceptance.
Test end-to-end business scenarios and train people using the work they will actually do.
Plan cutover, escalation, rollback decisions and a stabilisation period with named owners.

Designed for the real world
A coordinated rollout with reconciled data and prepared users.
From understanding to action
01Map business processes and compare standard capabilities with genuine gaps.
02Configure roles, approvals, master data and transaction flows around agreed operating rules.
03Connect surrounding systems with ownership and reconciliation rules for exchanged information.
04Clean, map and validate records using rehearsal migrations before final acceptance.
05Test end-to-end business scenarios and train people using the work they will actually do.
Tools selected for the task
Technology choices follow the requirements, constraints and maintenance plan. Inclusion here describes tools that may be considered; the final stack is agreed in discovery.
How it works · Our method
01We talk to the people doing the work, map the current process and agree on the problem before recommending technology.
A shared problem statement and a map of the current workflow.
02Establish a baseline. Identify the handoffs, bottlenecks and costs that make the biggest difference to your operation.
A baseline, prioritised opportunities and agreed success measures.
03Turn the evidence into a practical plan. Evaluate options, dependencies and trade-offs, with your team involved throughout.
A delivery roadmap, solution design and acceptance criteria.
04Deliver in reviewable increments. Test real workflows, handle exceptions and prepare your team to own the result.
Working software, tested integrations and a prepared team.
05Review actual use against the baseline. Fix friction, refine the roadmap and adapt as your business changes.
An improvement backlog and an agreed review rhythm.Where we work
Start a conversation with Ichelon about your team, operating hours and delivery needs. Working arrangements, access and review rhythms are established as part of the engagement.
info@ichelon.com.au 0451 608 058Cost and engagement
Agree on the work before committing to delivery. Scope, timeline, ownership and dependencies belong in the same conversation as price.
Agreed after discovery
Make the current situation, options and next decision clear. A useful starting point when scope or dependencies are still uncertain.
Discuss the fitAgreed after discovery
Deliver an agreed set of capabilities with acceptance criteria, review points and a plan for handover.
Discuss the fitAgreed after discovery
Review how the result is used, address friction and prioritise the next changes against business outcomes.
Discuss the fitFrequently asked
Only after comparing the business value of a requirement with configuration and process alternatives. Each customisation introduces maintenance and upgrade responsibilities.
Agree on source records, transformation rules and reconciliation totals. Run rehearsals, investigate exceptions and obtain business acceptance before the production cutover.
Dependencies between functions, locations and systems determine whether a phased or coordinated rollout is practical. Training, cutover support and operational capacity are part of that decision.
We begin with the current situation, the outcome you need and the constraints around erp implementation. Discovery identifies dependencies, responsibilities and acceptance criteria before a delivery plan and quote are agreed.
The price depends on scope, integration needs, existing systems and the level of uncertainty. A focused assessment helps establish a realistic estimate. Any ongoing platform charges and third-party costs should be visible alongside delivery work.
The engagement is designed around your team’s context. We agree on the product owner, technical contacts, access, review points and handover responsibilities before implementation begins.
Related services
Learn more

Insights · 1 min read
The most valuable configuration decision may be the field you choose to leave out.
Read the perspective
Insights · 2 min read
A good-looking chart is the visible end of a much larger agreement about information.
Read the perspective
Insights · 2 min read
A roadmap should help people make investment decisions, not just display a list of proposed projects.
Read the perspectiveLet’s move forward
Share the business challenge. We’ll establish the questions and next steps together.
Start the conversation