A customer, a global law firm, was looking to move existing data into a new data center, so they had strong deadline. They had a very diverse set of technologies (Dell, HP, Cisco, VMware, Oracle, NetApp, etc.), and couldn't control costs or procedures when a new business requirement came up.
I performed a gap analysis to determine what building block of technologies were needed, and the opportunity was right for the FlexPod solution infrastructure. You can use FlexPod to standardize the system and to have just a single control center and one vendor to work with.
Solutions that we put up on FlexPod were best-practices configurations - SharePoint, Exchange, SQL, etc. and they can all be downloaded from the FlexPod portal. It reduces the risk of incompatibility and down-time from making new configurations, profiles, and templates.
The other key reason for choosing it was the long-term vision of agile, automated infrastructure, giving private-cloud solution based on FlexPod. The struggle was their speed of deployment (contacting different vendors that took time through the internal authorization procedure), and FlexPod sped up this process by 50-60%.
It's a great solution for enterprise-level customers, but it needs something smaller, maybe hyper-converged for software-heavy, smaller infrastructures that work in the cloud.
The nature of running FlexPod in its pre-defined infrastructure is that it's not pre-configured. It comes in bits that you have to put in yourselves. Clients want something that meets their requirements that you can just plug-and-play, and this is especially true for cost-sensitive and less-knowledgable clients.
My advice would be to make sure everything works per your business justification. How does it fit into your long-term strategy? For example, if you already have lots of investments in other vendors, you're going to have to rip them all out to use FlexPod. Take what you've got, and see how it matches up against business goals. See where the gaps are that need to be filled - maybe FlexPod works for your and maybe it doesn't. Also, you should assess the capital costs and ask how it'll fit into existing datacenter architecture