My Trip To Skopje

My Trip To Skopje

This year the winter in Sweden was surprisingly moderate! Until last month that is, when we experienced some real winter with heavy snow! That called for a trip to southern lands while Stockholm was snowy and cloudy. I arranged a trip to Skopje, Macedonia to enjoy the sun, as well as to spend some time in our development center, and have a training session with the whole team, especially our newest members. Mother Nature had other plans of course- I only managed to do the latter! Luckily enough, my team didn’t blame me for snowy Skopje, rather praised me for bringing them snow!

Putting aside the story of my trip with delicious food and great & welcoming people of Macedonia, I managed to gather and meet the whole Navetti ClientCare™ team under one roof! We had two training sessions together regarding working with our Service Desk. We also reviewed and summarized the comments from our clients and discussed how we can improve our Service Desk services to meet your expectations. This included

  • communicating the progress of the tickets more frequently
  • using less technical language to explain the solution, so while it is still comprehensive and informative, it is easy to follow for users with little or no technical backgrounds

Because of these discussions, the team will now be more cautious regarding their ways of communication in our Service Desk tickets. Of course, we still appreciate your continuous feedback on how well we are managing our services, and in which aspects you would like us to improve. For example, one recent major improvement we have implemented is the expansion of the team. The need for expansion was indicated based on our KPIs as well as your comments. We at Navetti ClientCare™ are now comprised of 10 agents, compared to 4 agents one year ago. We are still in the process of recruiting.

Users of Navetti PricePoint™ who also use our Service Desk to receive support from Navetti ClientCare™ might be interested to know that our ClientCare team consists of .NET developers as well as database developers/system integrators. The .NET developers provide you support related to NPP™ and NAIS™, and database developers mostly support you with issues related to integration.

Also good to know is that we have a rotational schema in our team. This means every month 1-2 agents from the ClientCare team rotate to our development or system integration teams. This way we assure of the knowledge sharing among the team members, and make sure our developers get to know the incidents and issues our clients face and use that experience in the product development and implementation projects.

Below is a picture of a few of the people who work on our service desk:

Left to right standing: Sanja, Arsham, Johan, and Elena. Left to right sitting: Tina, Bube, Simona

</p

Arsham Mazaheri
Head of ClientCare

+46 (0) 70 032 63 79

arsham.mazaheri@navetti.com

10 Tips for a More Successful Price Optimization Project

10 Tips for a More Successful Price Optimization Project

A price optimization project is a major undertaking for any company. There are often multiple internal stakeholders, and it is likely to affect a wide range of internal systems and processes, from basic product management systems to cost and profit allocation and customer relationship programs. When done right, it can be one of the most profitable activities a company can undertake. But when done wrong, the dangers are equally significant.

Based on our experience from hundreds of price optimization projects, we have assembled some general advice for any company that is about to embark on – or is thinking of starting – a price optimization project with the target of sustainable improvements. In our experience, these 10 points are applicable irrespective of whether the aim of the price optimization project is to improve profits, increase customer satisfaction, or create better internal efficiency.

1) It Starts at the Top – C-level Support is Needed

Few things matter more to most CEOs and CFOs than their company’s revenues and profitability. And few things can impact these things faster and more positively than a successful price optimization project. Hence, it sounds like getting support from the top would be a done deal. But things are rarely that str aightforward. Pricing and price optimization represent a lot of opportunities, but there are also risks involved. Pricing has both an internal and external impact, and it must be done well in order to avoid causing frustration, problems, or both.

 

Sometimes a pricing project starts because a CEO or CFO initiates it. But more often, it originates from somewhere in the organization and eventually starts to materialize as a draft project proposal. If you are involved in the development, now is the time to prepare an executive summary of what the intended scope of the project is and what the project hopes to achieve. And of course, what resources are likely to be needed for this – including a senior executive (usually a VP/EVP/SVP, head of business, or similar) to run the steering committee that oversees the project and how well it meets its targets.

If you are on the receiving end of such a project plan, by all means question and challenge the plan and the team, but also consider the consequences of not updating your pricing strategy. And if you are a candidate for the steering committee, do try to accommodate this among your engagements. Chances are it will be one the most profitable activities you will ever overs

2) Excel is a Great Tool for Ad-hoc Analysis, but not for Operational Pricing

