For a long time, silence wasn't uncomfortable. It was a cocoon, and I felt completely safe inside it.
Building feature by feature, fixing small layout bugs, learning code late into the night, designing screens felt like a wild dream. The feeling of being completely wrapped up in the work felt good. In that space, nobody could judge what wasn't finished. Nobody could ask why it was taking so long, or why I’d chosen to do it at all. I was utterly and disgustingly happy in my own solitude.
I’d spent three years at a big insurance working in enterprise IT. Working with big systems, for big bosses, doing big migrations and projects. I had a degree in business, a background in UI/UX design, and experience managing software projects across teams. I knew how large organizations moved. I knew how to map out a migration for 5,000 users or rebuild an internal service portal from scratch. But configuring existing enterprise tools is quite different from opening a code editor and building a multi-module platform by yourself.
And yet in May 2025 I walked into my managers office to resign. It wasn't because I had a massive safety net or a team waiting for me. Completely the opposite. My parents are immigrants, who had spent their lives working to give me a safe, predictable path. And they were terrified (and quite angry, to be honest). I had studied in Vienna, moved to Israel, built a stable career, and then suddenly... quit? They were right to be worried.
I moved onto the living room couch and made sure to do my fair share: running household errands, keeping up with chores, and helping out wherever I could. But once the house went quiet, I’d pull out my laptop and learn React from documentation. The technical learning curve wasn't clean. Early on, I misconfigured AWS. Got hit with a surprise bill, had my card declined overnight, and woke up to discover my entire database was gone because I hadn't set up snapshot backups. I didn't panic out loud, because I couldn't bear the thought of being so naive and stupid. I simply moved everything over to Railway, rebuilt the tables, and kept writing code.
Months passed like that. But somewhere along the line, the cocoon stopped being a productive workspace and subtly turned into an escape mechanism.
Whenever the product reached a point where it was ready for real eyes, I’d find another edge case to handle. I’d tweak an animation, refine a database schema, or redesign a button state. The more I worked on an already functional system, the more I prolonged the silence. It took me months to admit the truth to myself: the problem wasn't the product, the infrastructure, or a missing feature.
I was simply afraid to show my work.
I was writing essays telling solopreneurs to step out, show their process, and let their craft be seen in the open. Yet I was sitting on a couch, terrified of following my own advice.
I started SimpleMark Studio because I’d spent years watching independent creators, designers, and consultants drown in unnecessary subscriptions. They were brilliant at their work, but they were running full businesses using a maze of Notion pages, spreadsheets, and invoicing apps. I wanted to build a single home where their strategy, projects, clients, and finances actually talked to each other.
SimpleMark is in its soft launch now. The core modules are built, the backend is running, and stepping out of the safe room to publish this makes my stomach turn a little.
Building in silence is comfortable. But at some point, the software has to leave the laptop, and the builder has to let the world see what’s inside.