This sounds like the fence I find myself on, when designing configurators. We have a product line that has variations based on the application. They’re all pretty similar - hence why I’m making a configurator - but different enough that individual configurators might make more sense…
The innards of the products are the same - but still need configuration (current capacity, length, etc…). The outer jackets vary the most. There are: fabric, wrapped, metal mesh, and perforated HDPE jackets. Some are meant for direct burial, other for in water, etc… It’s not just different materials for the jacket, but the processes are much different.
So I wrestle with the choice of making one configurator that allows the user to select the jacket type, and the configurator has to do all the logic of which other inputs to show, set limits, etc… Or making separate configurators (one for each Jacket type).
The first only requires maintaining one very complex configurator - and not just the user input aspect but all the row rules. The second is requires four configurators that are much simpler and concise - but have a lot of overlap, meaning a simple change might need to be done 4 times (one in each configurator).