Docmosis vs. FluidSurveys (Discontinued)

With customer support and flexibility in handling specific, unique scenarios, they are able to provide solutions quickly. There are no scenarios currently which we are aware that it may be less appropriate. If you have very large documents you should review architecture choices on how best to optimize your performance using Docmosis.

For surveys, and for centralized info-gathering, FluidSurveys provides an excellent solution. There are other programs out there which provide a wider range of solutions (i.e., they can be used for surveying AND comprehensive online engagement, rather than just a data-gathering type of consultation); however, for programming and implementing surveys, FluidSurveys has an effective variety of strengths and options that make it optimal for users who are focused specifically on surveys.

• Docmosis is excellent at support and will work with you to find a solution for your particular use cases.
• During our evaluation process, they were very helpful to get us up and running and we were one of the first docker based implementations so they worked quickly to get our infrastructure support setup.
• Their solution is very flexible and allows several ways to allow support dynamic document generation at a very good value.

• User-friendly. For the majority of the general and basic tools you can use with FluidSurveys to build surveys are simple to use and intuitive. When certain issues come up, the service is quick (chat room) and effective.
• Anonymity: the software has the reputation of being safer in terms of safeguarding private information the respondents share by answering surveys (this is mainly due to the fact that the servers are in Canada). Thus, indirectly, they increase response rates.
• Extensive possibilities: FluidSurveys offers a plethora of possibilities and options that really renders the experience interesting in terms of micro-managing each details of the surveys you are sending out there. When the invitation leaves by email, it is exactly how you want it.

• There isn't much in terms of what could be improved, but the only challenge we have which is in terms of future scaling and isn't a limitation, but just something we're trying to be cognizant of as it might increase our infrastructure costs. Since we have large numbers of multi-nested document templates, and large documents. Although Docmosis did help us reduce the time to generate our largest documents by a large percentage. This is likely an area of improvement that all providers would need to address.

• There should be more flexibility and customizability with regard to survey design (e.g. background, fonts...)

Note: I am responding to this question as a user of the system and not a representative of my organization.

On a personal level/as a user only, I would definitely continue to use FluidSurveys.On a personal level/as a user only, I would definitely continue to use FluidSurveys.

I think the average person can very quickly pick up on the basics of the system: they would have no problems programming and launching a basic survey. Organizations may benefit from having people of different backgrounds getting their hands dirty in the system: at a minimum, both web programmers and opinion research advisors should be solicited for input or help.

They always respond to support and provide resolutions quickly and even provide the ability for new features/support to be incorporated very cooperatively by help with with alternate solutions as necessary.

We also evaluated Winward Studios solution along with HotDocs, we selected Docmosis for the following reasons:

1. We were using docker very early on, so they were very cooperative in helping us get our infrastructure working during the early evaluation phases, and went above and beyond to help with some of our template processing efforts.

2. When we were looking to improve the processing speed due to our complex large number of dynamically inserted templates, Docmosis was helpful with ideas. We were able to improve speed quite significantly with Docmosis' help by managing some dynamic aspects of our templates and including them inline vs. having them loaded dynamically.

Although I do not have much experience with Survey Monkey, the only two reasons why I choose FluidSurveys is that clients demand it (privacy and anonymity) and because managing multiple surveys at a time is easier. As for ODK Collect, I think it is a valuable alternative to FluidSurveys if you have time to learn the coding (not very complicated). ODK is a little less user friendly and you cannot address small details as you can with FluidSurveys (e.g.: formatting).

• Very strong impact on ROI as it's value has been able to scale with our user growth.

• Confidentiality of data is a big concern for our company, and we feel more secure working with a Canadian company. Our clients feel more secure, too.