One interesting thing about enterprise systems is that you actually have to find out what the client needs. First and foremost to be able to continue running a

One interesting thing about enterprise systems is that you actually have to find out what the client needs. First and foremost to be able to continue running a business, which may be quite complex, with moving parts that can't easily be taken offline while they are overhauled. In contrast, the vast bulk of software addresses a perceived need -- perhaps as perceived by one individual. The "need" is a hypothetical that is then tested in the market. It then becomes wanted or needed through its adoption. Most non enterprise software can also apply the 80/20 rule and implement features incrementally if at all. I think this isn't just true for enterprise software, but for software used for disciplines that have a lot of descriptive domain knowledge and arcane methods.