About us

How we work

At Amista, we implement best-practice solutions which will make your business run faster.

Amista has done complete end-to-end implementations of SAP solutions both on-premise and in the cloud. Therefore, we have a broad experience with delivering successful projects. Over the course of time, we have witnessed a change in the expectations of our customers when it comes to time to value. Out of that, we have defined our own project methodology which is based on the following cornerstones:

Agile project management
We go for short iterative implementation cycles focusing on the features that provide the most business value. This allows for shorter implementation cycles and a higher return on investment.

Industry best practices
Our SAP solutions come with industry best practices. These best practices have a proven track record of making your business run better, leaner and faster. We always promote these as the starting point of every implementation as it will shorten considerably your implementation time.

End-user enablement
We don't just implement solutions and leave. We want to make sure the end-user is enabled and confident with the new system. Therefore we always recommend having a learning track which can support you in the change with SAP Enable Now.

Know our business

Working with Amista

09.00 am

Meeting with the project team

Every morning we have a short standup with the project team at the customer to discuss our tasks of the day. We share our ideas and challenges. The deadlines and the daily tasks are set.

10.30 am

Skype call with our offshore team

For our offshore team in India it's already 03.00 pm, time for a quick update. The project manager has a skype call to align and see if there are any open questions. This type of communication is used throughout the day between the consultants as they are often scattered across the country.

01.00 pm

Consulting stuff

Our consultants are very busy conducting workshops, documenting and implementing SAP solutions.

04.00 pm

Scrum Meeting

Scrum meeting with the customer and the project team. We discuss the status of the project followed by a demo of the solution. We get feedback and we review the action points.

06.00 pm

Get-together

Every six weeks we organize a get-together in our office. During this event, the latest project developments are presented, newcomers are being introduced, the sales and opportunity pipeline are evaluated,... It's a great initiative to work on the Amista team spirit. Afterwards we'll catch up with some drinks.

We're different

Why Amista?

One team

In all the projects we do, we always make sure that our customers are also part of the team. Getting you involved as much as possible in the project is a very important aspect. Only as a team we can succeed!

Knowing your business

Although there are similarities in the way certain industries do business, every company has its particularities. Gaining knowledge of the way you work is a critical part of our solution design.  

We are agile

Agility is the cornerstone of our implementation methodology. Rather than spending days and months blueprinting, we believe in short iterative cycles combined with best practices. We start by working with you to define a list of requirements and priorities followed by different release cycles. This way of working allows to have a quick time to value while your organization has the time to adapt to the new solution.

Experience is key

All our people have a broad knowledge of SAP or Dell Boomi solutions. Knowledge sharing and learning are very important within Amista. Additionally, all our consultants are experienced in the way projects should be run and managed. These soft skills are critical to the success of a project.

Say:do equals 1

We will only commit to a solution we think is feasible. And if we commit, we will go the extra mile to make sure we can deliver. We translate that internally in the say:do ratio which should always be equal to one. That is how we want to build trust with our customers.

Embracing change

Often omitted, change management is an essential part of our methodology. Acceptance of the solution is key. Making sure your organization gets used to the new environment and tools starts early in the project with an adequate communication and training plan. Future users need to understand the value of the new way of working.