Some companies feel they already have control over pricing and how to set prices that optimize revenue and profits. After all, they manage the set-up today and can see the effects of price changes on the demand curve for their products and how this affects profits. Often they have developed their own business intelligence models to analyze changes in sales and profits across the product range.

 

We applaud these efforts, because they are generally done by people with a deep understanding and insight into the dynamics of their market. But invariably we find that while Excel might be a good tool for analysis, it is not optimal for managing and optimizing prices in a dynamic way, especially if a more agile and responsive pricing strategy is desired. And given the complexity of international sales, where markets, competitive situations and commercial conditions can vary immensely, a dedicated system will soon pay for itself. If we take all different permutations based on product, currency, distribution, and commercial conditions into account, the average Navetti customer manages around 28 million different price points in our system. And by manage, we mean being on top of, setting and implementing pricing strategies, doing tests to verify the strategy, and so on – rather than just coping with price management.

3) Distribute Central and Local Responsibilities Within a Common Framework

In a large organization, there are likely to be many parties that want to be involved in setting and optimizing prices. Often there is a central pricing team working with product and category management, but the local sales organization who faces the customer should also be involved. And then there are a host of other central and local functions – controlling and finance, IT, communications, customer support, etc.

 

Some companies believe that all business decisions should be made as close to the customer as possible – and we tend to agree. But when it comes to pricing, that means working within the pricing framework, not defining it. Hence, our experience shows that successful pricing projects rely on a good balance between central and local resources. It needs a hub: a central team that can establish the project structure, manage the framework, and give each market relevant recommendations. And it needs local teams that provide input to the project team and can optimize prices against local conditions and manage exceptions.

The world is certainly getting more transparent, with data and information available across the globe instantaneously. This is also a compelling argument for why a price optimization project needs to have a certain degree of central project management – because there are fewer and fewer instances of truly local prices. In addition, more companies are also standardizing their operations on a number of core IT platforms, systems, and processes – so it would only be natural for pricing and price management to be one of these core central approaches.

4) It Is a Change Management Project, not a Price List Project

Pricing and price optimization is a process that has implications well beyond the product and market dimension. While the outcome might be defined as a revised price list based on customer-perceived value and competitive adjustments, the consequences for processes and systems tend to extend in many dimensions. The end result is often a change of working processes and approaches as much as it is an adjustment of prices.

 

For example, by adopting a value-based pricing model that is anchored to customer-perceived values, a company can establish a value-based sales strategy as well. Understanding how market conditions impact price levels means better handling of different distribution channels and customer segments, not to mention reduced trading risks. And with better price management tools, there are also opportunities to review how costs and profits should be allocated and which accounting methods the company should follow.

This means that a price optimization project should be treated as a change management project. As with all change issues, different parts and functions in the company will view these changes differently, including the need for any change at all. It means that an important part of the success of the project lies in defining and communicating key strategic issues such as:

  • Why are we doing this?
  • What do we want to achieve?
  • What are the consequences of not doing this?
  • What are the goals of the project (how do we define success)?
  • What are some of the key success factors in the project?

And for each function, to have an understanding for each person’s key concern: “How is this going to affect my role and my way of working?”

5) Communication, Communication, Communication

As anyone who has been involved in a change management project will tell you, it is impossible to communicate too much. Price optimization will affect many different functions internally, and hence the communication needs to be both regular and wide. And it needs to target both your own staff as well as your customers.

 

A good approach is to think of the need as two levels of communication. One level is about communication around the project itself and the changes it involves: why it has been started, what it should achieve, what progress it makes, and so on. The other, and even more important level, is to communicate about the results: why the revised prices are set the way they are. This is something that must be communicated and understood internally by all people who face customers, so that prices can be explained and defended. In that way, the revised prices can trusted by the sales organisation, and unnecessary discounts avoided. The approach also needs to be communicated to customers, so that they understand, can accept, and trust these prices.

A general recommendation is that communication about a change project like this should be regular and reasonably frequent. Don’t wait until you feel you have enough information for a full newsletter – and as a consequence only feel comfortable communicating when the project is almost finished. Another general recommendation is to divide the communication flow into two or three streams: One that is more frequent and which goes to a smaller group of recipients that are more closely related to the project (but not directly part of the project team). And one that is more condensed and not quite so frequent, which goes to recipients that are more in the “nice-to-know” than the “need-to-know” category. If needed, additional tiers of communication content and distribution can also be added.

6) Focus on Desired Outcome Rather than a Specific Platform or Technology

