01
A product built from nothing
You have a business and an idea, and nothing built yet. I turn it into something your customers can sign up to and use: the website or app they see, the accounts, the payments, and the admin screens you run it from.
Available for new projects
Independent software engineer
Your business has a back office. Somebody has to build it.
Not an agency, not a template, not a platform you rent. One engineer who builds the thing, and is still reachable when it needs changing.
Not sure which? Describe it in a paragraph and I will tell you.
8+
Years building software
Free
Written plan to keep
2–6
Weeks, plan to launch
1 day
To hear back from me
Most of what an agency charges for is the agency.
An account manager briefing a project manager briefing a developer — layers whose job is coordinating the other layers, billed to you. You get one person for the part that has to be correct and stay correct: the system, the data, the releases, and the day-to-day of keeping it up. Nothing falls between three suppliers, because there are not three suppliers.
02
Pages that load in under a second
If your site or app has got slow as it has grown, that is usually a matter of weeks to fix, not months. Faster pages mean fewer people give up before they buy.
03
Software nobody is looking after
The developer who built it has gone, or the agency moved on. I take it over, make it safe to change again, and write down how it works — so you are never in this position twice.
04
Software that keeps working
Automatic checks, a release process that takes a minute, and documentation written in plain English. So a change made on a Friday afternoon does not take the business down on Saturday.
Start with a call. Keep the plan either way.
Thirty minutes to understand your business and what you are trying to build. You get back a written plan: what I would build, in what order, what it would cost, and what I think could go wrong.
It is yours to keep — including to take to another developer. And if I am not the right person for the job, I will tell you on that call rather than three weeks in.
There is a person behind this.
Eight years building web software, five of them looking after one system for the same client. A literary background as well as an engineering one, and a master's in English literature in progress — which turns out to matter, because most of this job is explaining a complicated thing clearly.
What people who have worked with me say.
I can confidently say that Hesam is one of the most disciplined person I have ever had the opportunity to work with. His leadership skills are excellent and he always ensures that his team is performing at its best. His commitment to delivering high-quality results shows in every project he handles. If you're looking for a Back-end development role, I highly recommend Hesam who makes a positive impact on any team he joins.
I had the privilege of working alongside Hesam from my very first day as an intern, and I can confidently say he played a pivotal role in shaping my growth as a developer. As a backend developer, Hesam combines deep technical expertise with a rare quality—genuine patience in mentoring others. What sets Hesam apart isn't just his technical skill; it's his willingness to stop what he's doing to explain a concept, debug an issue together, or share the why behind a decision—not just the how. Many of the habits and best practices I rely on today were shaped by his guidance. Beyond his technical abilities, Hesam is the kind of teammate every engineering team needs: reliable, collaborative, and genuinely invested in the success of those around him. Any team would be lucky to have him.
The most disciplined coworker I’ve ever had. Hesam is extremely focused and giving up is not an option for him. He’s actually the man who gets things done no matter what it takes. His enthusiasm to learn new things is unbelievable. He’s the one you can get inspired by.
After working with Hesam for about 1 year, I can confidently say that you will have a compassionate friend and strong character in your team.
Tell me what you are trying to build.
A paragraph is enough. You will get an honest answer about whether I am the right person for it, including the times when I am not.