POC (proof-of-concept) and its optimisation in a software company
Chernenko, Anton (2021)
2021
All rights reserved. This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2021111120052
https://urn.fi/URN:NBN:fi:amk-2021111120052
Tiivistelmä
This thesis explores a POC (proof-of-concept) process in a software company with an intention to streamline it and improve POC success by shortening its cycle and reducing the amount of resources spent. In more depth the objective of this final year project is to provide the case company with an action plan to be observed when starting POC with a new customer.
In software and technological companies POC, sometimes also referred to as “trial”, or “pilot” is a way to try an IT product or service before making a buying decision. The goal of POC is to test whether a given product or service provides capabilities and delivers the assurance that a customer can use it to solve their business and/or technical problem.
POC projects typically consist of a few stages and communication and information at each stage is crucial. Streamlining and shortening of each stage may play a great role in increasing project success and improving customer acquisition.
POC guidelines proposed in this thesis can be used by any software company which offers POC to its customers or wants to improve information flow with their customers overall. There is an indication that introducing tools to communicate with a customer, share and exchange information can be of a great benefit and lead to a higher customer satisfaction which is critical at the beginning of customer-vendor relationship.
In software and technological companies POC, sometimes also referred to as “trial”, or “pilot” is a way to try an IT product or service before making a buying decision. The goal of POC is to test whether a given product or service provides capabilities and delivers the assurance that a customer can use it to solve their business and/or technical problem.
POC projects typically consist of a few stages and communication and information at each stage is crucial. Streamlining and shortening of each stage may play a great role in increasing project success and improving customer acquisition.
POC guidelines proposed in this thesis can be used by any software company which offers POC to its customers or wants to improve information flow with their customers overall. There is an indication that introducing tools to communicate with a customer, share and exchange information can be of a great benefit and lead to a higher customer satisfaction which is critical at the beginning of customer-vendor relationship.