Ops Dojo was officially a Delaware company.
We had incorporation papers, a first board meeting, minutes, stock certificates, and titles. My partner would handle the business side. I would handle the technical side. At the beginning, we owned it together.
That stack of documents made the company legally real. It did not make the product clear.
The idea had already started moving away from Monk Networks and its broad managed-services pitch. We were now talking about open-source infrastructure software with paid modules, support, or a premium version around it.
That sounded more scalable. It also opened a fresh pile of questions. Which part would be free? What would a customer pay for? Were we building deployment tools, monitoring, configuration, or the whole operations stack again under a different name?
The best feedback was also the least complicated: make it do one thing well.
That sentence went into the plan because we needed to keep seeing it. Every new feature sounded essential when it was discussed by itself.
We needed that. I could see a hundred connected problems and had a strong instinct to solve all of them. The infrastructure world encouraged it because every component touched five others. A useful first product still needed a boundary.
The company plan became a living document. That was a polite way of saying we were still figuring it out.
But we had crossed a line. This was no longer only a late-night conversation between former coworkers. There was a company, an agreement, and a shared obligation to decide what came next.