How can we switch to value-based pricing and quantify the value fairly?

[AndrewRR]

We’re trying to decide whether to switch from a flat project fee to a value-based pricing model for our consulting work. I’m stuck on how to objectively quantify the “value” we deliver for a client in a way that feels defensible and fair, without it seeming arbitrary.

[Olivia66]

We started by listing concrete outcomes we touch—time saved, fewer defects, faster decisions—and then attached a dollar figure to each based on their own costs. It felt defensible because it tied to their numbers, not our gut.

[MilaR]

I tried a simple model: impact = hours saved × client’s hourly rate plus risk avoided × cost of risk. It worked for one client, but after a while they pushed back on the risk weight and we renegotiated.

[ScarlettS]

Do you think the metric has to be universal or can it be project specific and still feel fair?

[Eric_M]

Sometimes it helped to pause and show a plain forecast to the client—a one page with expected outcomes, a couple of scenarios, and no hidden clauses—then we got to a price. Other times we walked away and kept the flat fee.