How I work

How I think about a project, and how we would work together.

How I think about a project

Most complexity does not come from the technology. It comes from a process that grew organically over years, a product with too many variables to explain over the phone, or a task that a skilled person still has to do by hand every single day. My work starts by understanding that complexity properly, not by jumping straight to a favourite tool or technology.

  • I start with the user, not the feature list. Every project begins by mapping what the person on the other end is actually trying to accomplish, and where the current process breaks down for them.
  • I design the experience before I write a line of code, so the interface reflects a clear decision, not a series of technical shortcuts.
  • I pick the technology that fits the problem, not the other way round. Some problems need real time 3D so people can see what they are choosing. Others need a simple, fast web form. Others need artificial intelligence to handle something that would otherwise take hours by hand. I stay genuinely useful across all of these instead of pushing every project toward the same tool.
  • I build with modern, current technology, so what I deliver performs well, ages well, and is genuinely pleasant to use, not just functional.
  • I build fast, working prototypes early, so decisions get made by looking at something real rather than debating a document.

How we would work together

1. You describe the problem

Send me a short message about the task, process, or product you want to simplify. I am as interested in the problem itself as in the solution, so the more context you give me, the better.

2. I send a written proposal

I reply with a clear scope, price, and timeline in writing, along with my honest read on the best way to approach the problem. You review it and confirm when you are ready to proceed.

3. I design, then I build

I map the experience first, then build it myself using whichever technology genuinely fits, bringing in artificial intelligence where it helps. Once I have something worth looking at, I send it over on WhatsApp and we go back and forth quickly from there.

4. You approve, and it goes live

Once you are happy with the result, I deploy it and hand over everything: source files, credentials, and documentation. It is yours, with no ongoing dependency on me unless you want to keep working together.

I am not big on scheduled meetings, and I do not default to a call for every update. I work asynchronously and keep in regular contact by WhatsApp, which lets us move quickly: I send progress or a working prototype as soon as there is something real to react to, and we go back and forth on it right there, often faster than a meeting would allow. This also means communication naturally works across timezones instead of fighting them. If something genuinely needs a live conversation, a video call is always available, but it is the exception, not the default.

Common questions

Everything people usually want to know before sending a brief.

Do you work solo, or do you have a team?

Solo, always. I design and build every project myself, from the first user flow to final deployment. No subcontractors and no handoffs between design and development. The person who understood your problem is the same person who solves it.

Where are you based, and can you work with clients in my timezone?

I am moving toward a fully location independent lifestyle, working remotely as a digital nomad, which means I am used to adjusting my working hours to overlap with clients in different timezones. I am not big on scheduled calls, and I do not need a meeting to give or receive an update. I work asynchronously and stay in regular contact by WhatsApp, sending progress as soon as there is something real to look at and going back and forth quickly from there. This removes most of the friction that usually comes with timezone differences, and I am always upfront about realistic response times before we start working together.

What kind of problems do you usually get brought in for?

Almost always something that is complex to explain or complex to use: a product with too many configuration options, a process that lives across spreadsheets and habit, a task that needs training that paper cannot properly deliver. If your problem is complicated and you are not sure how to make it simple, that is exactly the kind of project I enjoy most.

Do you always use artificial intelligence, or 3D, in a project?

No. I am deliberately polyvalent, and I choose whichever technology actually fits the problem rather than steering every project toward the same tool. Some problems are best solved with interactive 3D so people can see what they are choosing. Others need artificial intelligence to remove a manual step. Others just need a clean, fast, well designed website or app. I will recommend whichever combination genuinely solves your problem, and explain why.

Do you take over or extend existing projects, or only build new ones?

My focus is on new builds, from a fresh brief through to a finished product. This lets me guarantee the quality of both the experience and the underlying code, since I am not working around decisions made by someone else on a system I cannot fully see. If you have an existing project you would like to discuss, get in touch and I will be honest about whether it is a good fit.

How long does a typical project take?

It depends entirely on scope and complexity. A focused website can go live within days. A configurator or AI integration typically takes two to four weeks depending on how many variables are involved. Larger spatial or VR projects are scoped individually after a written brief. In every case, you will usually see a clickable prototype within the first week.

Do I own everything at the end of the project?

Yes. You receive the full source files, credentials, and documentation. Nothing is built on a platform that requires an ongoing subscription to me or to a third party unless that is genuinely the best tool for your specific problem, in which case I will explain exactly why before we start. Any developer in the world can pick up the files and continue the work if needed.

How does payment work?

For most projects, I ask for a portion of the total price upfront to begin work, with the remainder due on delivery, after you have seen and approved the final result. You are never asked to pay the full amount before seeing anything, and I share progress along the way so there are no surprises at the end.

What if my project does not fit neatly into one of your listed services?

That is completely normal, and often where the most interesting work happens. Describe the problem you are trying to solve and I will tell you honestly whether it is something I can help with, roughly what it would involve, and what it is likely to cost, before you commit to anything.

Ready to describe your problem?

Send me a short message. I read every message personally and reply within one business day.

Start a project