A problem here is that the project is rarely described as &quot;customer needs a CMS&quot;.  If that really truly is all that&#x27;s needed, and presented as such, yes... use an off the shelf thing that has other benefits.<p>Usually there are a lot more gotchas that need to be addressed.  Maybe WP is a valid solution, with some customization, or maybe it&#x27;s not, based on a bunch of other factors the client presents (existing integration needs, skills&#x2F;experience of other staff, etc).<p>Understanding&#x2F;parsing&#x2F;coaxing requirements, and setting and managing expectations... both of those are much larger factors in someone&#x27;s success than lines of code, of speed of coding.<p>When the client reasonably comes back and says &quot;oh, and we need XYZ to happen and tied in with the CMS&quot;.  Well... you&#x27;re now on a &#x27;hosted wordpress&#x27; platform and don&#x27;t have control of anything, so the tie-ins the client needs are basically impossible (or... require 10x the amount of work compared to Bob&#x27;s solution).  These scenarios happen.  We can&#x27;t <i>always</i> predict them, but with enough experience you should be able to predict many&#x2F;most of the potential use cases (at least out a few years in the future).