When a CMS isn't a CMS

Besides from running EPiServer for some of our own websites our company has a few customers for whom we develop and maintain EPiServer sites as well. Since I've been involved in quite a few of those projects I've subscribed to the vendors newsletter. Happily for them (and in a way for us that are partners) they seem to be doing quite well, getting new customers at a constant rate. However as a developer I see one problem with this, my personal opinion is that EPiServer is not a CMS. It's a framework, toolkit and skeleton for building websites.

So what does this mean? Where it a full blown product I'd state that consultants where only needed to do specialized development, for example developing integration with some legacy back end system or providing a custom authentication provider towards the customers unique account database etc. This is not the case. Most of the work consists of developing templates since there's no GUI for that particular task. And yes I'm aware that there are third party extensions that make this possible, but I don't think that's good enough. As a developer, consultant and over all the-right-tool-for-the-job kinda guy I don't like it when a product isn't a product.