Well I think your point makes some sense, but not in all contexts.

For instance, when I am building something for $work which we are selling in some way, then I will slap a 1.0 onto it for the first release. This is because it is the first release to a $paying, non-technical audience. If we do a major upgrade at some point, we will bump the version appropriately, depending upon the "size" of the upgrade.

When I am building a module for internal use within these $work products, that may or may not get released to CPAN, I take a different approach. My "clients" for this kind of work are fellow developers, they are not a dazzled by the bright shiney number 1.0. For these modules, I start at 0.01 and I increment each version by 0.01. Why? Because I know that those numbers don't really mean that much to a developer. A developer should only care that the module works, that is has a solid set of tests, and if possible has been field tested by the author (aka - deployed in prod). I would sooner use a 0.01_a module which had +95% test coverage and had been deployed in a production environment for 6 months or more, than I would use a 3.0 module which does not meet those same criteria.