What I've stopped pretending about building a consulting practice from zero in Dubai

I have stopped pretending that building a consulting practice from zero is a clean positioning exercise.

The website matters, the writing matters, and the methodology matters, but none of that replaces the uncomfortable part: you still have to put yourself in front of people before the market knows what to do with you.

When I started, I did not have some romantic expectation that the first few weeks would suddenly open a full pipeline. I just knew this was the right path forward. That sounds simple, maybe too simple, but it is the honest answer. The conviction was not that the market would answer quickly; the conviction was that this was the direction I had to keep walking in.

The part I had to stop pretending about was waiting.

If I wanted to wait for SEO, organic traffic, or ads to create the practice on their own, I would be waiting forever. A quiet website can look like discipline from the outside, but it can also become a comfortable way to avoid rejection. You can sit there, keep polishing the service page, hope the universe notices, and call that strategy.

That is not how the conversations started.

The real movement has come from cold outreach, DMs, and being proactive with people whose products I can actually understand. Not random pitching. Not the vague founder networking where everyone is trying to extract something from everyone else. The useful pattern is much more specific: find a founder, understand the product well enough to see a real issue or opportunity, then offer something useful with no expectation that it comes back.

Sometimes they reply, sometimes they do not, and sometimes the most useful thing you send disappears into silence.

That has to be fine.

The practice only works if I am comfortable giving value before the world gives anything back. It also only works if I accept that value given is not always value received, nor should it be. Some help is just help. Some observations are worth sharing because they make the product better, even if the person ghosts me, ignores me, or comes back six months later.

That is different from walking into a ProductTank room and hoping the right client appears. Product events can be useful, but they often put you around people in the same profession. A designer is not usually the person most likely to hire another product and UX consultant, especially when the work overlaps. Founders are different. They feel the product problem as a business problem, which means the conversation can start at the level where my work actually matters.

The hard part has not been one dramatic bad week; it is more ordinary than that.

The harder days are the ones where I get derailed, where too many parallel threads start pulling at the same time and the whole system starts to feel noisy. That has been the real lesson of the last year: context is finite. I have burned myself out trying to run six products at once. It was exhilarating for a while, and it also took a toll that was heavier than the output justified.

Since then, I have had to make the work simpler and more predictable. Focused product bursts, not six live obsessions at the same time. Products can be live without being worked on simultaneously. Just because I can build more does not mean I should.

What keeps me going is freedom, as cliche as that sounds.

My resume shows a committed person. I stay long-term in companies, and I usually get pulled into the change-management layer because that is where the work often ends up. Over time, that same pattern becomes the reason I want the practice: the freedom to work with whom I want, how I want, for as long as the work makes sense, and with the financial ability to carry my skills globally rather than only regionally.

There is also a work-life version of that freedom that I would not trade. The point is not to become busier under a different logo. The point is to build a practice that lets me do serious work without surrendering the life around it.

That is why the parallel product work matters too.

Outside the consulting practice, I am wrapping up the designs for Protocol, and Protocol is one of those products where the money is not the first reason it exists. If it makes money, great. If it does not, I still need it. That changes the discipline of building. You are not being seduced only by the possibility of a market; you are building something you can relate to, use, and commit to long term.

That matters more in the AI era than people admit. Product people are in love with the act of building their own software right now, and I understand why. The tools make the first version feel close. Still, the work is more complex than the first burst suggests. If there is no real attachment to the problem, no honest reason to keep caring after the novelty fades, discipline eventually collapses into burnout.

What would I tell someone three weeks into building a consulting practice from zero and thinking of stopping?

Keep pushing, but stop waiting passively. Think long term, then make the next brick useful: send the message, share the observation, give the founder something they can use today, and keep building the body of work without confusing publishing with being in the market.

The practice is not built by pretending the quiet is noble. It is built by putting useful work into the world often enough that the right people eventually have evidence to trust you.