When I started working for myself, there was no clear plan and no complete picture of what I was after. The road was not laid out the way it can look today, when people see only the results. I had no finished roadmap, and not enough experience to act with the confidence of the leaders I watched from a distance. But something inside me would not let go: a real desire to build something of value, to leave a real mark, and to live an experience that felt like me and the way I see things. The beginning was very simple, with some confusion, a lot of curiosity, and wide room for trial and error. I searched more than I knew and learned more than I understood, trying to grasp working life from the inside before trying to shape it my own way. In those days I repeated words I loved and believed in: passion, perseverance, initiative, development, the desire for change. What I did not realize then was that those words are not enough on their own. Real passion is not just excitement at the start; it is the ability to keep going when the road becomes exhausting. Perseverance is not just refusing to quit; it is taking responsibility for your decisions even when the consequences are harsh. Initiative is not a nice idea you talk about; it is a real risk that can cost you your time, your comfort, and sometimes your entire personal stability. Over time I discovered that building anything lasting does not come from talent alone or enthusiasm alone. It comes from a long series of hard decisions, sometimes painful choices, and lessons you do not learn from books but from real contact with life, people, and work. With every stage I went through, the way I thought changed. Things I thought were simple turned out to be very complex, and things I thought were complex turned out to rest on honesty, intention, and clarity. Over the years, this journey became a long film strip of memories, and every stop on it was more than a passing experience. Each was a lesson that reshaped my character and the way I see people, teams, leadership, and success itself.

Beginnings: When Passion Becomes a Path, from Spontaneity to Professionalism

The first of those stops was the moment I discovered ERPNext. Even today, I don't consider it a passing professional coincidence. It was a real turning point in how I see work, management, and technology together. To me it was never just software or a system for running companies. It was a whole idea that felt like me and the way I had always thought: every part of the organization connected, decisions built on real data, and management shifting from late reactions to clear, proactive vision. At that time I was working in senior finance at a large industrial group in Saudi Arabia. The volume of operations and daily detail was enormous, which let me see firsthand the chaos that traditional systems can create, and the difference smart systems can make when they are implemented properly. When I began implementing ERPNext at that facility in Saudi Arabia, I didn't know that what I was doing was called implementation. I didn't know the details of the software-company world or the meaning of the terms that later became part of my day. I was moving on a simple, honest drive: to apply what I believed in the way I saw as right. So I treated the system as an open space for ideas, not as a program with rigid limits. Every idea in my head, I tried to find a place for in the system. Every problem I saw in daily operations, I looked for a real solution to. Every professional vision I aspired to, I fought to see become something people could actually use. Sometimes I spent very long hours thinking, not because anyone asked me to, but because it felt like me and fed my professional curiosity and passion. For the first time, I felt there was something that brought together management thinking, financial analysis, technology, and the ability to build real solutions that affect people and companies. Perhaps that is why my relationship with ERPNext was different. I never treated it as a product I offered to people, but as a whole journey that changed how I think and my professional life. Then came the turning point, when I returned from Saudi Arabia to settle in Egypt, and a simpler, more honest stage began. There was no company in the usual sense, no marketing plan, no branding, not even a clear understanding of what "Sales" or "Business Development" meant. There was only a deep conviction that this system could change how companies are run, and that if people understood it properly, they would love it as much as I did. So I started talking about it with everyone I met, with no calculations, no clear plan, and no name for what I was doing. I talked to a friend, to a neighbor, to the owner of a restaurant where I was sitting, and sometimes to people I didn't know at all. I wasn't selling; I was simply convinced. I spoke with the same enthusiasm every time, as if describing something I had discovered and wanted others to see. Over time, I noticed that this simple talking was turning into real opportunities. Opportunities became customers, customers became projects, and projects became an organization taking shape step by step. That is when I understood something important: some big beginnings don't start with huge plans. They start with a very sincere conviction, and a person who believes in what they do so much that they talk about it with complete spontaneity, before it later becomes professionalism, responsibility, and a complete organization.

