Hi Sanmit, I believe your question is related to the pros and cons of showing the price in BYO.
I dont know if this is absolutely correct but here is my perspective:
If we don't associate price for each component, the respondent tends to select the best possible feature available and would not know which components are making my concept expensive. If he wants to control the price, he will either take up too much time in checking which level is effecting the price or will proceed with a higher total price.
The idea of BYO is to find near neighbours of levels selected in BYO and create relevant concepts for screener section. We may end up showing concepts with a higher price if they had selected all good levels. If total price is more than they wish to purchase then they will mark most of the concepts as Not a possibility which further increases none utility.
Thus, we always prefer to show the component level price and sometimes even validate the total configured price with the prior budget / average spending question.