What do you like best?
The Brandfolder platform is configurable to fit with our organization and the initial and ongoing from their team has been fantastic. Brandfolder listents to our needs and has been very accommodating.
They helped us identify a taxonomy that worked for our business, and the set-up and roll-out was super quick - about a month. The product is not overly complex - in fact it's fairly simple, but it fit well with our requirements of needing a simple DAM with just the right mix of features but not so weighty it would take forever to learn or use.
Also a really great feature is that we can upload image assets, then if we need to download them in a different file format or different size, that functionality is built right in.
What do you dislike?
Initially we did have some performance issues, but I must say Brandfolder was very responsive to that and is making fast steps to really improve the speed of asset retrieval. They are upgrading data centers and now the speed one expects with a Saas platform is on par or very nearly there.
Another feature that can be improved is on the usage analytics side (which I understand is on their roadmap). A valid question we want to solve for is which assets are consumed the most and by whom?
Recommendations to others considering the product
Consider how quickly it is to implement; how quickly it is to evangelize the value proposition, and the level of personal support. Also how mature your organization is to incorporate DAM into your technology stack and processes.
What business problems are you solving with the product? What benefits have you realized?
The business problem we are seeking to answer was simply a central location within which to store our marketable assets. We had previously so many places that content was stored, without an overarching taxonomy that it was impossible to find anything. Brandfolder has made that a lot easier simply by having one central location, with our own content taxonomy laid on top of it.
Primarly we have used Brandfolder as an internal resource, but another use case is external: deploy once, and use multiple places. For this use case, we would need more robust analytics on consumption, so if they can solve for that I think it would be a hit out of the park.