Kubernetes, Microservices, Compliance

As I look at our current Solutions on our website with DevOps, AI+DataOps, Cost Optimization, Modernization, and Compliance & Security it makes me wonder what we are pitching. It seems like we are trying to do too many things and I think a potential customer would also be confused. Each of those things is different with a Venn diagram that connects loosely.

I think we need a clear, crisp pitch. We do Kubernetes, Microservices and Compliance. I think this will make sales vastly easier to do and will allow us to be better known with our partners. We are already doing the pitch so we are not adding anything new and are really just bringing our strengths.

Some reasons I think we should simplify to these three:

• The existing solutions that we have are backward looking. We seem to say we do a bunch of things that are now common place and are done by others. The solutions just feel like an old company instead of a forward leader we want the brand to represent.
• DevOps and Cost Optimization are redundant if we just say we do Kubernetes. Kubernetes entails both cost optimization and DevOps for us. They should not be separate as our goal now is to have one Kubernetes cluster per AWS account. It no longer serves us to have cost optimization be a separate function but a part of our Kubernetes offering.
• Modernization and DataOps+AI are also redundant. We can just label them as Microservices with a tag line of building with Data and AI. Modernization is too big and doesn’t differentiate us in any way. We should just consolidate them. We provide and can build microservices.
• Compliance. We should not say Compliance and Security just compliance. Security is pretty vast and trying to incorporate all of it would be a crap shoot. We should narrow our focus to just Compliance as it differentiates us from others in that it focuses us on the Cloud infrastructure. We do not want to do MDM and device management as that is not our strength.

This is why I think Kubernetes, Microservices, Compliance should be our pitch.

• It is easy to remember. We are the Kubernetes and Microservices people.
• It is forward looking. Kubernetes is stable and legacy infrastructure will move to it. It future proofs us by building out moat around a new capability that others don’t have.
• Modernization was the move from onprem to the Cloud. Microservices are what happens when you are on the Cloud and want to make your apps more efficient. While we may do the onprem to Cloud work we should frame it from a future looking term of microservices as opposed to the early cloud migration term of modernization.
• It fits with our Platform vision more clearly. Kubernetes, Microservices and Compliance fits a lot clearly with our cross sharing of resources that we want to build with the Platform.
• Makes it easier to hire people who know what they are selling. By being focused we can create a common messaging that we can use to sell. The current units is pretty large.
• It helps us figure out who we need to hire for engineering. By doing too many things it makes it much harder to figure out who to hire. By focusing on Kubernetes, Microservices and Compliance our hiring becomes a lot clearer.