Core customer use cases should be the focus of a private PaaS demo.
This sounds obvious, but too many demos focus on what the “demoer” thinks is cool, rather than what real life is like for the customer.
The customer in private PaaS tends to be very large organizations (think north of a couple thousand employees). If you’re a small five-man shop in Oregon, you’re generally going to use a public PaaS. It’s unlikely the case you’re going to need a private PaaS. The reason is that, if you’re using a private PaaS, you’re big enough that you probably have multiple data centers, servers (and custom applications that you’ve built) numbering in the hundreds or even thousands—and, if you think of that use-case, what is it that you should be expecting of a private PaaS demo?
If you can’t demonstrate this in a private PaaS demo, it’s unlikely you’re looking at something that’s been in a production environment for private PaaS
From a demo perspective, this is a big deal. You need to establish a level on confidence at a practical level that mirrors customer case studies. It becomes very apparent, in a demo, if a technology doesn’t map well to a scaled deployment. This should, therefore, act as a big cautionary red light that the solution being offered isn’t the best one for your enterprise.
These examples combine together in what I think should be expected of a good, cohesive private PaaS demo, and potential customers should demand this sort of demo of vendors. Say: “Show me, at-scale, what this would look like. What would it be like if I had 1k servers? Do you have a customer that’s running at least that many? Can you show me someone that’s doing that? How many apps are they running?”
We’ve also created a separate infographic to illustrate the key points I’ve laid out above based on our experiences working with all of our enterprise customers. Should you want to have it on-hand to reference at a time of your choosing. Thanks for reading!