"Why invest heavily in a solution that may not be what you need?" was the question that prompted our investigation into an alternate way of building software applications.

The common methods of designing and implementing new software solutions usually begin with

• investigations
  
• requirements building
  
• implementation, then
• Testing.
  

Most of the time, clients are involved in the first two activities, but then are left in the dark until the final tested product is delivered to them. It is only until after the clients and end users begin using this new software that they make the following discoveries:

1) The requirements did not include some design features or technical implementations now seem obviously needed.

or

2) The requirements included unnecessary features and did not allow for more straightforward executions of simple tasks.

This usually leads to expensive change order request, the previous implementation, architecture, and testing being wasted, and a delayed deployment of the software or product. In some cases, the cost to partially undo what has been done and implement another solution does not fit within the budget, and clients are left with a new website for which they already see improvements needed.

Our Proof of Concept methodology addresses these issues by involving the client in the implementation process in a unique way. This methodology allows for changes to be made much earlier, so that the initial investment in the software application or product is not wasted in what essentially becomes just a prolonged discovery process.

Once the application reaches the testing phase, both the developers and the client are aware how the product works, and have understood what possibilities for extension and simplification exist. The Proof of Concept methodology

• Lowers costs
  
• Increases client's awareness and
  
• Raises the chances of having a successful project dramatically.