Leadership as I Never Imagined It

As this organization began to form, and the idea moved from individual efforts and small attempts to real responsibility, I started to see things from a completely different angle, one I could not see when I looked at business owners and managers from the outside. I used to think a company's leader was someone who sits far from the details, watches the results, makes a few decisions, and lets things run naturally around them. I imagined that reaching the position of business owner meant more comfort, more freedom with time, and that most of the real effort fell on the team. But the reality I lived was completely different, and far deeper than I had imagined. I discovered that the leader is often the person who works the most in the whole system, not just with their hands but with their mind, all the time. Even when they look calm on the outside, they are full of thought on the inside: about the future, risks, decisions, strategy, people, and the direction the company should take a year, two years, or five years from now. Leadership is not just managing tasks. It is managing worry itself, a responsible worry that forces you every day to ask yourself: Are we heading in the right direction? Is this the right decision? Is this person right for this stage? Will what we do today protect us tomorrow, or hurt us later? Over time I realized the hardest part of leadership is not the pressure of work but the pressure of decisions, because a decision can affect people's lives, the future of an entire team, and years of effort. That is when I understood why some decisions leaders make look cold or decisive from the outside, when in reality they are the result of long hours of thinking and inner struggle. I also realized that a leader's real work does not end when office hours end. There are no complete vacations in the true sense, and no time to disconnect entirely. Even when you are sitting with your family or trying to rest, part of your mind keeps working in the background: a problem that needs a solution, an employee who needs guidance, a customer you must keep, or a decision whose delay you fear could be costly. Work doesn't leave you, because it is no longer just a job. It has become part of your identity and your responsibility to those who work with you and trust you. Sometimes I felt I was living two states at once: one person trying to build their dream, and another carrying on their shoulders the responsibility of keeping that dream from collapsing. Over time I came to understand that real leadership is not giving orders, holding authority, or even the ability to make decisions alone. Real leadership is staying mentally and emotionally present at all times, bearing the consequences of your decisions, and standing firm even in moments of exhaustion, doubt, or fear. I realized that leadership is not a role a person plays inside a company, but a continuous state of awareness and commitment, an inner dialogue that never stops between mind and responsibility, ambition and fear, hope and doubt.

The first of those stops was the moment I discovered ERPNext

Partnerships: Between Intention and Reality

As responsibility grew and the work moved from scattered projects to an organization trying to find its real place in the market, I began to feel that the road no longer suited a one-person show or a tiny team. I started looking for support, for partners, for people we could grow with and carry this journey together. I believed then, and part of me still believes, that partnership in its true sense is not just dividing tasks or splitting financial returns. I saw it as something far deeper. Partnership means complementing each other, because no one can be complete alone, no matter how much skill or knowledge they have. I thought that having someone who shares your dream could make the road shorter, lighter, and more stable. But over time I found that partnerships are not as easy as they look from the outside. They may be among the experiences that most reveal the truth about people, and about yourself. I also found that sometimes, within your own team, you meet someone you feel more for than a manager-employee relationship. You feel they are close to the spirit of the big project you carry in your heart. You see them move with the same enthusiasm you do, worry the way you worry, celebrate success as if it were their own, and hurt over problems as if they belonged to them alone. They run beside you, sometimes understand you without a word, and read what is in your head from a glance or a situation. You feel they resemble you in dream, in way of thinking, and in the drive to arrive. For that reason I sometimes looked at certain people on the team not as employees but as professional children I was investing in. People in whom you see an extension of what you believe, whose success feels like part of your own, and whom you want to see in even better places than where you stand. Perhaps that is why I became convinced that real partnership is sometimes not written in contracts. It is built in everyday situations, in honesty, and in loyalty to the idea itself. On the other side, I saw a completely different kind of partnership: partnerships based only on effort, with no clear or balanced investment. There is no real valuation of time, no clear understanding of value, no precise definition of responsibilities, and not even real agreement on what success means. Each side sees things from its own angle, and each person measures their effort their own way. That is when problems begin to appear quietly, and teamwork gradually turns into bookkeeping instead of a single team spirit. Each side starts to feel they give more than they get, that they carry the load alone, or that their effort is not appreciated enough. Over time the partnership turns from a space for building into a space for draining. I became convinced that partnerships that are not built on real clarity, do not rest on fairness in evaluation, and have no mutual investment of time, money, or responsibility are usually partnerships destined to end, however strong they look at first, because in the end they serve one side's interest, not the organization's or the team's. Among the hardest things I faced was that some people entered these relationships with a mindset of taking advantage, while I entered them with a mindset of building. I was looking for an organization that grows with everyone, while some were looking only for a position inside it. That is when I saw clearly how different intentions can change the whole shape of a relationship. Even so, something always saved me: the sincerity of my intention, even when I chose wrongly, over-trusted, or was slow to see the facts. Even today I believe a sincere intention may not stop you from stumbling, but it keeps you from falling completely. And it lets a person come out of experiences with deeper expertise and a more mature understanding of people, teams, and true partnership.

