https://en.wikipedia.org/wiki/Slang_terms_for_money#United_S...
It's probably not precisely measurable, but it's a great thought exercise. It prompts us to think about the entire process from noticing an idea to a customer deciding to buy.
And Time to Customer's Customer Value -- I forgot that TTC^2V was the alternative name -- is even better. It makes us think about the journey from us noticing a need, developing it, releasing, customer installing, their team using it, releasing to their customers, who decide it's worth paying for.
When you turn that into a loop, you get something very like the Gitlab master plan. We call it the "Circle of Code", Onsi Fakhouri talked about it early this year: https://youtu.be/7APZD0me1nU?t=23m6s
Personally, I have mixed feelings about feature flags. They're the worst thing after feature branches, which are the worst thing after feature flags.
Then there's Time to Customer Value, which is the time it takes before a customer using the feature turns a buck on it.
> there is a risk of starting to optimize for the numbers
There absolutely is. You can only use your own judgment of the balance of risk between flying blind and becoming obsessed with instrumentation.