Ask HN: How can I charge my enterprise clients by value?
https://news.ycombinator.com/item?id=9538418An ongoing theme on HN is to price consulting projects based on the value achieved. Often, people in this context equate value with revenue increase, and almost always they are former web contractors that now mix marketing consulting in their offerings [1]. I find this advice intriguing but fail to connect this to my situation.
Currently, I am running a solo shop as a systems architect and programmer specialised in telecommunications. My clients are big telcos, the projects are part of multi-year initiatives, and their goals range from compliance with regulatory requirements, to new product roll-outs, to cost-cutting. I build them small, special-purpose network services for which the big IT service providers are either too expensive, too slow or just don't have the right skills at hand. I charge either by day or fixed-price, where the latter is still based on an effort estimate, plus contingency.
How should I ever get to the position to price by value? Often, my direct project sponsors themselves can't put a price tag on the value achieved. Working deep on the systems layer, there are many hops and even more so contributors between me and my clients top or bottom line. I see zero chance to get a procurement department agree to a profit-share with a single guy like me.
Do I have the wrong clients for this kind of pricing strategy? Or has someone here achieved it while staying small/solo in the enterprise world? I could also find gigs as a business analyst/program manager at my telco clients, but I don't think it would make a difference in the pricing strategy.
[1] A notable exception from this seems to be tptacek's Matasano. Still, with no experience in the security industry, I wonder how value-based pricing works there, given that security services IMHO seem more geared to preserve value than increase.