We moved from productized AI services to consulting because delivery alone does not scale, but diagnosis does. A client rarely knows their real problem going in. Build on their assumption anyway and the project turns into patchwork. A clear diagnosis before any delivery turns a one off project into something repeatable.
I went through this in my own business. In six months I went from 5,000 to 20,000 euros a month, built a team of six, and thought the model was working. Then I realized that exact growth had quietly pushed me into a dead end, and I had to question the whole model again from the ground up.
Five thousand to twenty thousand in a month, and still not stable
The first month brought in 5,000 euros, the second 20,000, and the number held steady from there. That reads like a clean win, and for a while it felt like one too. I hired four developers, an executive assistant, a copywriter and a designer, six contractors in total. Everything looked like a company that was growing properly.
What got lost along the way was closeness to the client's actual problem. The more people joined the team, the more individual advice turned into a production process. My clients had originally met me as a freelancer. Now they were dealing with a structure full of processes, handoffs and a company culture they never signed up for. The growth was real. The fit between what I had built and what my clients actually needed got smaller instead of bigger.
Why almost every project failed at the same point
Looking back, I see one pattern across almost every client project from the last few months. The client arrived with an idea of what their biggest problem was, and we built around that idea. Often it only became clear halfway through the project that this was not the real problem at all. The client could not have known otherwise, because they rarely see their own internal situation clearly enough to ask the right question in the first place.
That pushed me toward one clear conclusion. Before anything gets built, there has to be a diagnosis, as the actual first part of the work rather than a formality that comes before it. This approach changes what an offer is built on. Delivery becomes the second phase rather than the first, and that is what makes it repeatable, regardless of which industry the client happens to sit in.
The team should carry the work, not just my own capacity
When I started shifting toward consulting, one uncomfortable realization showed up fast. It felt like being a freelancer again, because too much depended on my own knowledge and my own time. That dependency was exactly what I had wanted to leave behind by building a team in the first place. A company that only runs as long as I personally have time is, to me, a well paid solo job wearing a company's clothes, and that is precisely why it does not scale.
The fix is to turn an initial phase with three to five clients into an actual method the team can later carry. I run the first engagements myself, hands on, one to one with the company. Out of that comes a repeatable approach that others can eventually deliver, while I focus on sales, recruiting and new ideas. That order matters: do it myself first, then turn it into a method, because that sequence is the real difference between a job that depends on me and a company that keeps running at every single point without me.
Who the right client is for this model
My preferred client profile is a company with 10 to 60 employees and six to seven figure annual revenue. That size fits what I actually enjoy doing, which is presenting, delegating and building team structures. Companies at this size also tend to see their own organization more clearly, and that clarity is exactly what a good diagnosis needs to work with.
At this size, one tension shows up over and over. Leadership knows clearly that they need to act on AI, but their own team hesitates or is afraid of getting it wrong. One business owner with 60 employees in his company put it to me directly: everyone knows they have to do something, but nobody knows what. That gap between knowing and acting is exactly where a real diagnosis starts.
The real takeaway: diagnose first, then the team can scale
Consulting with a clear diagnosis up front scales through a team, because my own delivery capacity stops being the ceiling. Productized packages without diagnosis hit their limit exactly where I hit mine: my own time and my own knowledge. Before any of that scaling happens, though, there is a stretch I will not skip. Gathering real experience has to come first, because scaling the wrong thing without it would mean starting over from scratch later, twice the work for nothing gained. The next step is testing this exact method with three to five companies, whether based in Dubai or in the German speaking market, before handing it over in a structured way to a larger team.