The Long Road to Doing What I Was Always Meant to Do

I have been around computers my whole life. Not in the way people say it now, where everyone has a phone and a laptop. I mean I was the kid who, at eight years old, was fascinated by the simple act of turning a machine on and watching it come alive. It started with games, like it does for most kids, but somewhere along the way it became something else. I started wanting to know how things worked, not just how to use them.

By the time I was fifteen, I had my own website. This was back in Dubai, and websites were mostly static pages at the time. Mine was more of a blog than anything else, but even then I was writing bits of code, figuring things out, putting something out there on the internet that was mine. I did not think of it as a career path. Back then, working with computers was not seen the way it is now. It was a hobby. Something you did on the side. If you wanted a serious career, you studied medicine or engineering or business. So that is what I told myself I would do.

I went to university and enrolled in biomedical science. It lasted about as long as you might expect for someone who spent every free moment behind a screen. I could memorise the material, I was not bad at it, but it did not interest me. Meanwhile, I was deep into cryptocurrency, running my own mining rig, constantly learning about systems and networks and how digital infrastructure actually works.

My friends kept asking me the same question: why are you studying biomedical science when you are always behind the computer? Why not study something related to what you actually do? It was a fair question. I did not have a good answer.

Eventually I stopped trying to have one. I went back to Iran, enrolled in software engineering, and something clicked. For the first time, what I was studying matched what I actually wanted to do. It felt like I had found the right lane.

The thing I have always wanted to do

From the very beginning, I have always felt like I was here to build something. Not just write code, but build something real. Something that starts as a line of code and grows into ten lines, then a hundred, then thousands, and eventually becomes something people actually use. That idea, of creating something from nothing, has been what drives me.

While studying, I worked across different areas of the field. Networking, setting up systems for companies. Front-end, back-end, databases, DevOps. I tried to learn everything, and at some point I realised that was impossible. Each field has its own depth, its own lifetime of learning. You cannot master all of them. But you can understand enough to know how the pieces fit together, and that understanding turned out to be more valuable than expertise in any single area.

Over time, I found myself drawn more toward the marketing side. Website design, SEO, keyword research, strategy. It was a different kind of problem-solving, and I enjoyed it. I had a full-time job doing this kind of work, and it was good. But the urge to build never went away.

When AI changed the equation

When AI and large language models started becoming genuinely useful, something shifted. The feeling I had always carried, that I was supposed to be building things, came back stronger than before. The tools had changed. What used to take a team and months of work could now be approached differently. Not easily, not without effort, but the barrier between having an idea and being able to execute it had dropped significantly.

I started small. Chrome extensions. Full websites instead of relying on WordPress templates. If there was something I needed to do on my computer and the process was tedious, I would build a tool to handle it. Each project taught me something, and each one made the next one easier.

Where Havnwright came from

The idea that eventually became Havnwright started in 2023. I have always been interested in real estate, construction, and renovation. I had been involved in renovation projects with my family, both in Iran and in Dubai, and every time the same problems came up.

You never had access to the information you were supposed to have. The head contractor would tell you "it costs this much, you pay this much, you have no other option." You were committed before you understood what you were committed to. If you wanted to get more involved in the process, to actually understand the decisions being made about your own property, the information simply was not there.

I kept seeing these gaps. Homeowners locked out of their own renovation process. Contractors with no professional tools to manage their work. The whole industry running on phone calls, spreadsheets, and trust that you hope is not misplaced.

So I decided to do something about it. The project started under a different name, AI Refurb, before becoming what it is now. Havnwright is built to solve the problems I experienced first-hand: giving homeowners the information and tools they need to manage their renovation properly, and giving contractors professional tools to run their business.

Where I am now

Today I work on this solo. Havnwright has a web platform with dedicated dashboards for homeowners, contractors, and administrators. There is a companion mobile app for contractors on both iOS and Android. I am also building Publishora, a marketing platform for solo founders, and a knowledge graph system that gives AI agents persistent memory across sessions.

Everything you see on these projects, from the architecture to the deployment to the marketing, is built by one person. Not because I think that is the only way to do it, but because right now, with the tools available, it is possible. And I would rather build it properly myself than hand it off before I fully understand every part of it.

The long-term vision for Havnwright goes beyond renovation. I see it becoming an ecosystem that covers all aspects of property, from renovation and construction to maintenance, buying, and selling. A system where people have the information they need to make real decisions about their most important investment.

I am not writing this blog as an expert. I am writing it as someone who is in the middle of building. Every post here is something I have experienced, a problem I ran into, a decision I had to make, a lesson I learned the hard way. If any of it helps someone else who is trying to build something of their own, then it is worth sharing.

---

This is the first in a series of posts about building products as a solo founder. If you are interested in the technical side, the business side, or just the honest reality of doing this alone, there is more coming.