It is certainly rare that a price optimization project takes place without any expected deliverable and/ or results at the end of the project. But at the same time, we would advise for some caution in already defining the deliverables in too much detail in the initial request for proposal. In our experience, the most successful projects focus on highlighting the key issues and problems, and identifying the expectations of what the desired solution should deliver, but have a fairly open view on exactly how that end solution should look or the technology on which it should be based. Clearly there are restrictions and considerations for the delivery, based on aspects such as organizational structures, existing IT systems and platforms, current operating procedures and so forth. However, being too definitive in already identifying the solution specifications in the RFP risks overlooking possible additional features and deliverables that could further enhance the performance of the system.

 

There are two reasons for this. One is the ever-increasing performance and capabilities of modern pricing systems, so that defining the deliverables in terms of a finite system specification might mean that a range of existing features and functions are neither included nor considered, perhaps not even as optional deliverables. Consequently, inviting the system providers to inform and educate their potential customer about new opportunities and pricing strategies is often a smarter approach than already having a fully defined system specification in the RFP. The other is that an RFP is generally written with an inside-out perspective, whereas an important skill of a good pricing system provider is their ability to analyze the existing pricing structure from an outside perspective. This might mean that there are additional opportunities for price optimization results that emerge from the supplier’s analysis in their response to the RFP than were apparent from the start.

7) Pilot + Full Implementation Rather than Step-Wise Approach

You may be familiar with the expression “the way to eat an elephant is one bite at a time.” Some people view pricing projects in the same way: by carefully adding incremental pieces of price optimization technology and processes in a step-wise approach, often evaluating each step before moving on to the next, they hope for a slow but steady improvement in their revenue and profit levels.

 

We think this approach works – in one aspect. But we also know that there are ways of speeding up the process. For example, by setting up a well-planned pilot where results can be evaluated quickly and comprehensively, the lessons of the pilot can be applied in full, rapid implementation across markets. Doing so repeatedly, adding modules and features in sequenced new pilots, is a tried and tested way to optimize prices and increase profits faster.

The key is to have a well-planned pilot, so that all key functions can be tested in a small-scale, but fully scoped, project. Once the “pressure test” has been performed and analyzed, and the approach verified, a full roll-out should be planned and implemented. A key part of this roll-out concerns training and transfer of knowledge to all functions that will be working in the system, so that the new resources can be fully utilized. Even in a step-wise approach, each step should also include a pilot to test the potential implications – which of course adds more time to the full implementation cycle.

8) The Right Cross-Functional Competences on the Team

In order to run a successful price optimization project according to the method described in section 6, our experience indicates that there are a couple of key success criteria that will help ensure that the project meets its intended goals. One of these is the composition of the core project team.

A good cross-functional project team contains a balance of people along two different dimensions. One is the range of different professional expertise areas needed, and the other is the personalities of the people involved. As a minimum, the following experiences and fields of expertise should be represented on the core team:

 

  • Pricing management – someone who knows how prices have been set, managed and optimized
  • Product/sales – someone who understands the category in question and the customers that buy these products
  • Business analysis/intelligence – someone who has experience in analyzing supply and demand changes and the external and internal factors that influence this
  • IT – someone who knows how pricing systems interact – or need to interact – with other systems such as ERP and/or production, sales and financial reporting

Equally important, but often overlooked, is the type of personalities of the people involved. In the same way that different professional competences are needed, it is also important to balance personalities in the team composition. Some people are driven by change and development, whereas others are more motivated by clear goals and structures, and yet others focus on the interaction between people and strive to foster good relations.

Having people with different personalities on the team will ensure a more balanced approach in how the project is run, and it means that the project will have a higher chance of long-term success than if all project team members are cut from the same mould.

9) It Is a Full-Time Job

Another important success criterium for a price optimization project is that the people on the core team are allowed to focus their attention on the project itself, and the numerous tasks that the project entails. Whilst it may be tempting from a cost perspective to assemble the team and let them manage the project in addition to their regular operative functions, our experience is that at least the overall project manager (or managers in the case of shared leadership) should be allowed to focus their attention on running the project and little else.

 

This is especially true if there are expectations for a speedy implementation and evaluation process. This will require a lot of communication and involvement across different parts of the company, which in turn puts high demands on the team’s availability and ability to interact with all relevant functions along the way.

10) Create a Reference Framework in Order to Understand Local/Segment Differences

