Monk Networks was orange.
The logo arrived with a little bald monk sitting inside something that looked like a network diagram. The word MONK was huge. NETWORKS sat underneath it. The whole thing had the subtlety of a construction cone.
I liked it.
Until then, the company mostly existed as email threads, spreadsheets, and an increasingly complicated plan for taking over technical operations for startups. We had talked about customers, support, software, equipment, financing, and who would do what. It was real enough to consume nights and weekends, but not real enough to point at.
The logo changed that a little.
I forwarded it around immediately. Small as it was, having something visual made the project easier to share and harder to ignore.
A name and a mark can make a half-built idea feel further along than it is. That is useful as long as you do not confuse the feeling with progress.
We still needed a product narrow enough to explain. We needed customers who would pay for it. We needed to decide whether Monk was a managed-services company with software or a software company that happened to provide services.
The visual identity solved none of that.
It did give the work a place to collect. Documents could have a name on top. A pitch could look like it belonged to an actual company. The two of us could stop saying “the new thing” every time we talked about it.
Sometimes a side project becomes a business one small artifact at a time.
This one started with a very orange monk.