To get a trial key
fill out the form below
Team License (standard version)
Enterprise License (extended version)
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Request our prices
New License
License Renewal
--Select currency--
USD
EUR
GBP
RUB
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Message submitted.

Your message has been sent. We will email you at


If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

>
>
Selling to decision makers

Selling to decision makers

Feb 25 2013

If you are doing test-drive of PVS-Studio for your organization, and you liked the software and services we are offering the next big step is convince decision makers in the organization that static code analysis for C++ projects based on PVS-Studio product is effective investment.

Note: if you are decision maker yourself you might still benefit from reading this article as you might find few interesting facts about PVS-Studio that you didn't know before.

So first thing you need to understand is who is /are decision makers for purchasing of new software and implementing significant changes to the development process (which obviously introduction of static code analysis is).

  • In case of rather separated or one-off projects it might be project lead or project manager
  • When a larger development organization is in place these decisions are usually approved by top manager in charge of the whole development organization
  • In the large technology-oriented companies there might be separate organization that controls selection, purchase and provides maintenance and customization of development tools

Next step is to understand who potential stakeholders of this product are. These are the people who are directly or indirectly are affected by introduction of the software. Usually they see additional tools as a more support burden, but we have to be proactive in presenting benefits of these changes:

  • Quality Assurance will definitely get a lesser number of issues to deal with, and overall product quality should improve also. There is a high chance that some of these 'uncatchable' bugs will be caught with static analysis, and less of such bugs will be introduced
  • Build engineers. As integration of PVS-Studio into the development process require some efforts and support from Build engineers it will definitely make their life easier in the long run due to lower number of emergency rebuilds, late night fixing shifts etc.
  • Peer developers. Sometimes developers have a strong feeling that static analysis is put in place to highlight someone's failures. Of course it heavily depend on organizational culture, but when talking to other developers you need to stress that management sees this tool as an early error prevention not as a way to blame and point fingers.
  • Senior management usually sees static code analysis tools as an additional line in the budget, however the main goal is to show that introduction of this tool leads to decrease of the cost paid for each feature, and also to overall increase in product's quality. Currently it is rather hard to estimate return on investments (ROI) into the static code analysis tool (like PVS-Studio) but numerous studies shows that it is definitely positive.

After all stakeholders are identified it is a good chance to engage with each of them informally and discuss their vision on static analysis, understand who supporters of this change are and who will be objecting. It is important to understand their objections and be prepared to address them during the management presentation.

Next big step is preparation of the presentation. You might want to use our template presentation of PVS-Studio static analysis tool as a base line that should be enriched with the detailed results of your trial.

Also on this stage do some homework and be prepared to address objections of the people who do not like the idea of introduction of static code analysis tool into the process.

Please note that our presentation of PVS-Studio doesn't concentrate much on exact errors it might detect - this of course depends on the particular project, rather it highlights other benefits of having static analysis tool in place.

Then time comes for the big presentation. Make sure that all decision makers are able to attend the meeting and all stakeholders are invited too as optional attendees.

Hint: talk to main supporters of this project to make sure they could attend the meeting.

There should be no major problems - by the time you do the presentation you already know most of the objections people have about this kind of software and PVS-Studio in particular.

As usually the most important outcome of this presentation should be either a final decision on starting this project or set of open discussion points.

Please feel free to contact us if you need help addressing questions you face on static analysis or PVS-Studio functionality.

Popular related articles
Static analysis as part of the development process in Unreal Engine

Date: Jun 27 2017

Author: Andrey Karpov

Unreal Engine continues to develop as new code is added and previously written code is changed. What is the inevitable consequence of ongoing development in a project? The emergence of new bugs in th…
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: Jul 31 2017

Author: Andrey Karpov

After I wrote quite a big article about the analysis of the Tizen OS code, I received a large number of questions concerning the percentage of false positives and the density of errors (how many erro…
Appreciate Static Code Analysis!

Date: Oct 16 2017

Author: Andrey Karpov

I am really astonished by the capabilities of static code analysis even though I am one of the developers of PVS-Studio analyzer myself. The tool surprised me the other day as it turned out to be sma…
The Evil within the Comparison Functions

Date: May 19 2017

Author: Andrey Karpov

Perhaps, readers remember my article titled "Last line effect". It describes a pattern I've once noticed: in most cases programmers make an error in the last line of similar text blocks. Now I want t…
The Last Line Effect

Date: May 31 2014

Author: Andrey Karpov

I have studied many errors caused by the use of the Copy-Paste method, and can assure you that programmers most often tend to make mistakes in the last fragment of a homogeneous code block. I have ne…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: Nov 21 2018

Author: Andrey Karpov

A brief description of technologies used in the PVS-Studio tool, which let us effectively detect a large number of error patterns and potential vulnerabilities. The article describes the implementati…
PVS-Studio ROI

Date: Jan 30 2019

Author: Andrey Karpov

Occasionally, we're asked a question, what monetary value the company will receive from using PVS-Studio. We decided to draw up a response in the form of an article and provide tables, which will sho…
The way static analyzers fight against false positives, and why they do it

Date: Mar 20 2017

Author: Andrey Karpov

In my previous article I wrote that I don't like the approach of evaluating the efficiency of static analyzers with the help of synthetic tests. In that article, I give the example of a code fragment…
Free PVS-Studio for those who develops open source projects

Date: Dec 22 2018

Author: Andrey Karpov

On the New 2019 year's eve, a PVS-Studio team decided to make a nice gift for all contributors of open-source projects hosted on GitHub, GitLab or Bitbucket. They are given free usage of PVS-Studio s…
PVS-Studio for Java

Date: Jan 17 2019

Author: Andrey Karpov

In the seventh version of the PVS-Studio static analyzer, we added support of the Java language. It's time for a brief story of how we've started making support of the Java language, how far we've co…

Comments (0)

Next comments

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
This website uses cookies and other technology to provide you a more personalized experience. By continuing the view of our web-pages you accept the terms of using these files. If you don't want your personal data to be processed, please, leave this site.
Learn More →
Accept