Skip to main content

AI Development | Technology Consulting Company Australia

Unlock your business’s full potential with Avenue Group Australia

background

Blog

Hiring a Dynamics
365 Partner: How to Choose the Right Cloud ERP Partner in Australia

hiring dynamics 365 partner

The vast majority of problems that occur with ERP solutions do not relate to the software itself. Rather, the problem lies with the way the solution is used by the people.

If you are an Australian business looking into Microsoft Dynamics 365, I bet you have thoroughly researched all the modules, licensing and features of this solution. Indeed, all you need & finance, supply chain, projects, CRM & everything is there and it's great. But there is one thing they won't tell you on the product page? It is not that important which platform you choose but which Dynamics 365 ERP partner to choose to implement it.

So, let's talk about how to choose a Dynamics 365 partner without guessing and marketing tricks.

Why your Dynamics 365 cloud ERP partner matters more than the licence?

Dynamics 365 isn’t something you can plug in. Instead, it’s a customisable cloud ERP solution that needs to be molded according to the way your business operates—approvals, price rules, reporting, idiosyncrasies.

A great Dynamics 365 cloud ERP partner will help you make many minor decisions right. A bad partner will get you a system that works on the technical end but that no one wants to use. We've experienced both cases, and the distinction is generally clear after about six months post go-live.

What does a Dynamics 365 ERP partner actually do?

The myth is that a good partner "installs the software." The reality is that a good partner will stay with you through all of it:

  • ➔ Discovery and planning: knowing your processes before any configurations take place.

  • ➔ Design and configuration: configuring Finance, supply chain, projects or whatever modules are necessary.

  • ➔ Data migration: moving your clean and reliable data from legacy systems.

  • ➔ Integration: integrating Dynamics 365 with banking, payroll, e-commerce, CRM and numerous other systems.

  • ➔ Training & change management: teaching your team how to use the new system.

  • ➔ Post go-live support & improvements: since cloud ERP systems are always growing, your implementation should as well.

If the partner just focuses on the first two points only, then you better ask him or her about the rest?

Why local expertise matters when hiring a Dynamics 365 ERP partner in Australia

Global ERP templates are designed on the basis of the lowest common denominator. Australia is not the lowest common denominator. If your partner considers compliance an end-of-the month issue, you will have been paying to fix it well beyond the go-live date.

Prior to signing anything, get evidence, not assurances, that your partner can deliver on the following:

  • ➔ Single Touch Payroll (STP) Phase 2: gross pay should be split into correct income classes at the data mapping stage, something which most global payroll templates cannot achieve.

  • ➔ Superannuation: super contributions must pass through an authorised SuperStream gateway or clearing house, and it is not done automatically.

  • ➔ Fair Work awards: penalty rates, overtime, and allowances differ across industries and cannot be dealt with via a generic payroll engine without localization.

  • ➔ ATO reporting: there is a different format and cadence of BAS, PAYG withholding, and taxable payments reporting.

  • ➔ Data residency: if you are regulated under the Privacy Act or an industry body (health, financial services, critical infrastructure) then make sure that your data is resident in Australia's Microsoft Azure regions.

This also holds true when it comes to delivery. A project can either succeed or fail in the process of discovery, and the best discovery will come from the presence of the right consultant at the table during the requirement generation process. The low rate is worthless if the person responsible for designing the solution works in different hours than yours and doesn't have any knowledge of BAS systems.

7 things to look for when hiring a Dynamics 365 partner

1. Knowledge of your industry

The needs of a manufacturer, aged care facility, or professional services business are completely different when it comes to ERP. Seek for samples from companies similar to yours both in size and in industry. Understanding of your industry means less time spent on explanation and much less of a surprise.

2. Knowledge of the Australian environment

This is something easy to underestimate. GST, BAS, Single Touch Payroll, award interpretation, superannuation, and local bank formats are realities here, not exceptions. A partner who knows the Australian environment will make sure that all these elements will be built in properly from the start.

3. Clear and transparent methodology

You should ask how they do their project. You should hear about phases, milestones, testing, sign-offs and decision-making process. You do not have to see a perfect chart. You just need assurance that they have a plan and will tell you right away if anything goes wrong.

4. Cloud ERP depth, not just IT proficiency

Dynamics 365 is a cloud solution, so regular Microsoft updates, Azure aspects, security roles and licensing decisions will impact your budget without you being aware of it. Your partner needs to be knowledgeable enough to advise you on everything.

5. The people who will be working on your project

A classic example: you meet the top consultants during the pitch, but the other people do the job. Inquire about the team that will be working on your project, their experience and the procedure in case someone quits mid-way.

6. Customer references you can call

Every partner can give you an impressive case study. It would be more interesting to talk for five minutes with a customer who completed a project similar to yours. Find out what he liked and disliked about the partner and his services.

Red flags worth noticing early

Nobody likes to begin a partnership in an atmosphere of mistrust, but there are some red flags that you should be aware of:

  • ➔ Quote of the job even before you know how your processes work.

  • ➔ Confusion on whose responsibility it is to complete the job.

  • ➔ Lack of concern for your data, your employees and your reporting needs.

  • ➔ Desire to sign the contract immediately.

  • ➔ No plan for training and implementation.

