In software development, “retrospective” has a specialized meaning – it’s a post-implementation review, or “post-mortem.” Over the years, this practice has helped Tensoft continue to improve both our products and implementation services. In celebration of the ten year anniversary of Tensoft Fabless Semiconductor Management (FSM), a thoughtful retrospective of Tensoft’s work with semiconductor companies seems in order.
When Tensoft first developed FSM, we became involved with the Global Semiconductor Association (GSA), which was then called the Fabless Semiconductor Association (FSA). At that time, the GSA sponsored quarterly forums, and Tensoft presented at every Supply Chain and ERP Forum until they were discontinued, and exhibited annually at the association’s tradeshows. This led to introductions to many of Tensoft’s early customers, and broadened our understanding of the semiconductor industry.
During what many consider the harshest downturn in the history of the technology industry, Tensoft launched FSM 2.0. The upside for us was that even $500M fabless semiconductor companies were conserving cash, so FSM’s low total cost of ownership was very attractive. By 2006, there were enough Tensoft customers to start a quarterly user group, as well as an annual user conference. These events boosted the collaboration between Tensoft developers and customers to a new level, and solidified the industry best practices that are now built into every Tensoft FSM release and enhancement.
A true retrospective must take a hard look at “lessons learned,” as well as “hurdles overcome.” Working with semiconductor companies for a decade taught us that understanding the needs of their operations, customer service, planning, finance and other departments wasn’t enough - we had to be able to handle and support the types of organizational change that our semiconductor customers grapple with. We’ve seen companies go through three CFOs in two years, growth by a factor of ten in a six month period, or drastic reversals of fortune – or business models – as well. We learned to adapt our support model and sometimes even step in and offer help before the customer was even aware of the need for it. I think it’s one of our proudest accomplishments that we’ve been able to support customers going through some extraordinary stress during periods of really chaotic change.
I think that going through this crucible together has formed some remarkable long-term relationships. The community aspect of this relationship has changed the dynamics of our R&D and market approach, so that taking care of existing customers is the first priority, and bringing in new customers is actually the result of taking care of that first priority. The level of involvement with some of our customers and their involvement with being part of our product development and with the rest of the user community is the really fun and fulfilling part of Tensoft’s business – we’re a living, breathing part of this dynamic organism, which is people using our software to achieve their business objectives.