Between Knowledge and Misplaced Admiration for People

Through all those experiences, all the attempts, ups and downs, and challenges, one thing inside me never changed: my real belief in the value of knowledge. I believed then, and still believe, that any organization that wants to truly grow cannot rely only on enthusiasm, effort, or relationships. It needs knowledge, understanding, and people able to keep developing and learning. The further I went in my journey, the more I found the world is much bigger than I imagined, and that real professionalism is tied not only to practical experience but also to how you think, your ability to reach the right information, and to understand quickly what is happening around you. I saw that a person who can get to information directly and has modern communication tools can move much faster than others. I admit I felt I had gaps in some of these areas. Sometimes I felt I had practical experience and good vision, but there were other things I needed to learn or complete. Because by nature I like to surround myself with people better than me in certain areas, I thought about bringing in talent that had what I lacked: people with stronger language skills, broader academic backgrounds, major professional certifications, or a way of speaking and a presence that made them look more professional. The intention was right. I wanted to build a team stronger than me, not a team that just revolves around me. I believed a real leader is not someone who fears having strong people around, but someone who seeks them. The problem was not the idea itself but how I carried it out. Sometimes I chose based on impression or admiration, not clear professional criteria. I was sometimes dazzled by the way someone spoke, their high confidence, their certificates, their language, or their strong presence in front of people. And I imagined all of that necessarily meant a real ability to build, work, and lead. But over time I found that some people may have an excellent professional image yet be very far from the real world of work. A person may have a lot of information but no passion. They may have strong language but no team spirit. They may have big certificates but not be able to bear the pressure of real building. That is when I began to understand an important difference: knowledge is one thing, and the ability to turn knowledge into real impact is something else entirely. I also realized that some personalities are very good at talking about success but are not as good once they enter a real building journey full of pressure, challenges, and instability. This kind of mistake cost me a lot: time, trust, and decisions that could have been better had I been calmer and more objective in my evaluation. In return, this stage taught me a very important lesson: being dazzled by people can be among the most dangerous things for any leader, because when you are dazzled by someone you may temporarily stop seeing the small details that reveal who they really are. Over time I learned to tell the brilliant person from the real one, and the person who is good at appearing from the one who can build something with you that deserves to last.

Between Strategy and Execution

