This sounds impractical and also skews development focus to features of a product that relate to short term revenue gains, not necessarily long term & customer focused improvements. For example, I think SaaS products & subscriptions should have good cancellation processes, which are the opposite of revenue generating. Someone working on the cancellation process with an eye on revenue generation is going to dig deep into the bucket of customer hostile anti-patterns, and nobody should be paid for that work.

They might have a better answer to this than the short term & limited analysis they describe in the article, but I think it is typically very hard to link individual features to revenue and not all beneficial features will be revenue generating. It is rare for SaaS or application pricing models to be per feature (e.g. pay $5/month more for this single feature). So, considering that there are a lot of other factors affecting revenue, how do they isolate the effects of a single feature? My guess is that even with public metrics, the company does, so the developer is depending upon a fair assessment.

I also wonder if they measure this new feature's effect on customer retention, which isn't an obvious short term increase. I can think of many examples of features I've introduced in the past that didn't directly increase short term revenue but did improve the customer experience, which is key for customer retention for our annual payment models.