A key challenge in many price optimization projects is how to cater for local market variations. What works well in one market will not be the ideal solution in another – and vice versa. In our experience, the best way to manage this is to go beyond “how things are today” in order to create a separate definition of “this is what we want to achieve,” i.e. how we believe the ideal situation should look. This also means defining what the different challenges are that have prevented us from achieving this so far. With such a reference model, including relevant price structures, analysis tools, etc., it is also possible to both identify the challenges and opportunities that exist in each local market and to develop practical solutions for how to implement the desired system and price optimization methods.

 

Mats Rönne
Marketing

mats.ronne@navetti.com

Help us Help you!

Help us Help you!

Clients and individuals interested in how we work with pricing often have similar questions. Our new blog portal, written by our ClientCare associates, is our way of providing easily accessible answers to your questions.

Those of you who have worked with our Service Desk may have noticed that you always get the chance to give us feedback regarding our service when the ticket you have reported to our Service Desk is closed. This is actually a great opportunity for us at Navetti ClientCare™ to assess our practices and improve the provided support.

With explanatory feedback from you, the end user, on what went well and what could have been improved upon during your experience with our Service Desk, we can improve our methods with every chance we get. However, our statistics show that many of our clients do not take advantage of this opportunity.

It may be interesting for you to know that the recent statistics from the last year of our Service Desk shows that we get feedback less than 15% of the time, even though we only need a single click from you to rate the received service by giving 1 to 5 stars. Of course, it is always beneficial and thoroughly appreciated if we can receive more constructive feedback on what worked and what didn’t when it comes to our support. Last year’s statistics show that of the 15% that clicked to give us feedback, less than 18% included their experience with us on what can be improved in our services

Of course, we constantly strive to identify areas for improvement in our services and work hard to satisfy our clients; but always a little hint from our end-users goes a long way. For that, in the latest issue of my Navetti ClientCare™ blog, I have listed five quick and easy ways that you can help us to help you:

  • Rate our service and give us constructive feedback
  • Addressing a single issue per ticket
  • Close/Cancel the ticket as soon as the issue is resolved
  • Choose the correct issue type when opening a ticket
  • Provide as much information as you can

Rate our service and give us constructive feedback

As I explained above, when a ticket is closed (either by you or by Navetti ClientCare™) you will receive an email informing you that the ticket you have opened is now closed, asking you to kindly rate the received service (Figure 1)

Figure 1: Rate the service you received from Navetti ClientCare

At this point, all you need to do is to click on the star that best represents the quality of the service you experienced.

Clicking on any of the stars will register your feedback, and at the same time opens a new page in your default web browser that allows for additional comments (Figure 2). Although commenting is optional, it is extremely helpful if you can take a moment (1-3 min) to lets us know what we did well and what can be improved in the future.

Figure 2: Constructive feedback is always appreciated

We review your feedback regularly and for future development plans of our division with the aim to always provide the best service regarding your Navetti PricePoint™.

Addressing a single issue per ticket

It is understandable that when you face multiple incidents at the same time, it is much easier to open a ticket and report all of them at once. However, I can assure you that based upon our experience working with multiple clients in our Service Desk, this does more harm than good. This is mainly because it increases the chance of confusion in the reported incident and the provided solution. This confusion can lead to longer wait times on solutions, due to extra time spent clarifying the issues at hand.

What I recommend instead is:

  • open one ticket per each incident/request
  • if the incidents/requests are related to each other, you can still a create single ticket, and mention the ticket number of the relevant incident/request in the new one. We can easily link those relevant tickets to each other, so our agents can quickly find the relation between those incidents/requests if needed for better support

Close/Cancel the ticket as soon as the issue is resolved

Another cause of confusion can be when the already reported incident/request is resolved, but instead of closing the ticket the user tries to address other matters in the same ticket by asking additional questions. This expands the recorded communication in the ticket, which can make it harder to find the relevant information if it is needed for future related issues.

What I recommend instead is:

  • open a new ticket for the new request/question, even if it can be somehow related to the previous ticket. You can request that we link the two tickets for better context and future reference
  • as soon as the issue is resolved, either let us know the issue is resolved so we can close the ticket, or you can go ahead and close the ticket by yourself from the portal (Figure 3). If the initial problem resolves itself, you can cancel the ticket right away (Figure 3).

Figure 3: Users can close/cancel a ticket from the portal

Choosing the correct issue type when opening a ticket

