Every planned project or software implementation needs to start with thorough preparation and a clear understanding of project scope and requirements. Without understanding across parties there is potential for confusion, and with confusion comes project delays, conflicting expectations, missed deadlines and even possible project failure.

At Inatech, we know how important it is to build an understanding of your business and to accurately establish the scope of a project, well before beginning any product implementation.

As part of our consulting services, we provide two services Assessment and Change Management. These services ensure your organisation is fully prepared for the next stage – software implementation.



At Inatech we work collaboratively with you at every stage of a product implementation. Nowhere is this more apparent than during the assessment phase of any project.

At the assessment we listen to your specific business needs, interpret them and document them. Our focus to understand your business and its requirements, and to build a picture of your IT landscape in order to deliver an accurate statement of work.

What we offer:

  • A 2-3 hour onsite workshop
  • A discussion focused around business issues, project requirements, IT issues and desired outcomes
  • A demonstration of a number of end-to-end key business scenarios, designed to build understanding and cover all business functions - front-office, mid-office and back-office
  • Meaningful real-life examples using sample customer data
  • Product demonstrations to show you the type of user interface, user experience, analytics and reporting capabilities available.



Installing new software or implementing a new business process usually means change. In any company there will be some resistance to this change. This can disrupt, delay or even jeopardise a project.

To address employee concerns and reduce resistance as early as possible in a project, Inatech has developed its change management service. This service adopts industry best practices and has been created in consultation with our parent company, Glencore.

By addressing resistance early you can reduce the likelihood of encountering the problem further into the implementation. The graph demonstrates the benefit of this approach.


Traditional Implementation Method – Resistance increases over time Change Management Method – Max Resistance is invited at the beginning.

Reaction to change:

Resistance to change typically happens at two different phases of a project:
  • At the initial phase of a project (the discovery phase)
  • At the time of User Acceptance Testing (UAT) near the end of a project (the delivery phase)
Resistance typically happens during the delivery phase where the resistance to change is very high. By that time:
  • The organisation has spent a lot of time and money on the project
  • The organisation is usually left with no choice but to impose the project on employees, which in turn creates more resistance amongst the employees and the possibility of a failed project.

Our service offering:

Using Inatech’s unique 4D methodology we aim to tackle any resistance at the start of the project. We achieve this by:
  • Involving all the key stakeholders
  • Identifying the people likely to resist change
  • Working with impacted employees, listening to their objections and working with them to demonstrate the benefits of the project/implementation.

View our other services