Is 1 + 1 = 1,5 or should it be 3?

When a customer uses your AI workflow solution in one department, the pricing is relatively straightforward. But what happens when they want to roll it out across two, three, or five departments? That is where things get interesting.

You essentially face two fundamentally different pricing philosophies.

The discount model: 1 + 1 = 1,5

The first approach says: give them a volume discount. If one department costs 1, two departments should cost less than 2. Maybe 1,5. The logic is rooted in a land-and-expand strategy.

The reasoning goes like this:

• Lower the barrier to expansion. Make it financially attractive for the champion inside the organization to push for broader adoption.
• Increase switching costs. The more departments that use your solution, the harder it is to rip out. The discount is an investment in long-term retention.
• Win the account before competitors can. Speed of expansion matters, and a discount removes friction.

This model works well when your primary competitive risk is that another vendor captures the next department before you do. It is a market share play. You trade short-term margin for long-term account control.

The premium model: 1 + 1 = 3

The second approach says: charge more per unit as the solution spans more departments. If one department costs 1, two departments together should cost 3. The logic here is fundamentally different.

The reasoning goes like this:

• Cross-department orchestration creates new value. When AI workflows span departments, they enable things that siloed deployments cannot: end-to-end process automation, shared intelligence, and unified reporting. That incremental value deserves a premium.
• Complexity increases, not decreases. Multi-department deployments require more integration work, more stakeholder management, and more customization. Your costs go up, so your price should too.
• Position as a strategic platform, not a tool. A tool gets discounted. A platform that orchestrates across the organization commands premium pricing.

This model works well when the cross-department value is genuinely greater than the sum of individual department deployments. If you can demonstrate that connecting departments A and B creates outcomes neither could achieve alone, the premium is justified.

How to decide

The choice between these two models is not abstract. It depends on three factors:

1. Is the cross-department value real and demonstrable? If connecting departments creates measurable new outcomes, lean toward the premium model. If the value is mostly the same solution replicated in a new context, the discount model is more honest.

2. What is your competitive position? If you are in a crowded market where speed of adoption matters, the discount model helps you secure territory. If you have a differentiated offering with limited competition, the premium model captures more value.

3. What does the customer’s buying process look like? If each department has its own budget and decision-maker, the discount model helps your internal champion make the case. If there is a centralized IT or transformation budget, the premium model aligns with how they think about platform investments.

The honest answer

Most companies I work with end up somewhere in between. The key is to be deliberate about which direction you lean and to have a clear rationale for it. The worst outcome is pricing that is accidentally discounted without strategic intent, or accidentally premium without the value story to back it up.

Know whether your 1 + 1 should equal 1,5 or 3, and know why.

Thinking about your pricing model? Let’s talk.