Improved customer service and access to grant documents for our subrecipients.

There are so many options to customize features and functionality to meet the unique needs of your specific organization.

Limited training seats were available with the implementation package, and purchasing additional training seats is a bit expensive. Due to the level of customization the trainings did not always meet the needs of our organization. It would also be helpful to have access to training manuals versus the videos and limited slides that can be downloaded for reference.

What I like most about Fluxx is that changes to the live process or forms can be made on-the-fly. This is very helpful for us as a new foundation still iterating on really everything to do with our grantmaking cycle. Another thing I like is that the company really does listen to its user community, incorporating our ideas into their updates.

What I like least aboutFluxx is that it's capability is deep, but there isn't a good way to tap into all that is available. When we set up the system, the implementation folks map the Fluxx system to your current process without really sharing what is available/possible. So now that we are changing our processes, there could be features that we could use but we don't even know what is available. Also, there is a lot that can be done with liquid code, but if you aren't fluent in liquid, there really aren't any resources to help except for other users who are busy with their own jobs.

The experience with iNet when we implemented in 2019 was less than ideal. After handing over the reigns to us, and we learned the administrative backend on our own, we quickly realized that the initial build of Fluxx was already unsustainable in the way it was structure. The documentation that was provided was less than ideal and was very little help. The training was also miserably lacking, as our whole staff would likely agree on. Fluxx was a step forward for us, as we have been using a legacy system may decades old, but the longer we used it, the more issues cropped up. The more I learned in the admin panel, the more I realized that the current setup was unsustainable and would eventually require a complete rebuild if we were to remain. We got very little help with that issue (about unsustainability) and little to no advice from Fluxx on how to proceed. We are getting by today, but as we add more programming we continue to struggle to fit things in our current setup. Not only is the setup an issue, the persistent issues with existing functionality, the bugs that arise and take a year to get fixed. Its been frustrating to say the least.

That it's cloud based, and helped our organization modernize.

The service, hands down. It takes days and weeks sometimes for tickets to be responded to. We've had tickets open for years that impact the usability and administration of the system. Tickets sent to engineering get lost in the void so much that its a common jest among the Fluxx user communities. I often have to reach a point of frustration where I am emailing our Fluxx representative before movement is made. And still, most often the response is that 'its with engineering'.

Fluxx is incredibly customizable. We were able to build and implement grant processes that reflect our values and the desired relationship we want to create with grantees and applicants, rather than needing to create workarounds based on an out-of-the-box or one-size-fits-all system. The connected data structure mirrors the relationship-oriented way we work and makes it very easy for members of our staff to move through the network of grantees and applications. Complex reporting tools are available and there are many features and integrations to experiment with and refine our processes so it can improve from year to year. Additionally, there is a strong Fluxx community to rely on with questions about those features or ways of maximizing the impact of Fluxx.

Shifting from an out-of-the-box GMS to Fluxx meant that we weren't prepared for the amount of work it would be to set up, build, and maintain Fluxx. Some back end tools like document and email templates require strong knowledge of liquid code. Staff members who are not fluent in Fluxx can't design their own reports, for example, because of how complex reporting in Fluxx is (the knowledge of backend field names is required, as well as understanding the relationships between models). Operating Fluxx, though it results in strong report, a flexible workflow, and lots of customization, is a heavier lift for the grants team and required new staff hires with past Fluxx experience. Additionally, the support team, though thoughtful and helpful in the moments when something goes wrong, is not available to brainstorm solutions, just solve problems. It would be helpful to be able to consult with someone inside of Fluxx when we have questions about new features or tools that could benefit us, rather than needing to seek that out from the community or pay for an additional contract.

Mostly positive. There is a great community that provide a lot of support and help in getting to learn the product. The product itself is very flexible and offer a lot of possibilities to custom it so that it fits our needs. However, it requires some time and energy to learn how to administrate it properly, especially when you are a small team (like ours)

This product is very flexible and offer a lot of opportunities to custome it if you have the skills and time for it

There is a steep learning curve. In addition, it is sometime necessary to re-adjust some settings after an product update release, which might be frustrating