Author: abhiyerra

When I started opsZero I wanted everything within code. It made it easier for me to reason about and work on, but as we grow it doesn’t make sense for us to continue using this method as it is heavily dependent on engineering resources which can be used elsewhere. Instead it makes sense to push out as much of opsZero’s stuff into no code solutions. There are a few reasons behind this:

1. No-code tools like Notion are simply amazing. With AI and Automations they simply do more than we can do ourselves. However, because of their API we can accomplish what we need to if we need to augment anything more technical.
2. As we add more people using commodity tools is much easier than using specialized tools that we have built internally. Building internally built tools becomes a liability for our team as we end up spending time building things that we can piece together instead.
3. We will be able to move much faster. Our goal is to not have a ton of custom code except for where it makes sense, which are largely integrations.
4. Lastly, the stuff we are building are from a UX standpoint not complex. We do not need to build custom tooling around that and can get away with simpler UX built using simpler tools.

What we will be doing then is pushing out almost all things to Notion as our source of truth. This will then feed to WordPress, etc. The end result of this is that System6 will be going away. Most things that need to be done will happen in Notion with code largely being scripts that are run through Github and Github Actions. The end result of this is we can increase our security posture while reducing amount of custom code we have.

I think I’ve been thinking about products wrong. I don’t think a venture should encompass everything but it does get more valuable when there is more added to it. A single site selling widget x is less useful than a website selling x, y, z. However, some people may just want widget x and don’t need y and z.

The question is how do you build ventures that can do both. If we sell x, y, z then we need to segment but what if the thing you are selling addresses different markets?

I think it may make sense to build the larger sites then figure out which features are popular and build the unbundled versions. However, I haven’t figured out if this is something I want to do. Overall, having a larger bundled site provides a lot of diversification and the customer has a feature list they can use.

Likely a better approach.

I’ve been trying to figure out what MakeProspect is as it pertains to opsZero. It is useful, but is not a part of opsZero. MakeProspect is a hobby. I was initially under the impression it would be a simple spreadsheet that I would sell but I don’t think that makes much sense. It would be much more useful as a content site.

One of the main problems that I have is everything should be easy for me, but this may not be easy for the customer. Sending an email containing job posts as an Excel is easy for me but not super useful for the customer.

In that regard I am changing the model of Studio a bit. I think the ideal model for MakeProspect and other Studio projects is to use WordPress for almost all the heavy lifting. I am good at the ideation stage but once it is up and running I’d like to spin it out as fast as possible. I do not want to necessarily work on these projects for the long term.

In that regard a hand off of the project should be straightforward:

• WordPress site that someone can modify quickly and is independent.
• Git Repo with a microservice that may power the site.
• Google Sheet containing a template making it easy for a business development person to come in and take over the project.

A Studio template should contain the following:

• Competitors. If we are building something it needs to be competing against someone. We need to have a list of the competitors that the product is going against.
• Sales Leads. We need to have a set of sales leads that we are going after.
• Marketing Locations. Setup marketing locations for where we promote.
• Persona. Who is the singular target for this product?
• KPIs. We need a KPI Dashboard that is added to the site that is only available to the admins.

Why do it this way? With $50/year WordPress ends up being exceedingly cost effective for launching and promoting a new site. By using microservices it is vastly easy to add what we need to automate the site. If we need more power we can add the bigger subscription. WordPress and a Google Sheet also makes selling super simple to sell. We can hire someone and give them both and tell them to run with it.

YerraCo treats and manages capital and looks at all investments internal and external from a financial view. Our goal is to follow in the footsteps of Koch Industries who take opportunities bets on new investments. We treat our ventures and investments as bets based on data and treat each entity we have from the perspective of private equity.

The company then is in the act of derisking investments as much as possible to optimize for returns.

To accomplish this our activities include:

• Risk Management. Understand where the risks are in our business and seek to uncover them.
• Global Macro. Understand the macro situation of the wider world and understand how those affect our businesses.
• Opportunities. We find opportunities with a bottom up approach through our businesses.
  • MakeProspect uncovers opportunities by following trends in jobs and sales.
  • opsZero uncovers trends by performing work for our customers and based on what they request.

With this we invest in the following:

• Ventures. We build businesses internally if they are asset-lite.
• Equities. We invest externally in public markets.
• Commodities. We invest in commodities based on geopolitical macro.

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.

I generally hate having to deal with interfaces and think that if I build an API then others should be able to use it with their existing tools. I have come to the realization that not doing this and focusing on consumer focused offerings is an absolute waste of time for me. It is just not our core competency and something I should not spend a lot of time around.

I want to sell an API not something that I have to build a UX around. Building a single API is better than creating a dozen bad products. We are looking to create offerings that are consistent and add value to our ecosystem and consumer apps are not a good use case for us.

However, by building API focused products we can encourage others to build on top and create content around how to do so.