What do you like best?
FileBound offers a tremendous amount of functionality at entry level cost. The features contained in FileBound are extremely useful for automating a variety of document based processes but these features are usually only found in extremely expensive enterprise level products. FileBound brings expensive product functionality to the table for mid-sized businesses that are not able or not willing to spend large amounts of capital on enterprise level software products.
The greatest thing about FileBound, in my opinion, is the flexibility to use the product within any department in an organization to tackle multiple and diverse business problems.
What do you dislike?
Due to the large amount of functionality within FileBound there have been some stability issues with past versions of the product. When rolling out new versions of the product in the past certain pieces of functionality have become unstable or unpredictable, requiring FileBound to review and fix. The good news is that FileBound is quick to respond when any issues arise and they work diligently to fix any issues as soon as they arise, leading to many of the stability issues being addressed and fixed by FileBound in previous versions via patches or upgrades. I am happy to report that the currently available version, version 7, is much more stable and reliable than past versions, while including new functionality that has helped the product address specific business needs and become more useful to businesses of all sizes.
Recommendations to others considering the product
Make sure that you have any business processes you are planning on implementing in FileBound mapped out completely and in very much detail. This will help you ensure that you are re-creating the client's business process as it currently exists.
Additionally be prepared for scope creep and be prepared to push back on it. As clients start to see and learn about the different features within FileBound they become a "kid in a candy store" and want every feature they see implemented in their new process. This is all well and fine and understandable, but you must be prepared to tell the client "not yet", and make sure you get the system implemented first. Trying to include scope creep in an initial implementation is a recipe for disaster, and will very easily cause system implementation to fail. It is best to first recreate the business process in FileBound as it is currently used so that users completely understand what they are doing in the system on a day to day basis. Once the system is implemented you can move onto "Phase 2 and Beyond", which is adding features and functionality that the client would like to improve their current process with.
What business problems are you solving with the product? What benefits have you realized?
The business problems we are solving with FileBound typically relate to paper pain within an organization. We have helped clients tackle paper problems ranging from backfile conversions and storage needs to electronic Business Process Management (BPM) to electronically capture and route documents through an organization for review. We have used FileBound in scenarios across Accounts Payable (to route and approve invoices for payment), Human Resources (to provide an Employee On-Boarding System) and within Purchasing (to create a Vendor Purchasing On-Boarding System).