top of page

Why I Started Ishikawa Technologies - Stuart McCaul

  • 5 hours ago
  • 3 min read
Last year I had the opportunity to speak with Fearghal O’Connor of the Sunday Independent about software, business, community and the thinking behind Ishikawa Technologies. The conversation inspired some reflections on stewardship, succession and why I believe Europe needs a better home for founder-built software companies.
Last year I had the opportunity to speak with Fearghal O’Connor of the Sunday Independent about software, business, community and the thinking behind Ishikawa Technologies. The conversation inspired some reflections on stewardship, succession and why I believe Europe needs a better home for founder-built software companies.

Over the course of my career, I have had the opportunity to work with a remarkable number of software companies. Some were large, some small; some growing rapidly, others facing significant challenges. They served different markets, sold different products and employed different strategies. Yet the more time I spent with them, the more I became interested in what they had in common rather than what set them apart.


In almost every case, the success of the company could ultimately be traced back to a founder or small group of founders who had identified a problem worth solving and then devoted years, often decades, to solving it. What appeared from the outside to be a software product was, in reality, the accumulated result of thousands of decisions, relationships and acts of persistence. The customers saw the software. The founder saw the journey.


As I progressed through my career, I found myself spending less time thinking about software and more time thinking about stewardship. What makes a company endure? Why do some businesses continue to thrive long after their founders depart, while others gradually lose the qualities that made them successful in the first place?


Those questions became increasingly relevant as I met founders who had reached a particular stage in their lives. Their businesses were often healthy. Customers were loyal. Employees had built careers there. In many cases, the company was performing better than it ever had before. Yet after twenty or thirty years of responsibility, they had begun to think about what might come next.


What struck me was that the decision was rarely driven by money alone. Of course, valuation matters and founders deserve to be rewarded for the risks they have taken and the value they have created. But the conversations I found most interesting were rarely about price. They were about responsibility.


Founders would talk about long-serving employees. They would talk about customers who had relied upon their software for years. They would talk about products that still had unrealised potential. Above all, they would talk about the fear that what they had built might gradually be dismantled, neglected or transformed into something they no longer recognised.


It seemed to me that there was a gap in the market, not for another financial buyer, but for a different type of successor.


The idea behind Ishikawa Technologies emerged from that observation. I wanted to create a company that approached software acquisitions from the perspective of stewardship rather than simply ownership. A company that recognised that when a founder sells a business, they are not merely transferring assets. They are placing trust in somebody else’s hands.


That is why we describe our ambition as creating the best home for European software companies. The phrase is deliberately simple. We are not attempting to create the largest software group in Europe, nor the most acquisitive. We are trying to build an organisation that founders can feel confident handing their businesses to, employees can feel proud to work for, and customers can rely upon for the long term.


The name Ishikawa was chosen deliberately. It reflects a long-standing interest in Japanese management thinking and particularly the principle of continuous improvement. Most successful software companies are not built through moments of genius or dramatic transformation. They are built through the accumulation of small improvements over long periods of time. The same is true of the businesses themselves.


When we acquired Big Red Cloud, we inherited more than a product and a customer base. We became responsible for a business that had helped tens of thousands of organisations manage their finances and employ their people. We inherited a community of customers, employees and partners who had placed their trust in the company over many years. Preserving and strengthening that trust is a responsibility that I take seriously.


Ultimately, Ishikawa was founded because I believe that great software companies deserve thoughtful succession. Founders deserve more than a transaction. They deserve confidence that the work of a lifetime will continue to matter long after they have moved on. That is the standard we have set for ourselves, and it is the standard by which I hope we will be judged.


-SM

 
 

Subscribe to get new blog posts.

bottom of page