01
Commitment
I take on a small number of projects and I stay with them. Your work isn't fitted around six other clients, and I'm not gone the week after it goes live.
Hesam Rad.
I help businesses grow by building them software they can use and rely on to move forward with their digital journey and I have been doing it since 2017.
Most of what I do is understanding what the problem is so I can build the right tool to fix it.
How I ended up working alone.
In my experience as an employed engineer, the software an entire business relies on is often built and maintained by a handful of people who know it end to end. In my case, I was always one of those people, responsible not just for writing the code, but for understanding the system, making decisions, and keeping it running.
Eventually, I realized I didn't need a company around me to take that responsibility seriously. I could work directly with a business, understand what it needs, and care about the software as deeply as the people who depend on it.
So I started working independently in late 2025. If you're weighing one engineer against an agency, I've written down the honest comparison, including the jobs an agency is the better answer for.
The software is only half the job.
The other half is everything around it: how I work with you, what you can see while it happens, and what you're left holding at the end.
02
Trust
You're handing over something the business depends on. One person is answerable for all of it, and when something goes wrong it gets fixed first and explained after.
03
Transparency
You always know where things stand. Progress is something you look at rather than something I report, and every decision comes with a reason in plain English.
04
Ownership
The domain, the accounts and the code are in your name from day one. Nothing runs only on my laptop, so replacing me is never a rescue operation.
Some of what I have built.
Each one was a single engineer on a single system for years. The write-ups say what the business needed, what I built, and what changed.
What a Broker Could Not Buy
A brokerage could only see what its trading platform chose to report about its traders, which was not much and not the right things. Their own analysts had worked out what they needed to watch, and the firm had rules it was enforcing by hand. This is the system that measures the first and enforces the second, sitting between the broker and its clients without either side having to change how they work.
Read the whole story
From Static to Dynamic: The Living Menu
Cafés and restaurants kept their menus on paper, so changing a price meant reprinting everything and living with whatever was on the table until the next print run. Top Menu put the menu behind a QR code on the table, and behind that, a system that made everything work flawlessly.
Read the whole story
Clients, in their own words.
I hoped we would get to work with Hesam from the day I met him. Professionalism, to me, is about how someone deals with people, how versatile they are, and how well they read a situation, and he had all of it. We brought him onto what was probably the hardest project our team had taken on, a platform built on the data sitting in our broker servers. He stayed with it, he was disciplined about it, and he was someone you could hand anything to and stop worrying about. I hope we work with him again.
After several disappointing experiences with other agencies, I met Hesam in another attempt to work on my idea. He designed the entire system architecture from the ground up and built a robust, scalable backend that powered all our front-end applications seamlessly. After five years of hard work, he turned my concept into the city’s #1 best-selling menu application.
Still deciding whether to email a stranger?
A paragraph about what you're trying to build is enough to start. I'll tell you straight whether I'm the right person for it, including the times I'm not.