I also believe that we the community could help Sparx in this. We have the expertise in using this tool in the wild; Sparx don't. They don't supply their own consultants, and internally, they only develop one piece of software so even if they do eat their own dog food it's only one flavour of one brand.
So we could actually help in prioritizing what improvements to make and what features to focus on for a given goal, eg reducing cost of adoption in mid-to-large organizations. But that would of course also require a higher level of community commitment from Sparx.
For the community to help Sparx, Sparx would have to listen to the community and make EA a piece of software that actually can be deployed and used in managed environments. Like actually using %appdata% for something useful. Currently if there is a bug/defect/weakness in a MDG/script/sample/pattern/dictionary you have to download a new version (hopeless if your software licensing is outsourced) and pay your IT services company to repackage and redeploy it.
I gave up developing a MDG that a few organisations were using as it was way too hard. I should just be able stick the files for the MDG on Github and leave the rest to the end user. However to make it work have to know the ins and outs of how every the organisations (mis)manage their PC fleets.