Selecting the wrong vendor does not normally blow up in your face; instead, it normally presents itself in terms of missed deadlines, increasing costs, frustrated staff and untrusted systems.

Things that buyers find out after the purchase

  • ➔ Sales-Delivery Gap: The consultant that sits at your boardroom is never the one that would carry out implementation. Get the résumé of the team implementing the solution before you commit yourself.

  • ➔ Third Party Costs Not Disclosed: The capability gap can be filled with different ISVs. Each has its own licensing, support, and upgrades needs. Make sure that each partner discloses all third-party applications involved in the solution and provides a TCO of three years from each.

  • ➔ The Payroll Blind Spot: Custom development will occur if the standard payroll application does not work, but custom software comes at a high price to develop, is expensive to maintain and breaks with each release wave. Make your payroll strategy known in design, not during production.

  • ➔ Release Waves: Microsoft delivers two major releases per year. Without a partner managing the testing and communicating in advance of each release wave, things may break live.

Questions to ask before you hire

Here's what to ask your next partner about:

  • ➔ What Dynamics 365 ERP implementations have you done for firms like ours in terms of size and industry?

  • ➔ How do you deal with Australian payroll, Fair Work awards, STP Phase 2 and superannuation?

  • ➔ How do you make use of Copilot and native AI capabilities to cut down on custom coding?

  • ➔ Who's going to work on our project, how many of them are located in Australia, and how do you plan on staffing this project?

  • ➔ How do you deal with release wave management from Microsoft both during implementation and post-go-live?

  • ➔ How do you do data migration and testing?

  • ➔ How do you provide support post go-live? Written SLAs, local helpdesk, escalation points?

  • ➔ Are there any two or three Australian customers whom we could talk to?

Not only the answers to these questions matter, but also the way people answer them. Direct and straightforward & that would be great. Defensive and vague, on the other hand...

Try a simple scorecard

When comparing three to five partners, the use of a weighted scorecard ensures a balanced discussion and helps in ensuring consensus within your leadership team. Use these weights as a guide and modify them according to your priorities.

CriteriaWeightGreen flag
Industry and Australian compliance expertise25%Real, recent examples in your sector, including payroll and ATO reporting
Delivery model and team20%Named onshore project lead and functional consultants from day one
Microsoft credentials15%Current Microsoft Solutions Partner status for Business Applications, plus relevant specialisations
Methodology and change management20%Clear phase gates, test approach and user adoption plan
Post go-live support20%Written SLA, local helpdesk, defined escalation path

One more thing deserves real weight even though it won't fit neatly in a cell: communication and cultural fit. You'll work closely with this team for months, sometimes years. Do they listen? Do they explain things in plain English?

Why partnership fit and clear communication matter?

Technology is teachable and configurable but trust takes time. The greatest relationship dynamics that we have seen are when our clients perceive us as an extension of their team; when we speak the truth regarding risk assessment and are as vested in success as you are.

How Avenue Group Australia approaches your Dynamics 365 project?

At Avenue Group Australia, we believe an effective ERP initiative starts with getting to know your business before talking about software. We begin by hearing about your way of working, your pain points, and your aspirations. Next, we work together to create an innovative Dynamics 365 solution that suits your needs, train your team through the transition and beyond.

We would be happy to discuss your requirements regardless of whether you are planning to replace legacy systems, migrate to the cloud for the first time or rescue a failed project.

Frequently Asked Questions

What is the cost of a Dynamics 365 implementation in Australia?

The Microsoft Dynamics 365 implementation cost in Australia is dependent on the range of scope, modules and partners. SMB project price typically ranges from $80,000 AUD to $250,000 AUD, whereas mid-market and enterprise projects usually exceed the $500,000 AUD mark in consideration of the cost of payroll, integration and change management. Don't forget to request TCO estimate for three years.

Should I choose between a local and offshore partner for Dynamics 365?

Businesses in Australia who have compliance requirements such as payroll, ATO reporting and Fair Work, are encouraged to go for a partner who has proven capabilities for delivering onshore. Delivery tasks could still be carried out through the offshore teams, but discovery, configuration and compliance tasks must be headed by the onshore teams.

What characteristics should a Dynamics 365 partner possess?

Choose 3 to 5 Dynamics 365 CRM and ERP partner Australia. Having fewer than three will be too few while having more than five will always be too many to be useful in the decision-making process.

What are the most relevant Microsoft certifications?

The new baseline Microsoft certification is now the Microsoft Solutions Partner for Business Applications. Look for specialisations in areas relevant to your modules, such as Finance, Field Service, Customer Engagement, and make sure that the designation is not just one step up from Gold/Silver.

What is the term of post-implementation support?

Make sure there is at least a year of structured post go-live support, with an agreed SLA for response time, local helpdesk and release wave management. After that period, companies usually continue on a managed services agreement.

Chat Support
×