You should not do this because the creation costs for a catalog could quickly surmount the calculated budget.

Building a catalog is a little bit like building a house: you tend to add something here and something there and in the end the costs have reached an unintended height.

Limit your first attempt of a catalog to the essential functionality and make sure that this is implemented reliably. Collect first experiences with this version and only then conduct changes and enhancements.

This issue is really important. Very often, money and time are wasted in attempting to create and implement the ultimate catalog. The more complex the functionality is, the higher  the chance is that the first version only runs stable after a good while; the impact on the costs is obvious here.