The Professional Services Transformation Paradox #10 – Client Intimacy vs. Platform Standardization

28. April 2026
Kategorien
Newsletter abonnieren

Professional services firms win through relationships.

The closer they are to the client, the more value they create. Understanding the client’s context, adapting to their needs, shaping solutions around specific situations rather than applying generic ones. That is where trust is built, where differentiation happens, and where premium pricing becomes possible.

Standardization moves in the opposite direction.

Transformation requires platforms, processes, and delivery models that can scale across clients, teams, and geographies. It depends on repeatability, consistency, and the ability to reduce variation in how work is delivered. Without that, there is no leverage, no efficiency, and no real transformation.

That is where the tension starts.

Because the closer you are to the client, the more you customize. And the more you standardize, the more you constrain that customization.

At the level of individual engagements, this often feels manageable. Teams adapt templates, adjust processes, and make exceptions to fit the client. The system bends slightly, and the relationship is preserved. But at scale, those small adaptations accumulate. What was designed as a standard platform becomes increasingly tailored, and over time, the standard starts to erode.

This is where many transformation programs begin to lose their edge.

They start with a clear ambition to create consistency and scale, but encounter a reality where client demands pull in different directions. Each exception is justified. Each deviation makes sense locally. But collectively, they push the organization away from standardization and back toward fragmentation.

The alternative is equally difficult.

If firms enforce standardization too strictly, they risk weakening the very relationships that drive their business. Clients do not experience “platforms.” They experience outcomes, responsiveness, and relevance. A model that feels rigid or disconnected from their specific situation quickly erodes trust, even if it is more efficient internally.

There is no easy balance between the two.

Standardization creates efficiency, scalability, and control. Client intimacy creates relevance, trust, and revenue. The more a firm pushes toward one, the more it puts pressure on the other.

This becomes particularly visible in large-scale transformations.

Global platforms are designed to enable consistent delivery, but local teams adapt them to maintain client relationships. Over time, the platform becomes more complex, less coherent, and harder to scale. What was meant to reduce variation ends up managing it.

The partnership model reinforces this dynamic.

Partners are accountable for their clients, not for the platform. Their incentives are tied to revenue, retention, and relationship strength, not to the level of standardization achieved across the firm. When forced to choose, they will protect the client relationship.

And that is entirely rational.

Which is why the system behaves the way it does.

Externally, the firm presents a structured, consistent delivery model.

Internally, delivery adapts continuously to client needs.

This creates a structural limit to how far standardization can go. The firm can build platforms, define processes, and enforce guidelines, but it cannot fully eliminate the need for adaptation without changing the nature of its client relationships.

That is why so many platforms in professional services end up being “standardized, but.”

Standardized, but with exceptions.
Standardized, but adapted locally.
Standardized, but interpreted differently across teams.

The deeper issue is not execution.

It is that the model is trying to optimize for two opposing sources of value at the same time.

As long as firms rely on deep client intimacy to win and grow, they will continue to customize. And as long as they try to scale through platforms, they will continue to standardize.

The tension is not something to solve.

It is something to manage deliberately.

Because if it is not, the organization will default to protecting the client relationship.

And the platform will slowly disappear behind it.


This article is part of a series exploring the tensions at the heart of the Professional Services Transformation Paradox.

The paradox is simple. Firms that excel at transforming their clients often struggle to transform themselves. Deeply embedded incentives, partnership structures, and legacy operating models create internal resistance to the very change they advocate externally.

Each article in this series focuses on a specific contradiction. Structural, economic, or cultural. These tensions are not side effects. They sit at the core of how decisions are made, how transformation is executed, and why many programs underdeliver.


I work with boards and executive teams on independent perspectives related to professional-services transformation, governance, operating models, platform economics, and the changing economics of professional-services firms.

If your leadership team is working through similar questions around ownership structures, governance alignment, investment pressure, or operating-model evolution, you may find my Future of Professional Services board sessions and Transformation Reality Review valuable. Feel free to reach out.

Henrico Dolfing

Tags

Das könnte Sie auch interessieren

Solving Your Between Problems

30. August 2020

Most executives agree with me that the biggest problems are not within roles but between roles.    Not within teams but between teams.    Not within departments but between departments.    And not within organizations but between organizations.     Such “between problems” are not assigned to anyone. Why? Because they are between.    And these

Weiterlesen

However Beautiful the Strategy, You Should Occasionally Look at the Results

6. Juli 2020

The title of this article is frequently credited to Winston Churchill (1874-1965), but he never said it. The saying first appears from about 1981, many years after Churchill’s lifetime.   The saying is used to stress that one needs to look at results and shouldn’t fall in love with one’s designed strategy if it doesn’t

Weiterlesen

Your Risk Matrix Is a Lie

15. Juni 2020

Risk management is at the core of good project management.    Or as Tim Lister says “Risk management is project management for adults”.     The standard approach is to use a risk matrix to classify project risks based on their probability and impact, then give each one a ‘risk score’ by multiplying the two numbers.

Weiterlesen

Most Good Strategies Are Not Planned

7. Juni 2020

Many people are discussing strategy and strategizing as if they were the sole outcome of a rational, predictable, analytical process.   But reality is often the opposite; emotional, unpredictable, and chaotic.     How organizations create and implement strategy is an area of intense debate within the strategy field.   Famous researcher on management and strategy

Weiterlesen

Is Your Strategy Bad? A Simple Checklist

26. Mai 2020

Recognizing good strategy is hard.    You need to understand the organization, the market(s) it is operating in, its competitors, its strengths, and its challenges.    On the other hand, recognizing bad strategy is easy.    Richard Rumlet coined the term “bad strategy” in 2007 at a short Washington, D.C., seminar on national security strategy.

Weiterlesen

The Difficult Act Of Balancing Your Project Portfolio

16. Mai 2020

Balancing your project portfolio is like juggling one hundred balls… in a storm… on a boat.    Project portfolio management is not necessarily complex. The goals are clear and simple.    1) Maximizing the value of your portfolio    2) Seeking the right balance of projects    3) Creating a strong link to your strategy 

Weiterlesen

People, Process, Technology (In Exactly That Order!)

11. Mai 2020

As an IT or information security professional, you cannot read a blog, book or paper without crossing paths with these three words; people, process, technology.    Popularized in the infosec world at the end of last century by Bruce Schneier, these three nouns have been at the heart of the ITIL set of practices since

Weiterlesen

Show Me Your Budget and I’ll Tell You What You Value

3. Mai 2020

Being in the middle of the yearly budgeting process I could not help but think about this quote from former US Vice President Joe Biden; “Don’t tell me what you value, show me your budget, and I’ll tell you what you value.” The RGB model developed in the early 2000s by Louis Boyle at Meta

Weiterlesen

Project Complexity Assessment

1. Mai 2020

One of the main reasons technology projects fail so often is their (underestimated) complexity.   Managing this complexity should be an urgent concern for any organisation doing large technology projects.   And before you can manage the complexity of your project, you need to understand what drives the complexity of your project.   That is

Weiterlesen

Complexity Is The Enemy Of Execution

1. Mai 2020

The title of this article is a quote from Tony Robbins, and he is absolutely right.   One of the main reasons technology projects fail so often is their (underestimated) complexity. Managing and reducing complexity in projects should be an urgent concern for any organization. But before you can manage and reduce complexity you should

Weiterlesen
PreviousNext