Currently, when you want to open a new ticket in our Service Desk you have six options to choose from regarding the type of ticket. No matter what type of ticket you choose you will receive the necessary assistance, but for our service improvement purposes it is highly appreciated if you choose the correct type that represents your request.

For example, when an incident occurs, it is important for us to know if the incident has occurred in any built-in functionalities in Navetti PricePoint™ itself, or in Navetti Apps™/reports. This is important because different teams address matters related to both. By assigning the correct type to the ticket, we will have better overview of where our products need improvements, and the correct team can start working on a solution for you right away.

Additionally, since different workflows are assigned to different ticket types (e.g. Incident Management workflow for Incident tickets, and Change Management workflow to RFC tickets), by choosing the right ticket type you ensure smoother and faster service with less confusion because of the correct workflow that will be followed by our team.

This is one of the reasons that I always encourage our clients to report issues via Service Desk portal instead of directly emailing our Service Desk, which instead creates a General Request, and can lead to slower response times.

Figure 4: Types of ticket that can be opened in Navetti Service Desk

Provide as much information as you can

A famous quote attributed to Albert Einstein reads: “Understanding the problem is half of the solution.” The same applies to our Service Desk agents!

Our experience shows that more than half of the time of our agents spend on resolving issues goes towards communication with users to clarify the problem. This is most often due to a lack of information about what causes led to the incident.

To ensure shorter waits we recommend that you include the following in your ticket:

  • the steps we need to take to replicate the problem on our end
  • related screen shots or other related files (e.g. .xlsx or .xml files)
  • clear description of your expectations
  • any examples that could help us investigate the cause of the incident

By doing this you can help us avoid any delays in resolving your issue and getting your day back on track!

 

</p

Arsham Mazaheri
Head of ClientCare

+46 (0) 70 032 63 79

arsham.mazaheri@navetti.com

Service Desk

Service Desk

Clients and individuals interested in how we work with pricing often have similar questions. Our new blog portal, written by our ClientCare associates, is our way of providing easily accessible answers to your questions. 

This is the third article in a series written by Arsham Mazaheri, Head of Navetti ClientCare™, meant to provide insights into how our clients can use Navetti ClientCare™ to their advantage on a daily basis.

In this edition of Navetti ClientCare™ working procedures, I want to guide you to our Service Desk, which is the single contact point between our clients and Navetti ClientCare™.

The content of this article are divided into five sections as follows:

  •       When and why to open a ticket in Service Desk
  •       How to open a ticket in Service Desk
  •       How to follow the status and progress of a ticket
  •       How to communicate with Navetti ClientCare™ agents via a ticket
  •       How to share a ticket with your colleagues

When and why to open a ticket in Service Desk:

In general you may create a ticket in our Service Desk mainly because of five reasons:

  • An incident has occurred regarding any of Navetti’s products or the implemented integration, and you want us to investigate and solve it, or possibly suggest a workaround for it. In such circumstances, if your Navetti PricePoint™ is integrated to other systems (e.g. ERP or CRM), you may first want to make sure the incident has not occurred because of a problem/incident in the other integrated systems
  • You have a question regarding any of Navetti’s products that you cannot find the answer for it in Navetti Knowledge Center™ or our Information Library
  • You have a service request like resetting a password, requesting access to Navetti Knowledge Center™, or any request for a service regarding our Service Desk
  • You have a Request for Change (RFC) to submit, or an idea/business need to discuss that can be implemented as a new or extended functionality in any of Navetti’s products
  • You want to add, remove, or modify data in the database

How to open a ticket in Service Desk:

In order to be able to open a ticket in our Service Desk, you first need to have an active account in our Service Desk.

To request a new account or to re-activate your account in our Service Desk, you can send an email to clientcare@navetti.com. We will then create/re-activate your account and send the credentials to your email address.

When you receive your account and its credentials, you can go to the Navetti Service Desk customer portal

Figure 1: Login to Navetti Service Desk customer portal

After you log in to the customer portal in our Service Desk, you can either search for a “how-to” article in our Information Library (A in Figure 2), or create a ticket by choosing the type of request you have (B in Figure 2).

