One Developer, Ten Years, 750+ Projects

How I got here

I studied computer science at GITS under RTU in Udaipur and started building websites for local businesses while I was still a student — mostly small shops and hotels that needed a first web presence. That work taught me something that no course covers: what people will actually use. A beautifully engineered system that a shop owner finds confusing is a failed project, regardless of how good the code is.

Over the following decade the work expanded from websites into the software that runs businesses. A hotel needed a booking system that its front desk could operate during a rush. A workshop needed job cards its mechanics would fill in without being chased. A transport company needed to know where a consignment was without phoning three branches. Those problems are more interesting than any framework debate, and solving them properly is what I have spent most of my career doing.

How I work, and why

I work alone, deliberately. When you hire an agency, the person who understands your business during the sales meeting is rarely the person writing the code, and something is always lost in that handoff. Working directly with one developer means the requirement goes into the system the way you explained it, and when you call about a problem two years later, the person answering still remembers why it was built that way.

The trade-off is honest: I cannot staff a team of fifteen on a six-month deadline, and for projects of that size I will tell you so rather than take the work and struggle. What I can do is take a well-scoped project from conversation to launch without anything getting lost between departments.

Everything is fixed-price against a written scope. You approve what will be built before it is built, you watch progress on a staging link rather than in a status report, and at handover you receive the source code, the database and every credential — registered in your name, not mine. I have taken over enough abandoned projects from developers who held clients hostage to be firm about that.

What I am genuinely good at

Business software where the process is complicated and the users are not technical. Laravel applications with real data behind them. Websites that load fast and rank because they were built correctly rather than optimised afterwards. Taking over a codebase somebody else abandoned and making it stable again.

What I am not: a large-team enterprise vendor, a designer who will produce award-winning visual art, or the cheapest quote you will receive. If those are what your project needs, I will say so in the first call rather than three weeks in.