Price-to-win

Under price-to-win one understands an approach, the cost of software to determine or influence. The focus is not on the functionality of the software, but on the customer's budget.

In principle, the project must be roughly estimated using an existing method ( function point method , COCOMO , ...). Then you inform the customer of the expected effort. He then decides whether he can afford it or not. If not, a new price can be negotiated, which is usually achieved by reducing the system requirements .

example

Assuming the effort to realize a project is 100 person-months, but the customer can only afford 60 person-months, the contract will be renegotiated and the requirements minimized so that the project can be realized in less time. The price thus determines the performance or the achievement of the goal (project completion).

criticism

If projects are assessed using this method, they are often fraught with financial or time problems, since the time is usually reduced, but the requirements are too high for the minimized time.