What should we do?
fauigerzigerk: After reading the long version of your question I want to say that my own experience with generic application generators is very similar to yours. Users want functionality and wording that is very specific to particular tasks.Therefore any generic framework can only ever serve as a basis for you to create specific applications. The question remains whether a generic framework or generator actually makes that task any easier. I doubt it. I tend to end up building one generic framework per application :-)So what could you do? One thing you should include in your thinking is that CRUD/OLTP + simple reporting is not the only thing people do, and it's probably the most crowded market.The other thing people do is analyse data. In order to analyse data they have to integrate and clean it first. It's a horribly messy affair, but what it involves is a generic database and user friendly transformation rules.I know I'm not being very specific, but I think it could useful for you to think a little more about decision support, analytics and data integration. It's what I do as well, so I'm biased.