With all these challenges, and as responsibilities expanded gradually, I found myself in a constant struggle between two very different levels, both of which demanded me all the time. The first is thinking, vision, and planning: the level where you try to see the big picture and think about the future, the company's direction, what the organization will look like in years, and the decisions the next stage should be built on. I always loved this side by nature. I love thinking, analyzing, building ideas, drawing scenarios, and looking at things more broadly than the task at hand. On the other side was a completely different level: daily execution, small details, sudden problems, and direct challenges that don't wait. That is where I started to discover one of the hardest equations in any building journey: as a leader you may know exactly where you want to go, but daily reality keeps pulling you away from that direction. Often I had to go down to the ground of execution myself. I would get into the fine details, battle alongside the team, and follow up on things that should already have been stable. Sometimes I felt I was turning from someone thinking about building a system into someone just trying to stop problems from exploding day after day. Every time I went down to that level of detail, I felt I was a step further from the bigger picture I was trying to build. It was as if my mind were split between two wars: the war to keep today stable and the war to build tomorrow. The real problem was that being drained by daily details makes you, over time, less capable of calm strategic thinking. Decisions start becoming reactions instead of calculated steps, and your time gradually becomes a space for firefighting instead of building something that prevents fires in the first place. So sometimes I felt I was going around in a closed circle. I solve one problem and another appears. I fix one fault and a new one shows up. I try to secure one thing and others move out of place. Then I come back to the same point. That feeling was very tiring mentally and psychologically, because you pour in huge effort but the feeling of real progress is not the same size as that effort. That is when I started to realize something important: the greatest danger to any organization in its growth stage is not too much work but the absence of balance between thinking and execution. Execution without vision makes you move a lot without clear direction. And vision without real ability to execute stays just nice ideas. Over time I became convinced that the real leader's role is not to do everything themselves, nor to withdraw completely from execution. It is to know when to go down into details and when to step back to see the whole picture, and to build a team, a system, and clear processes that let them think about the future instead of staying a prisoner of the present. Perhaps that is exactly why I came to understand that building a system matters far more than just solving daily problems. You might succeed in solving a hundred problems through personal effort, but you will only build a real organization when you build a way that stops those problems from recurring in the first place.

When the Lineup Changes, the Results Change

All of these accumulations, everything that came before, and everything left behind by partnerships, choices, and daily challenges led me finally to a hard but decisive moment: reshaping the team. This moment in particular was not an ordinary management decision. It was not just a performance review or swapping names in an org chart. It was a real confrontation with myself before it was a confrontation with others. Reshaping a team means asking yourself very hard questions: Are the people here today right for the next stage? Does the energy in the team help growth or consume it? Are we moving as one team, or is each person moving by their own logic? Is there real harmony, or just a temporary presence under one roof? And is my attachment to some people due to real conviction about them, or because my feelings prevent me from making the right decision? Over time I saw the truth more clearly: not every person is right for every stage. Someone may be good at one stage but unable to keep up with another. They may be a kind, respectful person, but their ambition, way of thinking, or level of commitment doesn't match the speed at which the organization is trying to move. This does not mean belittling anyone, denying what they contributed, or treating people harshly or arrogantly. It simply means that each stage has its own people, requirements, and way. But the hardest thing about these decisions was that they were not about people I didn't value. On the contrary, I valued and respected them. Sometimes we were talking about people who shared parts of the journey with me, with whom I lived moments of fatigue, attempts, and beginnings, and to whom I gave my time, energy, attention, and sometimes my heart. By nature I like to embrace people, and I always leaned toward patience in teaching. I saw that a person may start with modest abilities, but with support, guidance, and care, may discover themselves and become a completely different version. So I gave many chances, sometimes more than I should have. I told myself maybe the person just needs someone to believe in them, to take their hand, or to give them room to learn, make mistakes, and mature. It bothered me less that experience was lacking than that desire was lacking, because skill can be learned, but real drive can't be forced into being. Still, I continued the road with some people out of hope, hoping they would discover themselves, feel the value of the opportunity, or become another version of themselves. But among the hardest things I faced was that some people, despite all the patience, support, and backing, denied any favor, stand, or opportunity they got through me, at least in my perception, and perhaps I was wrong. Sometimes I discovered long afterward that the problem was not only lack of experience but the absence of basics that are not just about skill: commitment, appreciation, honesty, professionalism, and a real desire to grow. What probably hurt most was not that they didn't succeed the way I wished, but that some treated everything given to them as ordinary and worthless. By nature I never like the idea of reproaching anyone or reminding them of what I did for them, but I also believe appreciation and loyalty are among the simplest things that preserve human and professional relationships. A person may forget money and details, but it is hard to forget who stood beside them sincerely: "And do not forget graciousness between you." So sometimes I felt distress, not because of losing the people themselves, but because I felt I may have misjudged some choices. Over time, though, I became calmer in understanding these things. I realized this is very common in life and work. Not everyone you give a chance to will value it, not everyone you support will stay loyal, and not everyone you start the road with will finish it with you. That doesn't mean you stop supporting people or close your heart completely. It means you learn to balance heart and mind: to give, but with awareness; to support, but with clearer standards; to embrace, but without letting embracing turn into holding the organization back or being unfair to the rest of the team. With all these experiences, I began to see the team as one body. If one part is tired or out of step with the overall movement, the whole body is affected. So the decision, for me, was not about cutting anyone's livelihood, as some might think, but an attempt to protect the rest of the body: to protect the people who truly want to grow, to protect the energies that still believe in the goal, and to protect the organization itself from losing its soul through hesitation or politeness. And I admit I was late with some of these decisions. I was late because I saw the human side before the professional one. I was late because I kept looking for another chance to fix things. And I was late because I thought support alone was enough to create belonging. But the truth I learned is that support cannot create drive out of nothing. You can help someone who wants to help themselves, but you can't dream in their place. You can't plant ambition in a person who isn't looking for it. And when the decision was finally made, change began to show quietly, little by little. It wasn't a loud event, but something inside the team started to shift. A different energy emerged, along with greater harmony, a shared language, and a clearer goal. Meetings became lighter and better understood, responsibilities became clearer, and I began to feel there were people who "fight," not just work. It was as if the team had been born again. Not because we became perfect, and not because the challenges disappeared, but because we became clearer with ourselves: we know what we want, we know why we move, and we know that the long road needs not only skill but people with the same stamina and the same belief in what we are building.

