{"id":209,"date":"2025-10-15T20:49:36","date_gmt":"2025-10-15T20:49:36","guid":{"rendered":"https:\/\/deguzman.ph\/?p=209"},"modified":"2025-10-16T01:18:55","modified_gmt":"2025-10-16T01:18:55","slug":"when-professional-services-became-products-lessons-from-a-2010-transformation","status":"publish","type":"post","link":"https:\/\/deguzman.ph\/index.php\/2025\/10\/15\/when-professional-services-became-products-lessons-from-a-2010-transformation\/","title":{"rendered":"When Professional Services Became Products: Lessons from a 2010 Transformation"},"content":{"rendered":"

In 2010, I was brought into a professional-services firm facing a paradox common in many legacy partnerships: the organization was unified by brand, but fragmented by practice. Each industry head operated as a self-contained business \u2014 independent, successful, but inward-looking.<\/p>\n

What emerged was not one firm, but many firms sharing a logo.<\/p>\n

Back then, the term \u201cprofit center\u201d<\/em> was fashionable, and the model was celebrated as entrepreneurial. In practice, it had begun to erode what made the organization valuable: shared knowledge, shared data, and shared accountability.<\/p>\n

Reframing the Structure<\/strong><\/h3>\n

The first task was to move from practice-based silos<\/em> to a system-based enterprise<\/em>.<\/p>\n

The solution wasn\u2019t to take control away from partners \u2014 it was to give them a shared commercial discipline<\/strong>.<\/p>\n

We built a unified sales architecture<\/strong>, linking all practice heads to a common business development system governed by a single sales strategy and operating rhythm. Sales planning became a structured cycle \u2014 quarterly objectives, shared performance dashboards, and cross-practice pipeline visibility.<\/p>\n

This was not common in 2010. Most consulting and search firms then treated \u201csales\u201d as a function of relationships, not structure. Yet even then, it was clear: relationships scale when systems guide them.<\/strong><\/p>\n

Building the Early Infrastructure<\/strong><\/h3>\n

The technical piece was the introduction of Salesforce<\/strong>, which at the time was still evolving from CRM to platform.<\/p>\n

We configured it not as a contact manager but as the firm\u2019s central nervous system \u2014 integrating business development, client management, and candidate information.<\/p>\n

Perhaps the most important move was cleaning and securing the firm\u2019s candidate database<\/strong>, a digital asset as valuable as any intellectual property. At a time when data privacy and protection were afterthoughts, we were already enforcing principles now standard in data governance<\/em> and knowledge management<\/em>.<\/p>\n

In hindsight, that project anticipated what\u2019s now called data as an institutional asset<\/em> \u2014 treating information not as an administrative record but as capital.<\/p>\n

The Forward Look<\/strong><\/h3>\n

Fifteen years later, these same principles underpin digital transformation in far more complex organizations.<\/p>\n