The predominant reason we use M-Files is for the legal team to be able to manage contracts and the signatures between those and the change orders. We're a construction company, and when we have a contract to go build a building and they want to change it, you have to have a change order. We use M-Files for storing those types of legal documents.
Read reviews of M-Files alternatives and competitors
Good workflows, and it is easy to use with a dashboard that improves contract visibility
Pros and Cons
- "Using M-Files means anybody on the executive team to go in and immediately look at a dashboard and know the status of a contract."
- "The integration with other products needs to be improved."
What is our primary use case?
How has it helped my organization?
Using M-Files means anybody on the executive team to go in and immediately look at a dashboard and know the status of a contract. It has been huge for us.
What is most valuable?
The workflow is probably the number one reason we picked it. They have a very simple to use interface for normal people, who are not very technical. They can drag and drop a process and specify metadata, then set it up to be delivered to certain people, send approvals to others, ask to be alerted of updates, and so on. They have a very nice workflow.
What needs improvement?
The integration with other products needs to be improved. Our biggest problem is that it is very difficult to set up for API so that we can authenticate into it and pull data out. We want to be able to feed other dashboards that we have or to feed other processes.
Technical support is slow to resolve issues, which is something that needs to be improved.
They have implemented some AI where you can scan documents and bring up insights, but additional AI would be very good.
For how long have I used the solution?
We have been using M-Files for almost a year, since November of 2019.
What do I think about the stability of the solution?
This product is very stable.
What do I think about the scalability of the solution?
This is a very scalable solution. They have lawyers with two million documents that go in every year. The people we have using it are our legal VP, our contracts manager, our license coordinator, our program managers, and our IT people.
How are customer service and technical support?
Technical support is probably the weakest part. We had a number of authentication issues and support has been very slow to respond and get us solutions. They have, but we had one issue up for over a month. I would rate the support a four out of ten.
Which solution did I use previously and why did I switch?
In this company, M-Files is the first document repository or content manager that they have used.
In previous companies, I have used many solutions including OpenText, PandaDoc, and others.
How was the initial setup?
The initial setup is mostly straightforward, especially since it is a cloud product. They did it all.
What's my experience with pricing, setup cost, and licensing?
They have an Optical Character Scanning module but we didn't buy it because it's ridiculously expensive.
What other advice do I have?
My advice for anybody who is looking into implementing this product is to do a pilot first. After you do your research, do an actual pilot before you commit because everyone has nuances and you might find out that it is not what you want, or that it doesn't really do what you think it's going to do.
It is not the simplest product to use but because of the robustness of its feature set in the ability with the workflows, and the APIs, to do just about anything you can imagine with it, that's very valuable. I wish it was a little easier to use because we have to spend more time than I'd like with new users, teaching them how it works. We try to hide all that from them but the setup time to get everything the way we wanted was probably two months.
That is two months in one resource working on it half time a week, but it just took a lot of work to get the metadata set up, to get the workflows set up, and to get all the documents added to the repository. Now we've got versioning and we know where everything's at, the dashboard is great, but don't assume when they tell you that you'll be up and running in two weeks, that that is the truth. It takes much longer than you think.
I would rate this solution an eight out of ten.
Which deployment model are you using for this solution?
Disclosure: I am a real user, and this review is based on my own experience and opinions.