Building Knowledge: From Operion to Operion, Then Smart Academy

At the beginning of the journey there were no complicated calculations, no deep study of what a business identity means, and no real grasp of concepts like branding, building a mental image, or a corporate mission. All there was, at the time, was a person trying to work honestly and offer something they believed in. That is why the company started under the name Operion. The name seemed simple and direct to me then, and expressed something I saw as very important: that we were trying to offer smart solutions that help people and companies work better. I wasn't thinking then that a name should carry a deep philosophy, have a story behind it, or have a marketing or strategic dimension. I was moving with total spontaneity and full focus on the work itself. I believed the quality of what we deliver mattered more than any name, look, or branding. But over time, after contact with the market, dealing with customers, and the start of a real organization with its own style and way of thinking, I began to see things more deeply. I began to understand that a name is not just a word, and that identity is not just a logo or colors. It reflects a whole idea, a way of thinking, and a message the organization wants to tell the world. That is when I started reviewing myself again: Who are we really? What are we trying to offer differently? What is the core idea that moves us? Over time the meaning of the name, the identity, and the message I wanted this organization to carry became clear to me. From there came the decision to become Operion. Choosing the name was not a cosmetic change but a reflection of a completely different stage of intellectual and professional maturity. To me, the name Operion carried something that resembles what we are actually trying to do: an idea that joins operations and vision, management and thought, and daily processes and the ability to build a system that works intelligently. I felt this name was closer to what we really offer, because we weren't selling just software or technical services. We were trying to build a way of thinking, to turn chaos into a system, and to help companies see their business more clearly. So I felt Operion was not just a new name but an entirely new stage: clearer, more mature, and with a better understanding of what we want to be. But the journey didn't stop at building the company. Over time I started to feel that the experience we live every day should not stay locked inside projects, meetings, and customers. An important conviction formed in me: real knowledge must be passed on. And an experience that builds up inside a person over the years, if it doesn't become impact, content, or teaching, is largely lost. From there came the idea of turning experience into knowledge, and knowledge into content. That is how Smart Academy was born. It was not just a training platform or a side project attached to the company. It was a very natural extension of the whole journey. I saw that many people need someone to explain things to them in a practical, simple, honest way, away from academic complexity or theory alone. I wanted to pass on what we had actually lived: the mistakes before the successes, and reality before slogans. So the goal was not only to explain ERPNext but to explain the way of thinking itself: How are companies run? How are processes built? How do ideas become real applications? And how can an ordinary person with real passion carve out a different path for themselves? Then came another step very close to my heart: the idea of writing a book that explains the system. This may have been one of the things that felt most like me. To me the book was not just written content but an attempt to simplify a long journey of understanding, experimenting, and applying, to put years of practical learning in a form that helps someone else start more clearly and easily. All of this was part of a conviction that has become firm in me: real success is not only in what you build for yourself but in what you can pass on to others. That is why I see our role as not stopping at delivering a service. It extends to building awareness, passing on knowledge, and helping form a generation that understands technology, management, and accounting differently and more maturely. Perhaps that is why I feel today that the journey is no longer just a company that started from a simple idea. It has become a project trying to leave a real mark, even a small one, on the lives of those who pass through it.

