"A single responsive codebase really forces a lot of tough content questions to be asked and allows a simpler path for those problems to be solved." Sounds lik

"A single responsive codebase really forces a lot of tough content questions to be asked and allows a simpler path for those problems to be solved." Sounds like approaching the problem from the wrong direction. The primary ingredient of a site is the content. The content informs the design. The moment the design forces the content is the moment the design fails to be a design, and probably becomes decoration. If the content is conducive to a responsive design, by all means consider a responsive design. But if the content isn't conducive, don't force it into a responsive design.