[zerkten]

I'm a little confused about which DAM use cases this solves today, and which ones are next. Devs often do not understand the details or complexity of the use cases you are dealing with and can't work out how to slot this project in.

If you are looking to drive revenue eventually from this project I'd think about the compliance and asset usage angles. It may be cheap and easy to implement reporting features which will get you adoption. My experience with DAM has been that people will try to avoid integrating with a DAM, so it's hard to achieve the vision of everyone using it by opting in. If you are reporting on who's using old assets, assets are reused inappropriately, who needs to be contacted to replace something etc. it will be much easier to get adoption. Then push on the other parts of the DAM vision.