One of the most common misconceptions about Value Pricing is that it starts with pricing.

It doesn't. Many IT consulting firms begin by replacing hourly rates with fixed fees or by bundling existing services into Bronze, Silver and Gold packages. Others simply rename an existing service and call it a Productized Service. That feels like a logical first step. The offer looks more structured. Sales has something new to present. Internally, it feels as if the company has already started the transition away from hourly billing. Unfortunately, customers rarely see it that way. From their perspective, very little has changed. The same company. The same service. The same conversations. Only the pricing model looks different. Value Pricing is not about charging differently for the same service. It is about creating an offer that customers perceive differently because it solves a clearly defined business problem, produces a specific outcome and is easier to understand and buy. Only then does pricing become part of the value proposition. Not the other way around.

Most IT consulting firms describe their work in technical terms. Cloud migration. ERP implementation. Cybersecurity assessment. Custom software development. Technically, all of that is correct. Commercially, it is often incomplete. Very few customers buy technology because they want technology. They invest because they expect a business result.

Technology is simply the means to achieve those outcomes. As long as your conversations focus primarily on deliverables, customers will naturally compare suppliers based on scope, effort and price. That makes premium pricing difficult. The conversation changes when customers understand what will be different after the project—not only what will be delivered during the project. The clearer the business outcome, the easier it becomes to justify a different pricing model.

Many companies introduce Value Pricing by changing one thing: The price. Everything else stays exactly the same. The same positioning. The same sales conversations. The same qualification process. The same proposals. The same buying experience. A few months later, they conclude that Value Pricing doesn't work. That conclusion is usually premature. Changing the pricing model without changing the sales process is a bit like installing a new engine while keeping the old gearbox. The individual components may be good. But they were never designed to work together.

The problem isn't the pricing model. The problem is that your customers are still having the same conversations they had before. Customers can't evaluate value until they understand the business impact of your work.

That means asking different questions. Qualifying opportunities differently. Discussing business objectives instead of technical scope. Helping customers make decisions instead of simply responding to requests. Pricing is only one element of that system.

Once companies decide to move away from hourly billing, many want to change everything at the same time. Every service. Every customer. Every salesperson. Every pricing model. It sounds ambitious. In practice, it usually creates unnecessary complexity. Because you're not just changing pricing. You're changing your offers, your sales process, your delivery model, your internal management, customer expectations—and often the role of leadership itself. That is a major business transformation. Trying to manage all of those changes simultaneously creates a high level of risk for both your customers and your own organisation. A much safer approach is to start with one carefully selected Productized Service. Test it. Improve it. Build confidence. Develop internal experience. Then expand step by step. That's why we recommend treating the transition as a portfolio strategy rather than a company-wide revolution.

When companies decide to move away from hourly billing, many instinctively start with the part of the business that causes the biggest headaches. Margins are under pressure. Projects are difficult to sell. Customers negotiate every proposal. The service feels commoditised. At first, this seems perfectly logical. "If we can make Value Pricing work here, it will work anywhere." In practice, it rarely works that way.

Introducing a new pricing model is already a significant change. Trying to do it in an area where customers already struggle to see the value makes that change even harder. A successful pilot needs the right conditions.

Those early successes create confidence—not only for your customers, but also for your own organisation. Once people see that a different commercial model actually works, introducing it elsewhere becomes much easier. That's why we rarely recommend starting with your weakest service. Start with the one that already creates the strongest customer value.

One of the biggest misconceptions about Value Pricing is that there is only one "correct" way to do it. Many firms immediately think about gain sharing, outcome-based pricing or charging a percentage of the value they create. Those models certainly exist. They can work extremely well. But they are also among the most demanding pricing models you can introduce. They require trust. Reliable measurement. Mature customer relationships. And an organisation that already knows how to sell and deliver value-based offers consistently. For many IT consulting firms, this is simply too big a leap. Fortunately, there are many ways to move beyond hourly billing.

The objective is not to implement the most sophisticated pricing model. The objective is to reduce your dependence on billable hours while creating more value for your customers.

Most successful firms don't move from hourly billing to pure Value Pricing overnight.

They build experience. They refine their offers. They strengthen their sales process. They expand their portfolio step by step.

Value Pricing is not a destination. It's a journey. There is no need to begin at the finish line.

Value Pricing rarely fails because the principle is wrong It fails because firms:

That often leads to the conclusion: “Value Pricing does not work for us.” A more accurate conclusion would be: “We introduced it in the wrong way.”