Figure 2: Ticket types in Navetti Service Desk

 There are two ways to create a ticket in our service desk:

  • The recommended way is through our Service Desk customer portal, by simply clicking on the appropriate request type you have (B in Figure 2). Depending on what type of request you have, you may need to enter different information in the open window. In all ticket types, filling in at least a Summary of the request is mandatory. For incident tickets, filling Urgency and Impact of the incident are mandatory also (Figure 3). Our Service Desk will automatically assign a priority to your incident ticket based on the urgency and the impact you have defined. We have five levels of priority in our service desk as Blocker, Critical, Major, Minor, and Trivial, which will be assigned to each incident ticket based on different combination of Urgency and Impact.
  • The other way is to send an email to our designated email address for our Service Desk (if you don’t know the designated email address of our Service Desk, you can send an email to clientcare@navetti.com and we will help you). We generally don’t recommend this way because created tickets by email are categorized as General Request, and since no Urgency and Impact can be defined for them via email, no priority will be assigned to them.

Figure 3: Priority will be assigned to incident tickets based on the chosen Urgency and Impact

How to follow the status and progress of a ticket:

After you create a ticket in our Service Desk either via the portal or email, you will receive an automatic notification in the ticket as well as through your registered email in our Service Desk, acknowledging the ticket is registered in our Service Desk and informing you regarding the set priority (in case of incident tickets). Each registered ticket in our Service Desk will get a unique reference code (e.g. NSP-123) that can be used later for following up the status of the ticket.

To follow up the status of your ticket, you can login to our Service Desk customer portal and on the top right corner, select Requests, and then select either My requests or All requests (Figure 4). There, depending on your selection, the existing requests will be listed. You can modify the shown list by using the provided filters on top (Figure 4).

In the list you can check the status of the tickets in one glance. Clicking on the reference code in the list will open the ticket, where all the communications in the ticket is accessible.

HINT: Clicking on “Requests” will also show you the tickets that are waiting for your approval to proceed. This is required normally for RFC (Request for Change) tickets. You can click on “Approvals”, and then click on the tickets waiting for approval. You then have the option to either accept or decline the changes.

Figure 4: Navetti Service Desk customer portal

How to communicate with Navetti ClientCare™ agents via a ticket:

There are two ways to communicate with our agents through a ticket:

      Via the Service Desk customer portal

  • Log into our Service Desk customer portal
  • Open the ticket
  • Add your comment / attach documents in the ticket (Figure 5)

    Via email

  • You will receive an email notification when you open a ticket, or an activity (e.g. adding a comment or status change) is done in the ticket that you have opened or if the ticket is shared with you. In order to communicate with our agents by email, you can simply reply to the received email by keeping the subject line intact. This way, your reply will be added as a comment to the ticket and any attachment to the email will be added to the ticket as attachments. The agent assigned to the ticket as well as those who the ticket is shared with will be notified regarding your comment.

HINT: If you don’t want to receive email notifications for the activities done in a ticket, you can press “Don’t notify me” button in the ticket’s page (Figure 5)

Figure 5: Ticket’s view in customer portal of Navetti Service Desk

How to share a ticket with your colleagues:

You may want to get your colleagues involved in a ticket for various reasons. To do that (Figure 5):

  •       Go to Service Desk customer portal and open the ticket you want to share with your colleague
  •       Press the Share button in top right corner of the ticket’s page
  •       Start by typing the name of your colleague in the appeared box
  •       Press the Share button

HINT: If you regularly want to share tickets with a group of your colleagues, you can easily do so by putting all your colleagues in a so-called “organization” group, and simply share the ticket with that “organization” whenever you want to share a ticket with that group of your colleagues. You can read more about how to create organizations in our Service Desk here.

</p

Arsham Mazaheri
Head of ClientCare

+46 (0) 70 032 63 79

arsham.mazaheri@navetti.com

Release Notes and Release management

Release Notes and Release management

Clients and individuals interested in how we work with pricing often have similar questions. Our new blog portal, written by our ClientCare associates, is our way of providing easily accessible answers to your questions. 

This is the fourth article in a series written by Arsham Mazaheri, Head of Navetti ClientCare™, meant to provide insights into how our clients can use Navetti ClientCare™ to their advantage on a daily basis.

In this edition of Navetti ClientCare™ working procedures, I want to guide you through our Release Management logic and procedure and clarify how you can use Navetti Knowledge Center™ to get information regarding the new releases.

The content of this article is divided into three sections:

  • General overview of Release Management at Navetti
  • How are the releases announced?
  • How to compare the changes between releases

1. General overview of Release Management at Navetti

