Analysis of the demand for the developed system

If the concept is approved within the team, then the author of the concept presents it to the customer. According to the customer's comments, the concept is being finalized. When the contractor and the customer come to a consensus, the concept is fixed in the document version control system. The concept should be available to all project participants.

An analysis of the demand for the system should show whether this project is really interesting for the contractor, or whether it should be abandoned before too much money has been spent.

It would seem, why do we need an analysis of demand in the development of custom software? After all, the customer would not announce a competition if he did not need a program. However, the purpose of the demand analysis carried out by the contractor is to check how this project meets the interests of the business of the contractor itself.

Business interests are a very broad concept. In my practice, there were cases when we deliberately went for the implementation of a product that was not very profitable for us, but instead we got the opportunity to build trusting relationships with the customer and subsequently received orders that were beneficial for us. And, on the contrary, sometimes we refused to participate in the tender if it did not meet the interests of the business.