One of my very favorite books is The Systems Bible. It's a fantastic blend of parody, wicked humor, sharp insight, and thought-provoking truisms about systems. The particular genius is that the "laws of systemantics" around which the book revolves apply so well across so many diverse types of systems: political systems, social systems, management systems, business systems, transport systems, people systems, security systems, taxation systems, legal systems, computer systems and so on.
I can't recommend it highly enough.
When you say "You need to design this stuff in from the very beginning" ... I disagree. I'm not sure you meant it because later on you say "design ... with a platform mindset" which is (to my mind) quite different.
I don't know of many platforms which were created, from day one, as platforms. Platforms tend to emerge from successful products. Any of the things I've ever done that approached platform-ness started out as specific solutions to specific problems which after various rounds of a-ha! moments eventually evolved into platform-like things which supported the original solutions but also an entire class of solutions to similar problems.
If you start by trying to create a platform, you will likely fail. On the other hand, if in the course of building your product and iterating it into what customers actually want, thus making it wildly successful - if in the course of doing that you are "designing with a platform mindset", then you have a fighting chance of making the next evolutionary leap - extracting and then abstracting the platform from the product.
He's right, of course. And what else would you expect of one of the smartest systems guys around? My rhetoric went too far, and in fact his counter-argument is a simple analogue of laws number 15 and 16. So there's that.
I think the broader point remains, though: the best external platforms are built on top of solid internal platforms—and you'll struggle to deliver the former without first developing the latter.