Currently at Navetti we apply release management on three of our products:

  • Navetti PricePoint™ (NPP™)
  • Navetti Agile Integration Suite™ (NAIS™)
  • Navetti PerformanceManagement™ (PeM™)

The versioning is based on whether we release a version, a patch, or a hotfix.

Versions include collections of new and improved functionalities as well multiple bug fixes. Versions also always include the previously released patches and hotfixes.

Patches include multiple bug fixes that are packaged together. Patches may sometimes include improved functionalities. Patches also normally include the previously released hotfixes.

Hotfix includes one single bug fix. Hotfixes that are released for the same version/patch do not include the previously released hotfixes for the same version/patch.

Patches and hotfixes are always released for the latest released version or patch. Patches and hotfixes for the previous (not latest) released versions can be created in specific cases, upon request from the client. In such cases, the released patch and hotfix will also be included in the next version, if applicable.

Given the above definition, releases for Navetti products are:

Version

NPP1.2 / NAIS1.2 / PeM1.2

Patch   

NPP1.2.3 / NAIS1.2.3 / PeM1.2.3

Hotfix   

NPP1.2.3.4 / NAIS1.2.3.4 / PeM1.2.3.4

2. How are the releases  announced?

Generally, when new releases of our products are available, the installation package along with the instructions are released in our Information Library.

As a Navetti client you can always check our Information Library in Navetti Knowledge Center™ to learn more about the latest releases of our products.

For Navetti PricePoint™, we also announce the release of new versions via our newsletter and scheduled webinars. As a user of Navetti products, we recommend signing up for our newsletter, in order to be kept up to date on all releases. You can do so here.

3. How to compare the changes between releases

In order to find the changes or fixed bugs in each new release, and compare them with your current version of Navetti PricePoint, you can access the release notes in the Information Library.

In the Release Notes tool (see Figure 1), simply enter the current version of your product and the version that you want to compare it with in the provided boxes, and click the “Change” button. All the changes between the two selected releases will be listed along with information such as the steps to test the changes in your products.

Figure 1: Release Notes in Information Library

In order to view the full content of the table, you can copy/paste the table into a MS-Excel sheet. To do so, triple click on outside of the table, just beside the title of the first column (See Figure 2), copy the content to the Clipboard, and paste it to a new MS-Excel sheet.

Figure 2: Triple click to select all text, copy and paste as plain text into Excel to view the full content of each cell.

</p

Arsham Mazaheri
Head of ClientCare

+46 (0) 70 032 63 79

arsham.mazaheri@navetti.com

How to Use a Value Based Pricing Strategy in Service Contracts

How to Use a Value Based Pricing Strategy in Service Contracts

Service contract pricing is a hot topic of conversation for many companies these days. Tunca Turkoglu, a Navetti consultant who has experience working on a myriad of projects, recently completed his Masters in Industrial Engineering and Management at the KTH University in Stockholm. His thesis centered around the application of value based pricing strategies in service contracts, and the sustainable advantages that they generate.

Please find a summary of the study below, as well as a link to the full document.

“This paper’s aim is to analyze value-based pricing strategies in service contracts and how they help companies generate sustainable advantages. Scoop of the analysis will be service contracts in manufacturing industry. A service contract could be defined as an intangible value proposition that includes but not limited to maintaining client’s machines continuously for a negotiated amount of time.

By working with a Swedish pricing consultancy firm Navetti AB, a descriptive research was conducted in an effort to answer the research question: “How to utilize a value-based pricing strategy in service contracts?”. By trying to answer this question, authors of this paper wanted to contribute to the developing framework of value-based pricing phenomena.

Results of this study indicates that certain steps need to be followed by service providers in manufacturing industry in order to utilize a value-based pricing strategy. Obscure perceived value of customers need to be realized and their value drivers need to be extracted, quantified and analyzed.

Findings of this study have implications both in theoretical and industrial perspective. From industrial aspect, service providers need to communicate with their customers deeply and analyze their value drivers, they also need to take cost-based and competition-based pricing strategies into consideration while utilizing a value-based pricing strategy. From the theoretical perspective, this study contributes to the field of pricing and price optimization part of industrial management.”

How to utilize a value-based pricing strategy in service contracts: A descriptive case study of how a Swedish pricing consultancy company optimizes pricing of services for its customers

</p

Arsham Mazaheri
Head of ClientCare

+46 (0) 70 032 63 79

arsham.mazaheri@navetti.com