The End

When I look today at this long film strip of memories, I realize that every stop I went through was necessary. Even the moments I thought at the time were holding me back, delaying me, or exhausting me for no reason, I now see were shaping something in me that I couldn't see then. Every experience, every loss, every small success, every late decision had an effect. Sometimes we learned from success, but more often we learned more from fatigue, from mistakes, from the people who did not finish the road with us, and from moments when we felt confusion, pressure, or even doubt. Over time I came to understand that the journey of building any organization is built not only on what we succeed at but also on what we survive. And that a person sometimes doesn't mature because of the things that went exactly as they wanted, but because of the situations that forced them to rethink themselves completely. That is why I now see that the dream alone is not enough. The dream matters, because it is the first spark, the thing that makes you move at all, the inner voice saying there is something worth trying. But the truth I learned is that a dream without a decision remains just a beautiful idea, because a decision is the moment you move from wishing to commitment. A decision is taking responsibility for the road even when it becomes harder than you expected, and continuing even when you don't see results quickly. I also came to believe that vision matters a great deal: seeing the bigger picture and having a sense of what you want to build really makes a difference. But in the end, execution is the real judge, because ideas alone don't build companies, change reality, or create impact. What truly makes the difference is the ability to turn those ideas into steps, then into work, then into long, patient daily commitment. And so are values. Many people talk about values, principles, respect, and professionalism. But over time I have become convinced that real values don't show up in words. They show up when they become costly: when you hold to a principle although giving it up might be easier, when you choose honesty although something else might bring faster gain, and when you keep your respect for people even while forced to make hard decisions. Only then do values become real.

Why Did I Write This Article?

I am not writing this article to tell a success story, to present myself as perfect, or to say we have reached the end. Quite the opposite: I feel we are still in the middle of the road, and there are many things we are still learning every day. But I wanted to write these words because I believe real experiences deserve to be shared, especially those that speak not only of successes but of confusion, exhaustion, painful decisions, and lessons not written in books. I wanted to tell anyone trying to build something from zero that the road is not as easy as it looks from outside, that building teams is sometimes harder than building products, and that leadership is not an image or a title but, at times, a very heavy responsibility. I also wanted to remind myself, before anyone else, that what we live today is the result of what we decided yesterday, of patience, mistakes, experiments, the people who passed through the journey, and the decisions we were sometimes late on and then learned from. Perhaps the most important thing I took from this whole journey is that real building does not happen once; it happens every day, in every decision, in every person you choose or let go, and every time you decide to continue despite the fatigue. We continue, not because the road has become easy, but because we now know why we started, and because we still believe in what we are building and in the impact we are trying to leave. We ask God to make it a good impact and a legacy on our scale of good deeds.