Everything can be automated.
Except the one who automates.
Field notes from real builds, for the engineer who intends to stay irreplaceable.
New writing reaches the newsletter first.
Field notes from real builds, for the engineer who intends to stay irreplaceable.
New writing reaches the newsletter first.
About
I build systems that run without me. Four are in production right now, with real users and real money moving through them. Most of the time, nobody is watching them work. Not even me.
It didn't start there. In 2019 I could barely make a script do one thing. So I built the next thing before I felt ready, shipped it, and let what broke teach me. Then I did it again. Scripts became apps. Apps became the systems under them. Systems became models. Models became software that runs itself. Same move every time, one step higher. That path led to Vervelio, the studio I co-founded to build and ship its own software.
The code is rarely the hard part. The judgment is. An agent working while I sleep is running decisions I already made once, well enough that they hold without me watching. A system is a cast of its maker's mind. I try to build mine to be trusted with real consequences, and I stay accountable for what they do while the room is empty.
At a glance
Frequently asked
Sarthak Nimbalkar is an independent software engineer and the co-founder of Vervelio. He builds autonomous AI systems end to end, from the data layer and the model to the infrastructure and the interface. He works remotely and has been shipping software since 2019.
He builds agentic AI and multi-agent systems that can be trusted with real users and real money, along with the control layer that keeps them accountable: cost ceilings, rate limiting, audit trails, approval gates, and human-in-the-loop review. Every product shipped under Vervelio is built by him, including NidaMind, which surfaces product ideas worth building from real public conversations; Dev Djinn, which maps scattered development work into one searchable record; The Woof Back, an automated content and client-acquisition system; and DoorYard, same-day booking for home-services crews.
Whichever the problem deserves. He treats the stack as interchangeable rather than an identity, and picks the language, framework, and infrastructure that fit each system, from local-first and self-hosted setups to full-stack product engineering across the whole database-to-interface path.
He is open to technical co-founder conversations, hard problems in autonomous systems, and work where one person owning the entire stack is an advantage. Reach him on LinkedIn or read his writing at sarthaknimbalkar.in.