Well, if that started happening I'm sure people would start posting stories of how disingenuous the company's practices had become. If they flagged some softwa

Well, if that started happening I'm sure people would start posting stories of how disingenuous the company's practices had become. If they flagged some software as malware they should already know exactly what the reasons are. So we'll call that maybe a 1-2 hr session to get up to speed on exactly what the issues are. How someone goes about fixing it is another story. I'd say by default those sessions should be posted online for public viewing just so everyone can learn from the mistakes of the original team, or to make a judgment of how disingenuous Google is being about the issues. At the request of the project requesting those services they could make those sessions private. Also this could lead to real innovation in the tooling for example Google consultants could write unit tests that would need to pass in order to be allowed on the Google App store. Those unit tests would then, potentially become public so everyone could just download the unit tests from Github in order to confirm their software meets requirements. The other thing is Google would almost certainly see this as a cost center. Billing people at-cost (or slightly above that) for consulting services is way more labor intensive and tbh annoying for companies with a trillion dollar + market cap.